Related
I had success with the unrevoked root, so I decided to give the 2.2 upgrade a shot. I successfully reverted to a fresh stock unrooted 2.1, using the PB31IMG.zip file. This also took away my Clockwork Mod. Next I moved to the step of loading the dinc_ota.zip. After the 3 cycles it went to the HTC incredible boot screen and didnt move. I waited 15 minutes and nothing changed. I decided to pull the battery but no luck, still hangs on the white screen when i turn the phone on. I can still get into HBoot, which shows my radio as the updated 2.05 and my hboot is .79.
I've tried the RUU but I cannot boot the phone past the white htc screen so it wont work. I've also tried to load the PB31IMG.zip file from the sdcard agian, which doesnt. I get an error saying its too old.
Is there a way to restore my phone from Hboot?
Do you have any suggestions of threads I could read for the answer?
Thanks
Try the image again, then try the ota.
Sent from my ADR6300 using XDA App
i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
k_flan said:
i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
Sorry, my bad. DONT APPLY THE UPDATE AGAIN!
Sent from my ADR6300 using XDA App
Try a clear storage.
jdkoreclipse said:
Try the image again, then try the ota.
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I tried the image again, same error, it reads:
Main Version is older!
Update Fail!
Do you want to reboot device?
vol up yes
vol down no
I tried the reboot and it still hangs at white screen.
k_flan said:
i would not try the radio update again, that's pretty much a sure fire way to brick. I would wait for the opinions of others first.
PB31IMG.zip doesn't roll the radio back does it? It reverts to stock recovery and ROM, but does it roll the radio back too?
I thought you had to follows this to roll the radio back, http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
Click to expand...
Click to collapse
As for the radio update, I agree that it would be a bad idea to try to reaplly it, especially since my HBoot shows it as the updated radio.
I also saw the thread you pointed out to me but that requires clockwork mod to be installed and that was removed when i reverted to stock.
Any helpful ideas are greatly appreciated.
Does it show up on adb?
Sent from my ADR6300 using XDA App
jdkoreclipse said:
Does it show up on adb?
Sent from my ADR6300 using XDA App
Click to expand...
Click to collapse
I did try to clear the storage, but it still hangs.
Also tried adb devices in hboot, at the htc incredible white screen, and in the fastboot menu, all with no luck. When I try to boot to recovery it hangs at the same white screen. Might just have to bring it to Verizon tomorrow, I'm beginning to think I may be holding a brick.
To revert your radio back to the original 1.x, you need to have access to adb and pushing to your data directory
Long story short, you dun goofed by pulling the battery
HTC Incredible, rooted w/ modified Sense 2.1
I think its a brick
Sent from my ADR6300 using XDA App
ilinfinityil said:
To revert your radio back to the original 1.x, you need to have access to adb and pushing to your data directory
Long story short, you dun goofed by pulling the battery
HTC Incredible, rooted w/ modified Sense 2.1
Click to expand...
Click to collapse
Once the radio update completed, the white htc inc screen came up and hung there for 15 minutes, I didnt think I had much of a choice.
In that situation what should I have done?
aaman137 said:
Once the radio update completed, the white htc inc screen came up and hung there for 15 minutes, I didnt think I had much of a choice.
In that situation what should I have done?
Click to expand...
Click to collapse
When i did the ota, it took about 7-10 min total. Yours hung on that incredible boot screen for 15 min. You did the right thing.
Sent from my ADR6300 using XDA App
I appreciate all the help, this is why I came to xda. As for my Incredible, I guess its going back to Verizon tomorrow to see what they can do for me. I'm sure I'll be waiting a good week or two until I have my Incredible back, DOH!
I wouldn't think it's bricked if you can still get into the bootloader. Bricked generally comes about when you can't even power the device on. While I have nothing to add in the way of help, I'd say don't give up on the phone yet. I'm betting one of the *real* devs may be able to help you.
Ruoh said:
I wouldn't think it's bricked if you can still get into the bootloader. Bricked generally comes about when you can't even power the device on. While I have nothing to add in the way of help, I'd say don't give up on the phone yet. I'm betting one of the *real* devs may be able to help you.
Click to expand...
Click to collapse
It may be a soft brick.
Sent from my ADR6300 using XDA App
i brick it this morning, called around dinner time, and they dispatched a replacement to me. overnight free shipping!!!
Its not bricked. I had the same issue. You need to follow this guide. Basically you have to redo it to get it to work, and this is the only way that I could do it.
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
(This was the most important part of the guide for me. Solve that: error saying its too old. All glory to Adrynalyne)
Having troubles with the RUU giving connection errors? Do this.
Go to start, and in the search/run box, type
%temp%
Delete all that you can. Make sure the RUU is not running in the background.
Now run the RUU again. Once it starts to the first screen, it has extracted the files to the temp directory. You can then copy them to a safe place. It will be a long winded numbered folder, with a similar subfolder.
Once you have copied it to a safe place, you can then copy adb.exe, fastboot.exe, and adbwinapi.dll from the latest SDK into it, overwriting the older copies. Then start the RUU by executing ARUWizard.exe. This fixed the problem for me.
You can also rename the rom.zip contained within the extracted files to PB31IMG.zip and put it on your sd card. Booting to HBOOT will scan it and offer to install.
HolyGrail said:
Its not bricked. I had the same issue. You need to follow this guide. Basically you have to redo it to get it to work, and this is the only way that I could do it.
http://androidforums.com/all-things...16-how-revert-back-earlier-version-hboot.html
(This was the most important part of the guide for me. Solve that: error saying its too old. All glory to Adrynalyne)
Having troubles with the RUU giving connection errors? Do this.
Go to start, and in the search/run box, type
%temp%
Delete all that you can. Make sure the RUU is not running in the background.
Now run the RUU again. Once it starts to the first screen, it has extracted the files to the temp directory. You can then copy them to a safe place. It will be a long winded numbered folder, with a similar subfolder.
Once you have copied it to a safe place, you can then copy adb.exe, fastboot.exe, and adbwinapi.dll from the latest SDK into it, overwriting the older copies. Then start the RUU by executing ARUWizard.exe. This fixed the problem for me.
You can also rename the rom.zip contained within the extracted files to PB31IMG.zip and put it on your sd card. Booting to HBOOT will scan it and offer to install.
Click to expand...
Click to collapse
This only works if he can get to recovery.
TNS201 said:
This only works if he can get to recovery.
Click to expand...
Click to collapse
Your point? He can get into stock recovery, which is all he needs to start over.
HolyGrail said:
Your point? He can get into stock recovery, which is all he needs to start over.
Click to expand...
Click to collapse
His tutorial says you need clockwork, so he might not be ok. You need the ability to push files to your data directory which is why he needs clockwork, unless he can do it the old way when we first got root by the time attack method. I do not know how much functionality adb would have if he was able to access ADB with stock recovery.
This is all his fault for his failure to read. From what I read in the OP, he did this
1. He downgraded with the RUU image.
2. He tried to apply the OTA
He failed to do this or at least didn't acknowledge that he did this, but he didn't install the original OTA which you will get after you RUU back to stock. If you boot your phone back up it should download the OTA from VZW and then you apply the leaked OTA. So sounds like this is the reason for his brick/semi-brick. Failure to read or understand what youre doing leads to FAIL>
Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.
Newsflash. I've never heard one story of Spring checking a bootloader to make sure a phone is S-On.
Flash A stock ROM and you;ll be good, although there have been posts that say Sprint will work on Rooted phones now.
rosario04 said:
Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.
Click to expand...
Click to collapse
Ignore this, double post. Next post.
rosario04 said:
Having a hell of a time getting my evo 4g to change to s on. I have successfully unrooted it but the s off remains there. I need to take it back to sprint for repairs.
I have tried several with the recent unrevoked 3. But my results are after flashing "waiting 5 seconds because windows hates" message and the other says waiting to reboot" (both freezes forever). Any direction would be appreciated.
Thanks you.
Click to expand...
Click to collapse
You have to have a custom recovery to do that (Amon-RA or Clockwork). You need to reinstall Amon-Ra Recovery by putting this in the root of your SDCard and rename it "PC36IMG.zip": http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Then flash this: http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
After that just run an RUU from here: http://goo-inside.me/supersonic/ruu
In case the RUU won't work from your computer, download one of the ZIP ones, put it in the root of your SDCard and rename it "PC36IMG.zip". That always works.
I am not sure what you mean by "Spring checking but I have flashed the stock rom PC36IMG.zip onto the root of the sd. My understanding that once your successful doing this you basically revert to the original rom. I have done that thanks to this site. But, I cannot for the life of me get the s on back on. Rooting my phone with three different custom roms were easier. Not all Spring stores like rooted phones. Id rather revert to original with the s on to be sure. product F thanks for the reply I will try that..perhaps I missed something. Thank You.
HipKat said:
Newsflash. I've never heard one story of Spring checking a bootloader to make sure a phone is S-On.
Flash A stock ROM and you;ll be good, although there have been posts that say Sprint will work on Rooted phones now.
Click to expand...
Click to collapse
That plus the leaked document from the sprint employee forums that said that sprint supports rooted devices means we don't have to fret over s-on for service just make sure that your phone is running a sense rom when it is taken in otherwise they can't use the diagnostic commands from the dialer to fully support the device.
Sent from my PC36100 using Tapatalk
s on
Well I think my biggest problem is that i unrooted my phone because Clocwork will not work for me to flash forever s on because it is unrooted. Is this correct? Thanks
rosario04 said:
Well I think my biggest problem is that i unrooted my phone because Clocwork will not work for me to flash forever s on because it is unrooted. Is this correct? Thanks
Click to expand...
Click to collapse
If you're using Clockwork, you have to disable Signature Verification.
s on
Product F(RED) said:
You have to have a custom recovery to do that (Amon-RA or Clockwork). You need to reinstall Amon-Ra Recovery by putting this in the root of your SDCard and rename it "PC36IMG.zip": http://files.androidspin.com/downloads.php?dir=amon_ra/RECOVERY/&file=PC36IMG.zip
Then flash this: http://downloads.unrevoked.com/forever/current/unrevoked-forever-son.zip
After that just run an RUU from here: http://goo-inside.me/supersonic/ruu
In case the RUU won't work from your computer, download one of the ZIP ones, put it in the root of your SDCard and rename it "PC36IMG.zip". That always works.
Click to expand...
Click to collapse
But to get clockwork to work you have to be rooted...correct?
Thank you
Yes but you're still s-off so follow those instructions.
Sent from my PG86100 using XDA Premium App
Thanks for staying with me. Appreciate it.
Here is how I wasable to get to recovery to get to the root directory for choosing zip from sd.
STEP 9: TURN OFF DEVICE
Power down the device by holding the Power Button for 2 seconds. Allow it to shutdown completely. Wait about 10 seconds before next step.
STEP 10: RECOVERY MODE
Hold down VOL DOWN + POWER until device boots into a White Screen.
Move to RECOVERY by using the VOL DOWN toggle and select by using POWER button.
STEP 11: TRANSFER PC36IMG.zip TO SDCARD
Connect the MICRO USB Cord. There is an option for this in both the Amon RA and Clockwork recovery.
Transfer the PC36IMG.zip to the ROOT of your SDCard.[/SIZE][/SIZE]
It was the connection and discnnection of th usb cable. Everything was in green. Is that normal.
So, my next step was to flash the forever s on zip. The results were unsupported radio version. Update failed. The current version I have is 2.15.00.05.02. on the new update on my evo. I tried it first by removing the pc36img.zip nd then tried it with it on...same results.
So I found this radio version (EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_NV_2.15_003), but I am not sure if this is what version is needed. Anyways, I apologize for this long everyone, but I am trying to provide as much info and hopefully I can minimize your time. Thanks alot.
rosario04 said:
.
...
So, my next step was to flash the forever s on zip. The results were unsupported radio version. Update failed. The current version I have is 2.15.00.05.02. on the new update on my evo. I tried it first by removing the pc36img.zip nd then tried it with it on...same results.
So I found this radio version (EVO_Radio_2.15.00.05.02_WiMAX_27243_PRI_NV_2.15_003), but I am not sure if this is what version is needed. Anyways, I apologize for this long everyone, but I am trying to provide as much info and hopefully I can minimize your time. Thanks alot.
Click to expand...
Click to collapse
The radio package you mention is the same radio you already have, so you'll want an older version. I'm not exactly sure of the version number, but I do know that is not the correct one.
Remember when you flash radios to not pull the battery. It'll flash, then upon rebooting it'll finish. You'll see a screen that you probably haven't seen before, it'll most likely be an arrow pointing down to a phone or an Android in a box... or something like that. Regardless of what you see after the flash, don't freak out and pull the battery - you'll end up bricking your phone. It's one of the few ways to guarantee a real brick, the phone will never turn on again. You may already know this, or it may be in whatever guide you're using, but it's good to know.
Anyway, I'll see if I can find the correct radio for you, and good luck!
Edit: I read somewhere that someone used this one to get s-on: http://www.mediafire.com/?v0ymbhaa0ltcvyy
However, you may need to do some trial and error. It should work, but here's a link to all of them: http://forum.xda-developers.com/showthread.php?t=715485
These are from Calkulin, so if they're PC36IMG files you'll be fine, but I'm pretty sure you flash them in recovery. Sorry, it's late & I'm lazy. Anyway, I think Calkulin still uses amend scripting, which will render them incompatible with ClockworkMod. You'll either need to switch to Amon Ra to flash them or find a different flashable zip. I think you'll only need to flash the radio, not all of them, but I could be wrong.
Sent from my PC36100 using Tapatalk
You don't need S-OFF to have sprint work on your phone for repair. My cousin just got an insurance replacement Evo 4g because he washed his phone with his clothes. He brought it over to me to be rooted and the phone he got was already S-OFF and that is an Insurance REFERB. also with the leaked forum of how Sprint will infact work on Rooted phones gives it away that you dont need S-OFF
Plainjane. Thanks for the info. I downloaded the zip from the first site you showed here and it ran well with the exception that it got stuck on formatting cache. So, I rebooted. s off still on. I will try the next one here in a few. Thanks everyone.
s on
well. While I continue to try and solve this puzzle I will attempt to attach this link on how to flash a radio to evo. i take no credit.
well i am happy to say i have finally go the s on back on. I believe the problem was that i left the recovery supersonic ra image on the root directory of the sd. i deleted that and flashed the supersonic s on image and voila!!! Everythin crumbled under the rosario wrath and s on is on. Thats Boricua power. My next problem is flashing sense back on. Khilbron, I wasnt ignoring your post on sense, it was just I was trying to get the other things done. So can you please expand on the sense. Thanks to everyone who took out the time even you kipkat with your kind of unfriendly comments. Dueces.
s on
rosario04 said:
well i am happy to say i have finally go the s on back on. I believe the problem was that i left the recovery supersonic ra image on the root directory of the sd. i deleted that and flashed the supersonic s on image and voila!!! Everythin crumbled under the rosario wrath and s on is on. Thats Boricua power. My next problem is flashing sense back on. Khilbron, I wasnt ignoring your post on sense, it was just I was trying to get the other things done. So can you please expand on the sense. Thanks to everyone who took out the time even you kipkat with your kind of unfriendly comments. Dueces.
Click to expand...
Click to collapse
i took my phone back to sprint and they replaced both speakers. now to root again.
Again. Want to thank everyone for their help.
I have a Galaxy Note 2 on the sprint network. Yesterday someone sent me a text and i tried to sent them a text back but my phone didn't have a signal. It reset itself a bunch of times. It stopped resetting and now there is no signal to the tower. I looked on my phone and Baseband version, network, mobile network type say unknown. service state is out of service, username is unavailable. mobile network state is disconnected, my phone number is unknown, min unknown, prl version unknown, meid unknown, imei unknown, iccid unknown. device status modified.
I rooted my phone when i first got it with the method that doesn't make your flash counter go up. I had super user installed and had the OTA survival mode checked and did the OTA update for multiwindow and then lost root. This wasn't a big deal to me so I just left it alone, everything worked. Its been a couple of months and then this happened. I reflashed a stock rom on the phone and that didn't fix anything. I rooted it with the Samsung Note 2 toolkit and that went well. But it somehow got stuck on the boot screen again after a while so i just reflashed to stock.
I downloaded QPST and entered my IMEI into the nv line 550 and clicked the write NV block and returned an error. Im stuck. I have insurance and I've only had the phone a couple of months. What the heck happened? Was it somekind of wipe? I have been working on this all day and I'm going to bed now, but can someone help me out?
I would not have been so quick to start messing with qpst.In most cases where ive seen this the imei and related numbers were fine and it was a system screw up. That said,This happened to me recently and even odin wouldnt fix it. I ran THIS and it brought me back so I would try that first.
billard412 said:
I would not have been so quick to start messing with qpst.In most cases where ive seen this the imei and related numbers were fine and it was a system screw up. That said,This happened to me recently and even odin wouldnt fix it. I ran THIS and it brought me back so I would try that first.
Click to expand...
Click to collapse
thanks. I am downloading that now and will try it and let you know. I didn't want to start messing with qpst but i saw a tutorial that you can enter your imei back into your phone with it. i got my numbers off the box and went to work. but qpst would not write the values into my phone.
when i plug the usb into the phone a flag pops up in windows and says hardware id is missing as well.
billard412 said:
I would not have been so quick to start messing with qpst.In most cases where ive seen this the imei and related numbers were fine and it was a system screw up. That said,This happened to me recently and even odin wouldnt fix it. I ran THIS and it brought me back so I would try that first.
Click to expand...
Click to collapse
i went to the link. i downloaded the file. it was a zip file so i put it on an sdcard and slapped it in my phone. i used the vol up, home key, and pwr key and then i used the update from zip file on external storage. it did some stuff and rebooted. i checked my flash counter and it went up and said i was running custom, custom.
i didn't see any instructions with your post that you linked and I probably didn't use that file the way it was supposed to be used. how exactly do you use it? and when i turned my phone on it still said baseband unknown.
thanks again for helping me with this.
dd807 said:
i went to the link. i downloaded the file. it was a zip file so i put it on an sdcard and slapped it in my phone. i used the vol up, home key, and pwr key and then i used the update from zip file on external storage. it did some stuff and rebooted. i checked my flash counter and it went up and said i was running custom, custom.
i didn't see any instructions with your post that you linked and I probably didn't use that file the way it was supposed to be used. how exactly do you use it? and when i turned my phone on it still said baseband unknown.
thanks again for helping me with this.
Click to expand...
Click to collapse
Do you have Root Explorer? If baseband is showing unknown makes me wonder if build.prop is there and complete...?
It needed flashed in a custom recovery. Did u use twrp or cwm to flash it? If so, you did it right. Is it only the baseband thats unknown or everything still? Did you try a ##72786# dialer code reset?
garwynn said:
Do you have Root Explorer? If baseband is showing unknown makes me wonder if build.prop is there and complete...?
Click to expand...
Click to collapse
I don't have root explorer on here right now because I was trying to return the phone back to stock for a return to the sprint store.
I used the stock rom that you download from the samsung note 2 tool kit. how do i check what your talking about?
billard412 said:
It needed flashed in a custom recovery. Did u use twrp or cwm to flash it? If so, you did it right. Is it only the baseband thats unknown or everything still? Did you try a ##72786# dialer code reset?
Click to expand...
Click to collapse
everything is still unknown.
when i dial ##72786# it goes to a meny labeled SCRTN but is blank with no options.
at this point I used triangle away and flashed the stock rom on my phone, it keeps randomly resetting. in the setttings it still has baseband unknown. i did the ota update and the build number is JROO3C.L900VPALJC
under status, everything is unknown and at the botton it says device modified.
when i put it into download mode right now it says custum binary: no ; current binary: samsung official; system status: custom
this started when the phone just started resetting a bunch after my buddy texted me and then it didn't have service and all the values were wiped, i just want to take it back to sprint because ive only had it for a couple of months. will the above values be ok for a trip to the sprint store?
billard412 said:
It needed flashed in a custom recovery. Did u use twrp or cwm to flash it? If so, you did it right. Is it only the baseband thats unknown or everything still? Did you try a ##72786# dialer code reset?
Click to expand...
Click to collapse
i didnt use twrp or cwm to flash it. just used the factory recovery to. i will use twrp to do it now. thanks man.
billard412 said:
It needed flashed in a custom recovery. Did u use twrp or cwm to flash it? If so, you did it right. Is it only the baseband thats unknown or everything still? Did you try a ##72786# dialer code reset?
Click to expand...
Click to collapse
i think i have a corrupted EFS. can anyone help?
I had this happen to me when I first got the phone and rooted. Scariest first day of ownership thought I was going to have to go in to sprint. Thankfully I flashed the full stock tar and my phone came back to life. Maybe you should try flashing it and see how it turns out for you.
http://forum.xda-developers.com/showthread.php?t=2035566
Sent from my SPH-L900 using xda app-developers app
RayTrue04 said:
I had this happen to me when I first got the phone and rooted. Scariest first day of ownership thought I was going to have to go in to sprint. Thankfully I flashed the full stock tar and my phone came back to life. Maybe you should try flashing it and see how it turns out for you.
http://forum.xda-developers.com/showthread.php?t=2035566
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
I went back to full stock with :http://forum.xda-developers.com/showthread.php?t=2086769
i also went baclk to full stock using the samsung note 2 toolkit and triangle away.
both methods left me with custom binary as no and current binary as samsung offical, but system status says custom.
both ways.
and the screenshots that i posted earlier are the same.
i found this thread:
http://forum.xda-developers.com/showthread.php?t=1611796
and i think i have a corrupt EFS.
as it is, does the spring store take your phone back if system status is custom and device says modified?
b.) if i can fix it, it would be better than taking it back. everything on the phone still works, but it obviously cant see a cell phone tower or make calls. data on wifi only type deal.
thanks for any help...
dd807 said:
I went back to full stock with :http://forum.xda-developers.com/showthread.php?t=2086769
i also went baclk to full stock using the samsung note 2 toolkit and triangle away.
both methods left me with custom binary as no and current binary as samsung offical, but system status says custom.
both ways.
and the screenshots that i posted earlier are the same.
i found this thread:
http://forum.xda-developers.com/showthread.php?t=1611796
and i think i have a corrupt EFS.
as it is, does the spring store take your phone back if system status is custom and device says modified?
b.) if i can fix it, it would be better than taking it back. everything on the phone still works, but it obviously cant see a cell phone tower or make calls. data on wifi only type deal.
thanks for any help...
Click to expand...
Click to collapse
I'm not familiar with that EFS issue since I've never read about it. However I would try that tar I posted as a last resort since the stock zip didn't do anything for you. The issue you're describing is the exact same thing that happened to me and that tar brought me back. And about being custom/modified it all depends on the Sprint Rep you get. Some are cool about it some are not.
Sent from my SPH-L900 using xda app-developers app
garwynn said:
Do you have Root Explorer? If baseband is showing unknown makes me wonder if build.prop is there and complete...?
Click to expand...
Click to collapse
i just downloaded root explorer.
i think im having some efs issues. i downloaded efs pro to help with it but it says my phone is not perm rooted. but i do have root right now.
btw- the galaxy note 2 tool kit is friggin awesome- totally donating.
RayTrue04 said:
I'm not familiar with that EFS issue since I've never read about it. However I would try that tar I posted as a last resort since the stock zip didn't do anything for you. The issue you're describing is the exact same thing that happened to me and that tar brought me back. And about being custom/modified it all depends on the Sprint Rep you get. Some are cool about it some are not.
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
thanks, ill try it. i mean- whats one more flash right? could fix it. fingers crossed. thanks for your help man.
ill let you know.
also to everyone helping, i made a backup of all my system settings with my backup pro app before all this happened. i was wondering if it backs up your efs data anywhere and if it does, how could i get it back on my phone?
Sent you a pm
Sent from my SPH-L900 using xda app-developers app
RayTrue04 said:
I had this happen to me when I first got the phone and rooted. Scariest first day of ownership thought I was going to have to go in to sprint. Thankfully I flashed the full stock tar and my phone came back to life. Maybe you should try flashing it and see how it turns out for you.
http://forum.xda-developers.com/showthread.php?t=2035566
Sent from my SPH-L900 using xda app-developers app
Click to expand...
Click to collapse
flashed the sextape back to stock rom and it didn't work. i think my efs is corrupted- gunna take something more than flashing- like editing some files to put my meid and other info and pushing it back to my phone.
looking at this right now:http://forum.xda-developers.com/showthread.php?t=2060085
dd807 said:
flashed the sextape back to stock rom and it didn't work. i think my efs is corrupted- gunna take something more than flashing- like editing some files to put my meid and other info and pushing it back to my phone.
looking at this right now:http://forum.xda-developers.com/showthread.php?t=2060085
Click to expand...
Click to collapse
Damn that sucks! I really thought it might bring you back since it worked for me. Good luck!
Sent from my SPH-L900 using xda app-developers app
Update-
my phone is screwed. i got the MSL and put it in my phone and nothing happens. i have to take it back and get a new one.even though all the hardware works, just cant program the info back in the phone for meid, baseband, username, icc id, etc. etc. so no voice calls.
the bummer is that this all happened randomly. i wasn't messing with my phone at all and it was running great then it reset a bunch of times and then wiped everything. i don't know if it would have helped, but i highly reccomend everyone backing up their EFS. because you never know when this will happen to you.
take care, thanks for the help everyone.
I'm no stranger to rooting and flashing ROMs, but this is a new one on me. I've had my Virgin Mobile Siii for several months and am pretty happy with it. However, I want to go to CyanogenMod. I also want to root and put a custom recovery on my phone.
My first problem is that I put TWRP on the phone a month or two ago, but when I try to boot into recovery, all I see is the <e3> recovery. I have a TWRP folder with a copy of a Nandroid backup on it, so it must have been there, right? Anyway, to try to figure this out, I downloaded ROM Manager (free version). It says I have both TWRP and Clockwork recoveries on the phone, and trying to have it set me up to use or update either one goes nowhere. Superuser says I'm not rooted.
What I'd prefer to do is get a working root and TWRP recovery on the phone -- I've used it with both an EVO 4G and HTC One V I had in the past and I'm comfortable with it, though if I have to use CWM I can. Then I'd like to use the new CyanogenMod installer if I can be sure it's compatible with the phone. My baseband/build version numbers end with MG2, so I know the phone might be slightly different than a Sprint SIII, but from my exploring the forums here and on other sites it seems to be pretty compatible.
This uncertainty of whether or not I have a custom recovery on the phone makes me very leery of trying to flash a new one without a second opinion. Can anyone help or give me guidance on this?
EelResuah said:
Can anyone help or give me guidance on this?
Click to expand...
Click to collapse
Have you went here and used this method? I would first flash all that way back to stock unrooted on pc Odin to get rid of all the clutter. And if it were me, I wouldn't use ROM manager either. It says Sprint in the link, but everything is the same.
http://forum.xda-developers.com/showthread.php?p=34579827
Sent from my SPH-L710 using XDA Premium 4 mobile app
Gracias
jdsingle76 said:
Have you went here and used this method? I would first flash all that way back to stock unrooted on pc Odin to get rid of all the clutter. And if it were me, I wouldn't use ROM manager either. It says Sprint in the link, but everything is the same.
http://forum.xda-developers.com/showthread.php?p=34579827
Thanks, I will check this one out. The problem I often have is finding my way through a dozen or so threads that almost give me what I need, but this one looks pretty straightforward. I probably won't try it until the weekend, but in the meantime, thanks for the tip!
Click to expand...
Click to collapse
I turned my s3 off for about a month while I used my note2. When I turned it off it was rooted with twr recovery and running a custom Rom. When I turned it back on the Rom was still running however I did loose all the widgets I was using. Over night titanium tried to run the scheduled backup redo. Then in the morning I noticed titanium said it could not gain root access. I tried other apps that require root and none will gain access. The super user app is still there but says there is no root. It's simple enough to re-root but I'm really curious as to what happened. Any ideas?
Sent from my SGH-T999 using XDA Premium 4 mobile app
Please Specify Rom and Android Version.
In short, if your TWRP recovery is intact try a factory reset from there.
Thanks Persius, I haven't tried to go into recovery since I have to do it manually cause I'm not sure what will happen if it's not there. My computer is broke right now so I'm limited. It's been since the s3 first came out that I installed the Rom so I'm not really sure which one I'm on but it says JZO 54, and it's 4.1.2 Thanks again for your help
bls2633 said:
Thanks Persius, I haven't tried to go into recovery since I have to do it manually cause I'm not sure what will happen if it's not there. My computer is broke right now so I'm limited. It's been since the s3 first came out that I installed the Rom so I'm not really sure which one I'm on but it says JZO 54, and it's 4.1.2 Thanks again for your help
Click to expand...
Click to collapse
Say... Are you sure we talking about an SIII or an S-II ?? That sounds like the 4.1.2 Stock of an S II. What does it say under Settings > About Phone > Model Number ?
Turn off completely then Hit Volumn Up + Home +Power all at the same time. Wait for 3 minutes or so with all 3 pressed. You will see Recovery come on. Let go of all 3 buttons and then do a Factory Reset in the recovery.
Thanks again, under build that's what it says, jzo 54, I think it might be Liquid Smooth. And it is an s3. I will try to go into recovery if you don't think anything will happen if that's not there either. Something else weird I just thought of is I also had some strange kiddie like themes and apps I never put there. It's like someone else used my phone but that's not possible as I saw it every day and live alone. Strange. Any way, thanks again
bls2633 said:
Thanks again, under build that's what it says, jzo 54, I think it might be Liquid Smooth. And it is an s3. I will try to go into recovery if you don't think anything will happen if that's not there either. Something else weird I just thought of is I also had some strange kiddie like themes and apps I never put there. It's like someone else used my phone but that's not possible as I saw it every day and live alone. Strange. Any way, thanks again
Click to expand...
Click to collapse
Yes its safe to Go into Recovery. Go ahead and do a Factory Reset. Let me know how that goes.
Ok, did the factory reset and went ahead and did the ota update to 4.0 I'm going to root again. Do you have any suggestions on a good Rom? Also what is the best way to root these days and best recovery? Thanks Perseus I appreciate your help and advice
Sent from my SGH-T999 using XDA Premium 4 mobile app
I am confused. Wasn't (or shouldn't it be ) your S3 already on the JB 4.1 ? What did you mean by OTA update to 4.0 ? Are you referring to the OTA Update to 4.3 ?
I can not comment on Rooting unless I know which os version you have.
Sorry, was a misprint. Yes, went to 4.3
Sent from my SGH-T999 using XDA Premium 4 mobile app
So if you still have TWRP then flash Superuser from Recovery. Lookup its thread here on XDA.
However, with the Knox being present and SELinux in Enforcing state, your chances of Rooting are slim.
Please don't brick your device.