Related
Alright so I started the process of rooting, unlocking, and flashing the Bean ROM on my VZW GS3. I backed up using Nandroid and Titanium backup, rooted and unlocked the bootloader using EX Unlock yesterday. Then, without flashing a ROM, I rebooted my phone. And then I got drunk. Today, I flashed recovery, booted into recovery mode, deleted the user data (again) and installed then installed the Bean ROM. I figured my bootloader was still unlocked but I guess it wasn't. Now I'm getting the "This System Software not authorized by Verizon Wireless..." message.
Anybody have any clue what to do now?
Restock the Rom via odin flash of stock files from Adams thread
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
You say you made a nandroid yesterday but today you just flashed recovery. I'm confused.
Sent from my SCH-I535 using xda app-developers app
If you use ez unlock I'd say unlock and lock twice. Recovery told me I wasn't unlocked at first.
Sent from my SCH-I535 using xda premium
Hey guys, so I have been trying to work at this and here is where I'm at...
I'm following section 6 of this post [http://forum.xda-developers.com/showthread.php?t=1762709]. Everything works as listed except for when I select the ROM from the three in that post and try and run it through Odin. It always fails. I tried all three ROMs with the same result and since I don't know what exactly is keeping this from working, I can't troubleshoot it in any way. If anyone could help, I would really appreciate it.
Thank you!
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
mike216 said:
Hello guys I just got may galaxy S3 from a friend. I think the bootloader is still unlocked after I received an OTA today. I don't have root or recovery. I just want to be sure I use the correct root and recovery method. Could someone point me to the one they used on this build with success? I would be greatly appreciated. I did look but none are specific enough for me to be sure I'm using the correct one.
Is my bootloader still unlocked if it says (custom)?
Again I appreciate any help
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
nghtrain88 said:
Welcome! In order to unlock your BL in the first place you must have had root. This is a good thread on rooting, unlocking, and flashing recovery/ROMs/kernels:
http://forum.xda-developers.com/showthread.php?t=1762709
Click to expand...
Click to collapse
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
mike216 said:
Thanks so much bud! Will I be all good on the updated build I received today?
My bootloader is unlocked if it says custom on boot?
Again I really appreciate it!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
How did you unlock your bootloader?
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
With the app
Sent from my SCH-I535 using xda premium
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
annoyingduck said:
Ok, issue is probably that you used the current version 1.4 I think. In the app description in the playstore is a link to older versions, you want 1.2. The new ones are unlocking, but it's not sticking. There is also a link in the current root guide somewhere, but direct from the play store is fine.
Click to expand...
Click to collapse
link for ez-unlock 1.2
annoyingduck said:
How did you unlock your bootloader?
Click to expand...
Click to collapse
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
nghtrain88 said:
As long as you have one of the stock builds listed in section 2 of that thread you should be good. The EZ-unlock app should be able to tell you if you're BL is unlocked.. also if you reboot the phone, if the samsung splash flashes for a split second (the one before you see Samsung Galaxy SIII), then you're prob unlocked.. if you see it for a few seconds then you're prob locked
Click to expand...
Click to collapse
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
mike216 said:
Man I rooted flashed recovery in rom manager. (recovery wouldn't stick) so I flashed it again after making a nandroid and ended up having to recover a soft brick at 4am. Thank God for puremotive's guide on how to recover from it I was able to be back up. I don't know what went wrong. Because I didn't have busy box. Maybe I shouldn't have used the latest recovery rom manager flashes? I'm on stock with root and afraid to move anywhere! Anyone know how to make recovery stick on stock rom? I've never had this happen. Usually I would be OK and on to try AOSP on other devices uve had. Right now I'm rooted on stock rom with bootloader unlocked and have OTA root keeper in case I get another OTA. Any help would be greatly appreciated! Take care
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
mike216 said:
Let me be more specific because I may have had a locked bootloader.
I received the phone yesterday from my friend. He did unlock the bootloader with the app. I installed the official OTA from Verizon as soon as I got it. I rooted it. I didn't bother trying to unlock the bootloader because after the OTA when it booted it said custom with a lock symbol on boot up. I rooted and flashed the latest recovery from rom manager. I'm sure I picked the right phone. I made a nandroid but my recovery wouldn't stick. I remember it saying something about Co firming something about a recovery and I could have chosen yes. It sounded like CWM wouldn't stick if I choose yes?
I don't know if the OTA locked my bootloader back up?
I would like to try again. Any of you guys no how to make recovery stick on stock rom? I would like to try paranoid android. What recovery should I be on to flash this jelly bean based rom? I would really appreciate anyone who knows how I screwed up or has went straight to JB from a specific CWM recovery. I'm also not sure if I should said yes or know when in CWM when asking me that recovery question. I wish I remember what the question was
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Cwm 6.0.1.2 for aosp jb, do not use the old 5 . something touch in ez recovery
mike216 said:
Thanks for everything Boss! That probably was the reason my recovery wouldn't stick. I used the link to grab easy unlock 1.2. I'm now unlocked, rooted. I want to flash an AOSP based rom (paranoid android) what recovery should I flash? The newest in rom manager or the slightly older one EZ-Recovery has to offer?
Thanks once again!
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Brian Gove said:
Which is the recovery that you want to use? I have the latest CWM touch on my Dropbox if that's the one you want. The regular CWM in the app is fine to use and twrp recovery has a thread in the development forum.
Click to expand...
Click to collapse
I'm on stock ICS in want to go to paranoid android. Sorry guys but after last night I'm paranoid myself!
Sent from my SCH-I535 using xda premium
Brian Gove said:
The app doesn't actually check the bootloader. It just keeps the info in the app data. Meaning if you unlock with the app then uninstall ezunlock and then reinstall it won't know if you're locked or unlocked.
I'm 90% sure you wouldn't have been able to install the OTA if your bootloader was unlocked. The 'custom' on the boot doesn't mean that, and now that I think of it the fact you saw that proves that you aren't unlocked.
If you're still stock rooted then download the EZ unlock 1.2 from the link above and also go find EZ recovery on the market. Do not use the market version of EZ unlock. Now it doesn't matter what order you do it in but unlock your bootloader with the app them use EZ recovery to flash your recovery. Then you're all set to flash ROMs.
Click to expand...
Click to collapse
Thanks once again! I'm now on PA after a pack of smokes! Appreciate all your help. You were absolutely right ! Recovery stuck and it flashed with no problem. I used the current recovery straight from ROM manager
Sent from my SCH-I535 using xda premium
Good, glad to hear you got it rolling.
2 months back, I upgraded my phone to S3, so I kept my infuse aside. Today morning when I tried to switch on the phone, phone doesnt start.
It was perfectly working before I upgraded my phone.
Is it bricked? I am able to open CWM, I wiped cache, dalvik cache and factory rest through CWM. Is there any other way to get back instead of download mode. my last destination is download mode, go back to stock. but just checking, if there is any other way, before trying it.
TIA
atrix4nag said:
2 months back, I upgraded my phone to S3, so I kept my infuse aside. Today morning when I tried to switch on the phone, phone doesnt start.
It was perfectly working before I upgraded my phone.
Is it bricked? I am able to open CWM, I wiped cache, dalvik cache and factory rest through CWM. Is there any other way to get back instead of download mode. my last destination is download mode, go back to stock. but just checking, if there is any other way, before trying it.
TIA
Click to expand...
Click to collapse
do you have adb access in recovery? anyway why not flash in download mode now that you have already wiped data?
Dani897 said:
do you have adb access in recovery? anyway why not flash in download mode now that you have already wiped data?
Click to expand...
Click to collapse
yeah that is my final shot. just checking whether there is any otherway and checking is there a problem keeping the phone idle for long time.
Evening i will flash stock in download mode.
atrix4nag said:
yeah that is my final shot. just checking whether there is any otherway and checking is there a problem keeping the phone idle for long time.
Evening i will flash stock in download mode.
Click to expand...
Click to collapse
yeah if you had adb access there is a chance you could identify the issue but the idea that you'd be able to correct it is iffy. but if you hadn't already done a reset you could potentially use adb to backup your data and apps before a reflash. anyway I think you will like the selection of jelly bean ROMs. the infuse might not be a galaxy s3 but with cm10 its not so bad.
Dani897 said:
yeah if you had adb access there is a chance you could identify the issue but the idea that you'd be able to correct it is iffy. but if you hadn't already done a reset you could potentially use adb to backup your data and apps before a reflash. anyway I think you will like the selection of jelly bean ROMs. the infuse might not be a galaxy s3 but with cm10 its not so bad.
Click to expand...
Click to collapse
I loved my infuse alot, with my upgrade eligiblity i switched to S3, but still with stock.
I used heimidall oneclick back to stock, and I tried to install ICS rom, it stuck in CWM.
Any idea.
atrix4nag said:
I used heimidall oneclick back to stock, and I tried to install ICS rom, it stuck in CWM.
Any idea.
Click to expand...
Click to collapse
Did you flash gingerbread boot loaders before you flashed ics
Sent from my SGH-I997 using xda premium
jimjcollins said:
Did you flash gingerbread boot loaders before you flashed ics
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
yes, i installed boot loaders. I think, i didnt rooted my phone, before installing ICS.
now when I try to root my device, i am stuck at the following location.
Please help me.
my phone is working perfectly in UCLB3, but unable to root, and install any other ROMs.
atrix4nag said:
yes, i installed boot loaders. I think, i didnt rooted my phone, before installing ICS.
now when I try to root my device, i am stuck at the following location.
Please help me.
my phone is working perfectly in UCLB3, but unable to root, and install any other ROMs.
Click to expand...
Click to collapse
Well if your phone wasn't rooted or didn't have recovery, how did you try flashing ICS, start over using a back to stock, then follow instructions to a t, on root, recovery, boot loaders, and finally go for a jb ROM there are a few very stable ones available.
Sent from my SGH-I997 using xda premium
---------- Post added at 05:02 PM ---------- Previous post was at 04:58 PM ----------
atrix4nag said:
yes, i installed boot loaders. I think, i didnt rooted my phone, before installing ICS.
now when I try to root my device, i am stuck at the following location.
Please help me.
my phone is working perfectly in UCLB3, but unable to root, and install any other ROMs.
Click to expand...
Click to collapse
Try this, its a wonderful collection of info, http://forum.xda-developers.com/showthread.php?t=1610374
Sent from my SGH-I997 using xda premium
---------- Post added at 05:05 PM ---------- Previous post was at 05:02 PM ----------
jimjcollins said:
Well if your phone wasn't rooted or didn't have recovery, how did you try flashing ICS, start over using a back to stock, then follow instructions to a t, on root, recovery, boot loaders, and finally go for a jb ROM there are a few very stable ones available.
Sent from my SGH-I997 using xda premium
---------- Post added at 05:02 PM ---------- Previous post was at 04:58 PM ----------
Try this, its a wonderful collection of info, http://forum.xda-developers.com/showthread.php?t=1610374
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
U could also try qkster how to thread
Sent from my SGH-I997 using xda premium
jimjcollins said:
Try this, its a wonderful collection of info, http://forum.xda-developers.com/showthread.php?t=1610374
Sent from my SGH-I997 using xda premium
Sent from my SGH-I997 using xda premium
Click to expand...
Click to collapse
I am using •Heimdall One-Click Back To Stock UCLB3 + Easy Clockwork Recovery Mod Install (FOR AT&T USERS) Last Updated: June 03, 2012
this to goto stock, then flash boot loaders.
After flashing boot loaders, I am trying to root the device using super oneclick, then I am stuck on the screenshot shown in my previous post.
If you have clockwork mod recovery you don't need to root. Find an ICS ROM and flash away. BUT FOLLOW ALL THE INSTRUCTIONS IN THE OP. Not shouting at you just emphasizing the importance of it.
Sent from my SGH-I997 using xda app-developers app
I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
arizonaomnia said:
I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
You have to fully unroot to take the ota.
arizonaomnia said:
I am tempted to go back to a regular sense 2.1 stock rooted ROM and attempt the upgrade even though I know I might not be able to root again for a while. I rooted through revolutionary. What is the worst, likely thing that could happen? Will I boot back up to all of my data on the stock Thunderbolt ICS?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
You, of course, need to fully unroot before you flash back to the stock ROM and take the OTA. If you do not fully unroot, taking the OTA will brick you since it contains a new encrypted hboot. I would just wait for the rooted version of the OTA to be released, which should be posted within the next few days.
It would suck to unroot and take the OTA and then have to wait however long before you can root again.
However, if you're talking about flashing an old stock ROM backup that you may have made a long time ago, it wont have any complications. You will be able to receive the OTA then, but do not install it without fully unrooting first.
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
arizonaomnia said:
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
I wouldn't trust it.
Just download the files and go through command prompt to unroot. Not sure if it can be done with trter10s tool or not. I rooted mine with the same method and when I ran trter10s tool and hooked up my phone, it basically was saying it was interrupted. So I had to unroot the old manual way through command prompt.
If you can use his tool though, by all means, use it. It will definitely save you time.
arizonaomnia said:
Buy fully on rooting, does that include the option to on route that is found in the Super SU settings?
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
Click to expand...
Click to collapse
No, that only removes superuser. Fully unrooting means flashing everything back to stock (aka tbolt tool)
Hboot has to be stock as well.
Sent from my ADR6400L using Tapatalk 2
Bummer. Thought about how I could do this without redoing the setup and all that.
Sent from my Sense 4 ICS Thunderbolt with Tapatalk 2
disconnecktie said:
Hboot has to be stock as well.
Sent from my ADR6400L using Tapatalk 2
Click to expand...
Click to collapse
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
johndddd said:
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
Click to expand...
Click to collapse
We are talking about taking the new ICS OTA and the consequences of installing that OTA with your current hboot.
Don't try it.
RBarnett09 said:
We are talking about taking the new ICS OTA and the consequences of installing that OTA with your current hboot.
Don't try it.
Click to expand...
Click to collapse
Isn't that what he was talking about? Sounds like he was rooted with s-off, flashed a stock rooted rom and then updated via the OTA. Sounds like he didn't apply the stock locked bootloader and the OTA applied just fine. Wouldn't the OTA just overwrite the bootloader with the new locked one?
Looks like the only problem you'd have doing it that way is waiting for a new root method.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------
johndddd said:
Nope. I am running Revolutionary Hboot 6.04.1002 and I flashed the stock 2.3 rom and just finished setting up and installing apps after the 4.0.4 ota update.
Click to expand...
Click to collapse
What version is your bootloader now?
Sent from my ADR6400L using xda app-developers app
Nate14 said:
Isn't that what he was talking about? Sounds like he was rooted with s-off, flashed a stock rooted rom and then updated via the OTA. Sounds like he didn't apply the stock locked bootloader and the OTA applied just fine. Wouldn't the OTA just overwrite the bootloader with the new locked one?
Looks like the only problem you'd have doing it that way is waiting for a new root method.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 04:03 PM ---------- Previous post was at 03:59 PM ----------
What version is your bootloader now?
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
Possibly. I figured you'd probably have to return the bootloader to stock before taking the OTA to prevent a brick.
If you can work around it that way, that is definitely a good thing to know.
Sent from my ADR6400L using xda premium
Sent from my ADR6400L using xda app-developers app
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
GMPOWER said:
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
Click to expand...
Click to collapse
So you pulled the OTA and it flashed fine with the Revolutionary Hboot and stock recovery? I have stock .19 recovery and the same hboot as you have there, running rooted stock, and the OTA failed for me. It tried to run and then failed about 1/3 of the way through.
Tiezane said:
So you pulled the OTA and it flashed fine with the Revolutionary Hboot and stock recovery? I have stock .19 recovery and the same hboot as you have there, running rooted stock, and the OTA failed for me. It tried to run and then failed about 1/3 of the way through.
Click to expand...
Click to collapse
I plan on testing this some time in the next hour - I'm currently downloading the RUU. If I get to it tonight I'll update with the results.
GMPOWER said:
I was previously on the most up-to-date version of gingerbread, and used HTC Thunderbolt tool v1.0.1 to S-off/root the device.
I flashed stock recovery 2.11.605.9 to the device. I downloaded the following RUU_Mecha_GINGERBREAD_S_VERIZON_WWE_2.11.605.9_Radio_0.01.78.0916w_3_NV_8K_1.41_9K_1.64_release_226879_signed, pulled the rom.zip from it, and renamed it to PG05IMG.zip to flash it to the device. The device then updated itself to the most up-to-date gingerbread version. I then performed the update for ICS, it installed itself just fine, and the device booted up into ICS. I checked the bootloader, it says that I am S-off Hboot-6.04.1002, and Radio-2.02.00.1117r.
After restarting the device, I started HTC Thunderbolt tool v1.0.1. It asked if I wanted to install SU, I said yes, and it proceeded through it. Once the program finished its installation, I had the SU app in the app drawer, and downloaded ROM Manager so that I could install the recovery, it asked for SU permission to install it. I then restarted just fine into recovery to double check that it was there.
Click to expand...
Click to collapse
That's great. I'm about to try myself, will report back if it works for me as well. Thanks!
Backing up current ROM now.. have the RUU on SD ready to flash.. Looks like RUU in trter10's sig has stock recovery in it, so going to try flashing RUU with 4ext and nusensex currently installed.
backup done.. formatting all except SD to be safe (ext3)
Loading PG05IMG.zip in bootloader...
Updating.. it says it Bypassed the bootloader... excellent... all others updated OK including recovery and radio..
rebooting.. seems to be starting up ok. Signed in to google, will check for OTA in a moment.
Found 395.638MB update (ICS) Downloading now.. appears to have enabled 3g to download even though i'm on wifi.. this my take a bit. not sure why it's not 4g at the moment.
hmm, ics loaded, when trying to root with the thunderbolt tool, phone reboots itself into the bootloader. any ideas? ok, had to choose the bootloader option, and then choose the fastboot option to go back in and it took. weird.
installed busybox and updated 4ext to the latest, looks like im in business.
Actually, all you have to do is download the stock Rom. Then you can do the ota without unrooting. That is what I did.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 05:53 AM ---------- Previous post was at 05:45 AM ----------
I originally unlocked my boot loader through HTCDev. I installed root and clockwork recovery. Clockwork recovery prevented tho ota. So, I installed the stock Rom via recovery which overwrite clockwork recovery AMD unrooted the phone. I then did the ota. So now I have ics with unlocked bootloader. I should say that I spent half a day reading numerous web pages outlining complicated directions on unrooting and ways to remove clockwork recovery. In the end it was quite easy as stated above.
Sent from my ADR6400L using xda app-developers app
trunkamonkey said:
Actually, all you have to do is download the stock Rom. Then you can do the ota without unrooting. That is what I did.
Sent from my ADR6400L using xda app-developers app
---------- Post added at 05:53 AM ---------- Previous post was at 05:45 AM ----------
I originally unlocked my boot loader through HTCDev. I installed root and clockwork recovery. Clockwork recovery prevented tho ota. So, I installed the stock Rom via recovery which overwrite clockwork recovery AMD unrooted the phone. I then did the ota. So now I have ics with unlocked bootloader. I should say that I spent half a day reading numerous web pages outlining complicated directions on unrooting and ways to remove clockwork recovery. In the end it was quite easy as stated above.
Sent from my ADR6400L using xda app-developers app
Click to expand...
Click to collapse
Do you have a link to the file you used?
dante020 said:
Do you have a link to the file you used?
Click to expand...
Click to collapse
ruu is in trter's sig.. either way is easy. ruu will do radios, rom wont. only difference is you flash one in recovery on the other in the bootloader.
I don't seem to be able to install a Custom ROM, when I try I get this error "system software not authorized by verizon wireless found on your phone". I've tried twice with this result. Anybody know why this might be happening?
I'm assuming you took the ota today?
Sent from my SCH-I535 using xda app-developers app
Zub236 said:
I'm assuming you took the ota today?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Actually I soft-bricked my phone yesterday, and since I was brand-new I didn't backup anything. And after a hellish ride unbricking my phone I got it to work, but I went back an update.Before I was at 4.1.2 and it went back to 4.0.4
Waffes775 said:
Actually I soft-bricked my phone yesterday, and since I was brand-new I didn't backup anything. And after a hellish ride unbricking my phone I got it to work, but I went back an update.Before I was at 4.1.2 and it went back to 4.0.4
Click to expand...
Click to collapse
You never unlocked your bootloader.
Well I'm not entirely sure where you went wrong there, did you Odin back to 4.0.4 or was that just an old backup?
That unauthorized software has been detected happened to me before when I took an ota unknowingly and didn't realize it locked my bootloader.
Going back to 4.0.4 was my fault, when looking for a solution to unbrick my phone I found a webpage that explained how and gave me files to download. And the file for the default rom was 4.0.4. I will try again after unlocking my bootloader again.
What did you use to get back to 4.0.4?
I unlocked my bootloader, went to cwm and tried to install a custom rom and got "E:Error in /sdcard/cm- 11 -20131211 - NIGHTLY -d2vzw.zip. (Status 7) Installation aborted".
Is that what it's showing now?
Uodate cwm latest version
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 07:20 AM ---------- Previous post was at 07:19 AM ----------
Update CWM custom recovery
Sent from my SCH-I535 using xda app-developers app
Zub236 said:
Is that what it's showing now?
Click to expand...
Click to collapse
Yes, at first I forgot to wipe data/cache but even after I did that the same thing still comes up. Halp. Should I use Rom Manager? That's the progrom I used originally when I would get the System Software error, and now I get this error when going into CWM manually.
Waffes 775 update CWM RECOVERY
Sent from my SCH-I535 using xda app-developers app
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
You can't install cm11 in older CWM RECOVERY
Sent from my SCH-I535 using xda app-developers app
I'm assuming now that the version I have is outdated and incompatible?
Older recoveries don't work with kit Kat (4.4) roms.
If you are using CWM make sure its 6.0.4.3
Where could I find a newer version? Sorry I'm scrub-cakes.
Can flash it with ROM manager
Download the .IMG from here http://www.clockworkmod.com/rommanager
Personally I prefer to use the app called flashify and install recovery image.
Alright thank you all I should be good now, if not then I will post some more.
Lol System User thing again I'm so bad at this.