Related
Hi guys,
I bought a Nexus S yesterday which is the "new" i9023
It comes with 2.3.3 GRI54 built in already and it's supposed to be using the Super Clear LCD
One thing I noted is I couldn't install custom rom due to a error in the recovery menu about the cache. Which I couldn't find any info on the web. Apparently, there are a few people with this new model who have the same problem as me. So I assume this new model is "unrootable" for now.
Is there any way I could fix this? Or i'm just screwed buying Nexus S too late?
I have the newer nexus s too. And it was easy to root.
You need to unlock your bootloader, and there are loads of guides in this forum.
I did follow the guides on the forum. But after unlocking the bootloader and installing the recovery menu and superuser, the recovery menu shows error messages about the cache, which was pointed out in this post
http://forum.xda-developers.com/showthread.php?t=992114
I reckoned that since most of the users who had that problem was using the new Nexus S, its the problem with the new Nexus S. But I think its not the case now since you have it and it works fine.
Mine is the i9023 like yours, but I had gri40 pre installed.
I unlocked the bootloader, flashed clockworkmod, and then I used superboot to get root, and it all worked just fine.
Maybe gri54 is the problem.
Hmm, that might be the case.
I, too, have the new Nexus S model with 2.3.3 GRI54, and had it rooted within minutes. But as noted in the other thread, several people are having issues with the cache not working.
I flashed GRI54 on my I9020T with Odin, and I have no problems.
Odin works fine because it returns you to stock. I used Odin too because installation of custom firmware failed and I got temporarily 'bricked'
The main thing is I want to install custom firmware successfully so I need to solve the cache error.
Bumping this as many new sets in Singapore are on GRI54, so I hope someone is able to solve this problem.
Vulpix said:
Bumping this as many new sets in Singapore are on GRI54, so I hope someone is able to solve this problem.
Click to expand...
Click to collapse
Try this, it worked for me and suboxide, at least. http://forum.xda-developers.com/showpost.php?p=12244497&postcount=26
Vulpix said:
Bumping this as many new sets in Singapore are on GRI54, so I hope someone is able to solve this problem.
Click to expand...
Click to collapse
it's solved liao with a newer CWM xtracted from latest CM7 source
Yup, temporarily solved liao. Hope the official clockworkmod recovery gets updated to fix this problem too.
navlem said:
Yup, temporarily solved liao. Hope the official clockworkmod recovery gets updated to fix this problem too.
Click to expand...
Click to collapse
ahhh another sgrean
Great, managed to root my i9023 too!
An update to this issue. Apparently the recovery needs "new" recovery kernel for it to work on the i9023 Nexus S.
The CWM mod has been updated to 3.0.2.4 and the modder has released 2 versions to the public so you can update your recovery and use the right one for your phone.
http://forum.xda-developers.com/showthread.php?t=988686
I haven't try the new version yet but will try later tonight. Hope those who try it first give some comments if there is any problems with the new version
navlem said:
An update to this issue. Apparently the recovery needs "new" recovery kernel for it to work on the i9023 Nexus S.
The CWM mod has been updated to 3.0.2.4 and the modder has released 2 versions to the public so you can update your recovery and use the right one for your phone.
http://forum.xda-developers.com/showthread.php?t=988686
I haven't try the new version yet but will try later tonight. Hope those who try it first give some comments if there is any problems with the new version
Click to expand...
Click to collapse
boots fine into recovery without the cache errors
yet to do any flashing
Hi how can I flash that? Using fastboot? I'm on a Mac it should be fine right? Also I can't seem to download the file. We should be getting the i9023 ver right? Hope the file won't be taken off.
Sent from my Nexus S using XDA App
noobhero said:
boots fine into recovery without the cache errors
yet to do any flashing
Click to expand...
Click to collapse
That sounds really good!
Sent from my Nexus S using Tapatalk
dash7869 said:
Hi how can I flash that? Using fastboot? I'm on a Mac it should be fine right? Also I can't seem to download the file. We should be getting the i9023 ver right? Hope the file won't be taken off.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yup, flash that using fastboot. Use the i9023 version if you are using the i9023 Nexus S.
Sent from my Nexus S using Tapatalk
I followed the instructions on the first post of this thread, but when I went to restart, my tablet wouldn't get past the "Galaxy Tab 2" splash screen. Whatever it told me to do with the kernel or whatever must've caused the problem. I didn't have CWM at the time. I then followed this thread to try to root it. So, I have CWM if that helps, and my tablet is very likely rooted. But I still can't get past the splash screen. Any help would be greatly appreciated, and since I can get to download and CWM, I don't think it's bricked (although, I'm not entirely sure what "bricked" means, software/hardware wise).
Thanks in advance
EDIT: I have a Samsung Galaxy Tab 2 7.0" GT-P3113 running Android 4.0.4
yoharnu said:
I followed the instructions on the first post of this thread, but when I went to restart, my tablet wouldn't get past the "Galaxy Tab 2" splash screen. Whatever it told me to do with the kernel or whatever must've caused the problem. I didn't have CWM at the time. I then followed this thread to try to root it. So, I have CWM if that helps, and my tablet is very likely rooted. But I still can't get past the splash screen. Any help would be greatly appreciated, and since I can get to download and CWM, I don't think it's bricked (although, I'm not entirely sure what "bricked" means, software/hardware wise).
Thanks in advance
EDIT: I have a Samsung Galaxy Tab 2 7.0" GT-P3113 running whatever version of Android that Kies gave me
Click to expand...
Click to collapse
If it were me, I'd load the adb drivers and see if I could get into an adb shell. This would do two things. First, it would let you get a logcat which might tell us what happened. Second, it would let you do things to fix whatever seemed to be the problem. If it is the kernel, this probably won't work, but if it is something else it should. You can get into a shell from CWM but that won't get you a logcat of the problem.
If you have CWM have you tried doing a complete wipe from the CWM menu?
yoharnu said:
I followed the instructions on the first post of this thread, but when I went to restart, my tablet wouldn't get past the "Galaxy Tab 2" splash screen. Whatever it told me to do with the kernel or whatever must've caused the problem. I didn't have CWM at the time. I then followed this thread to try to root it. So, I have CWM if that helps, and my tablet is very likely rooted. But I still can't get past the splash screen. Any help would be greatly appreciated, and since I can get to download and CWM, I don't think it's bricked (although, I'm not entirely sure what "bricked" means, software/hardware wise).
Thanks in advance
EDIT: I have a Samsung Galaxy Tab 2 7.0" GT-P3113 running whatever version of Android that Kies gave me
Click to expand...
Click to collapse
I had this happen to me today. I got a new P3113 because I had a dead pixel. Anyway, my new one came with 4.0.3 and immediately wanted to update to 4.0.4. After this, I used Odin to flash cwm, and was immediately stuck in a boot loop. I checked my source again and saw that there was a new file to flash, and sure enough that did it. I was so worried that I screwed up my new tab, but it works now. My counter now reads 2 flashes.
I used this guide and got the latest espressowifi image:
http://rootzwiki.com/topic/25228-how-to-rooting-gt-p3113-step-by-step-updated-07182012/
Sent from my GT-P3113 using Tapatalk 2
Dralanmage said:
I had this happen to me today. I got a new P3113 because I had a dead pixel. Anyway, my new one came with 4.0.3 and immediately wanted to update to 4.0.4. After this, I used Odin to flash cwm, and was immediately stuck in a boot loop. I checked my source again and saw that there was a new file to flash, and sure enough that did it. I was so worried that I screwed up my new tab, but it works now. My counter now reads 2 flashes.
I used this guide and got the latest espressowifi image:
Sent from my GT-P3113 using Tapatalk 2
Click to expand...
Click to collapse
Thanks. But where can I get the latest version of espressowifi?
EDIT: I tried espressowifi-recovery-5-18.tar.md5, but that didn't work. I think the problem has something to do with the PIT file I flashed, but I'm not sure. Also, I have access to adb now, and logcat just spits out a big stream of stuff. Should I upload it?
EDIT2: Fixed it with ueblg5_espressowifi_recovery.tar.md5. Thanks to both of you!
yoharnu said:
Thanks. But where can I get the latest version of espressowifi?
EDIT: I tried espressowifi-recovery-5-18.tar.md5, but that didn't work. I think the problem has something to do with the PIT file I flashed, but I'm not sure. Also, I have access to adb now, and logcat just spits out a big stream of stuff. Should I upload it?
EDIT2: Fixed it with ueblg5_espressowifi_recovery.tar.md5. Thanks to both of you!
Click to expand...
Click to collapse
Awesome! That was what fixed it for me too. It really sucked to bootloop my device about 20 minutes after opening it and not see a way out! I'm glad you got yours working!
Sent from my GT-P3113 using Tapatalk 2
First, if you're stuck in a bootloop, try accessing the recovery mode then wipe data, if this doesn't work, try getting into download mode and flash a firmware file (from sammobile.com or anywhere else)
i have a motorola atrix 2 at&t(MB865).my phone was 2.3.6
1. I try to flash this firmware 5.5.1-EDEM-28-37-MEARET_cfc.xml.zip from this site http://sbf.droid-developers.org/edison/list.php with rsd.at 7/20 rsd was writting fail.i tried again with same result.after this my phone had problem with boot.the only method for boot was "vol down"+"vol up"+"power" and after i was pressing "Normal powerup".after all these my phone booted normal and worked normal.
2.after i flashed the Blur_Version.55.13.25.MB865.ATT.en.US.zip (ics) from this http://forum.xda-developers.com/showthread.php?t=1779968 and my phone was working normal but with the same problem with the boot.
3.after i tried to use this utillity http://forum.xda-developers.com/showthread.php?t=1805975 .this process had some failure and after this my phone is unable to boot.
with "vol down"+"vol up"+"power" i can choose normal power up, but phone stucks at boot image.in addition i can choose recovery and phone boots at recovery mode.i choose to update from sd with this file Blur_Version.55.13.25.MB865.ATT.en.US.zip but my phone writes that its unable to flash this.
4.after i try to flash InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip with rsd.the rsd wrote fail at 3/20 in addition i use the replace.zip with the same result.
5.after i try again the 3rd step with same results.
can anyone help me?
This whole mess started when you tried to flash MEARET firmware on your AT&T phone. NEVER mix firmware!
And trying recovery at this point is not going to work, as the ICS zip is just a large patch file for 2.3.6. And since it failed on the fxz, a portion of your system is missing so ICS won't install. You need to fxz back.
What step is the script falling at? A screenshot would be helpful.
And for the future, please post questions in the Q&A form.
Sent from my SAMSUNG-SGH-I727 using xda premium
you mean at 3rd step?
sorry.please move this thread at q&a
Yes the script from step three is what's going to save you here.
But we need to know where it's failing at.
Sent from my SAMSUNG-SGH-I727 using xda premium
i can see that problem is with cbt, recovey and cdrom partition.
Uh oh.
Which ICS version did you install? Please show need the thread.
I need to know which leak it was.
Sent from my SAMSUNG-SGH-I727 using xda premium
Blur_Version.55.13.25.MB865.ATT.en.US.zip
Well I hate to tell you man. But you are soft bricked until we find an fxz for ICS.
Recovery and cdrom are failing because cdt.bin isn't flashing. And we haven't found a fix for this yet.
Although the strange thing is that this shouldn't be happening on the first leak... but it is...
So you're bricked mate.
Sent from my SAMSUNG-SGH-I727 using xda premium
ok, i will wait.
thanks.
but please explain to me.i had a motorola a1200 and a siemens sx1.when i flashed a firmware, all the flash memory erased and new data wrote at flash.if i had bootloader, all was fine.the only method to brick a phone was to replace the battery when flash the bootloader(or flash false bootloader).
at A2, why when i write a new bootloader and new mbr(and partition table?) is necessary to flash the same or newer edition of firmware?this is because bootloader is locked?
i thought when i flash a new firmware, all the flash memory erased and writes new data(at the begining the bootloader, after mbr with partition table, after the image(i think this is the kernel of linux) and all other the data)
macnick said:
i have a motorola atrix 2 at&t(MB865).my phone was 2.3.6
1. I try to flash this firmware 5.5.1-EDEM-28-37-MEARET_cfc.xml.zip from this site http://sbf.droid-developers.org/edison/list.php with rsd.at 7/20 rsd was writting fail.i tried again with same result.after this my phone had problem with boot.the only method for boot was "vol down"+"vol up"+"power" and after i was pressing "Normal powerup".after all these my phone booted normal and worked normal.
2.after i flashed the Blur_Version.55.13.25.MB865.ATT.en.US.zip (ics) from this http://forum.xda-developers.com/showthread.php?t=1779968 and my phone was working normal but with the same problem with the boot.
3.after i tried to use this utillity http://forum.xda-developers.com/showthread.php?t=1805975 .this process had some failure and after this my phone is unable to boot.
with "vol down"+"vol up"+"power" i can choose normal power up, but phone stucks at boot image.in addition i can choose recovery and phone boots at recovery mode.i choose to update from sd with this file Blur_Version.55.13.25.MB865.ATT.en.US.zip but my phone writes that its unable to flash this.
4.after i try to flash InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID28 5.zip with rsd.the rsd wrote fail at 3/20 in addition i use the replace.zip with the same result.
5.after i try again the 3rd step with same results.
can anyone help me?
Click to expand...
Click to collapse
Use rsdlite and flash the Asian or Chinese stock firmware worked for me when I had this issue now I'm running 4.1.1 cm10 jb and its awesome!
If this works for you hit my thanks button
P.s phone must be in fast boot mode
Sent from my MB865 using XDA Premium HD app
Code:
whiteboi-hakz
can you tell to me which firmware you mean? and where i can find.
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
macnick said:
Code:
whiteboi-hakz
can you tell to me which firmware you mean? and where i can find.
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
Click to expand...
Click to collapse
http://sbf.droid-developers.org/edison/list.php
There is the firmware you wanted dude
Download retail Chinese
Sent from my MB865 using XDA Premium HD app
macnick said:
Code:
Fall of Enosis
i forget to tell you that i did the ics ota update from at&t.
so maybe i have the same problem with others...
Click to expand...
Click to collapse
If you did the OTA ICS update you WILL NOT be able to flash the FXZ back. We have no way out of this right now. And if you are bootlooping or stuck on the splash screen then you are bricked. Sorry mate.
Please read these threads:
http://forum.xda-developers.com/showthread.php?t=1897042
http://forum.xda-developers.com/showthread.php?t=1882335
whiteboi-hakz said:
http://sbf.droid-developers.org/edison/list.php
There is the firmware you wanted dude
Download retail Chinese
Sent from my MB865 using XDA Premium HD app
Click to expand...
Click to collapse
Whiteboi, thanks for your consideration of others but PLEASE, research before you try to help others. For one thing, he is on an MB865 AT&T phone and therefore MUST download the firmware for an AT&T phone. The international versions of the A2 are completely different, including radio, WiFi and the like. NEVER mix firmwares.
Also, he already flashed international firmware which is what got him into this predicament in the first place. He also installed the OTA update for ICS for which there is NO GOING BACK. Read the threads I gave him and educate yourself man.
I applaud you generosity, but if he wasn't already bricked, your advice would have surely/quite possibly bricked him. Be careful man.
Read, read, read!
Fall of Enosis said:
If you did the OTA ICS update you WILL NOT be able to flash the FXZ back. We have no way out of this right now. And if you are bootlooping or stuck on the splash screen then you are bricked. Sorry mate.
Please read these threads:
http://forum.xda-developers.com/showthread.php?t=1897042
http://forum.xda-developers.com/showthread.php?t=1882335
Whiteboi, thanks for your consideration of others but PLEASE, research before you try to help others. For one thing, he is on an MB865 AT&T phone and therefore MUST download the firmware for an AT&T phone. The international versions of the A2 are completely different, including radio, WiFi and the like. NEVER mix firmwares.
Also, he already flashed international firmware which is what got him into this predicament in the first place. He also installed the OTA update for ICS for which there is NO GOING BACK. Read the threads I gave him and educate yourself man.
I applaud you generosity, but if he wasn't already bricked, your advice would have surely/quite possibly bricked him. Be careful man.
Read, read, read!
Click to expand...
Click to collapse
Dude it works and he can then reflash his fw so what's the big deal the one I bricked was at&t non international and that method worked great but I'll take your advice man
Sent from my MB865 using XDA Premium HD app
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
macnick said:
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
Click to expand...
Click to collapse
OK well was worth a try I guess ay try his method and let's us know
Sent from my MB865 using XDA Premium HD app
macnick said:
i tried your method without any Success.
so "fall of enosis" is right.maybe the solve of the problem is to find an ics firmware(from at&t????)
Click to expand...
Click to collapse
Yeah man, if you OTA'd to ICS then I can almost guarantee it will fail at step 3 of the flash process which is the cdt.bin. If you are using the script it will also fail on the recovery portion and the cdrom portion. These are both because of the cdt.bin As of right now, we have no fix for this. Once again, this is the reason we are recommending people to ONLY use the first leak, and not OTA to ANYTHING unless it's 2.3.6 GB. Once again, reference the links I sent you.
You're bricked sir.
Until we find an ICS fxz. Which might be A LONG TIME.
Time to get a replacement/new phone.
Fall of Enosis said:
Yeah man, if you OTA'd to ICS then I can almost guarantee it will fail at step 3 of the flash process which is the cdt.bin. If you are using the script it will also fail on the recovery portion and the cdrom portion. These are both because of the cdt.bin As of right now, we have no fix for this. Once again, this is the reason we are recommending people to ONLY use the first leak, and not OTA to ANYTHING unless it's 2.3.6 GB. Once again, reference the links I sent you.
You're bricked sir.
Until we find an ICS fxz. Which might be A LONG TIME.
Time to get a replacement/new phone.
Click to expand...
Click to collapse
Thanked you as earned it man
Sent from my MB865 using XDA Premium HD app
After using all-in-one toolkit to have my Telus phone bootloader unlocked and installed TWRP, i flashed the wrong ROM and boot.img(the one for HOX International, instead of the one for AT&T / Rogers). now i'm stuck with only bootloader and TWRP. and in Recovery mode it always shows the error "unable to mount /sdcard"
after a few hours, i've tried a few things and nothing worked so far. totally in lost now...
i've tried re-locked and flash factory RUU, ADB sideload a customized ROM, nothing worked.
currenlty when in fastboot, fastboot can see the device, but adb can't see the device at all.
Any help and thoughts will be greatly appreciated!
when running the following RUU,
RUU_Evita_UL_TELUS_WWE_1.91.661.4_Radio_0.18a.32.09.01_2_10.94.32.20L_release_266645_signed.exe
it's checking current image version, and shows 3.17.661.2...
Team Nocturnal has a fix for corrupt/unmountable sdcard. I posted for someone else yesterday with the same problem here: http://forum.xda-developers.com/showthread.php?p=39119164. Read carefully and good luck!
Sent from my One X using Tapatalk 2
jeffwyeh said:
Team Nocturnal has a fix for corrupt/unmountable sdcard. I posted for someone else yesterday with the same problem here: http://forum.xda-developers.com/showthread.php?p=39119164. Read carefully and good luck!
Sent from my One X using Tapatalk 2
Click to expand...
Click to collapse
Thanks a lot, Jeffwyeh. i saw that thread, just didn't realize this might be the issue.
I'll take a look and provide update later.
this is just magical!
now i'm back on track!
Thank you very much for your help!
Glad to hear it!
Sent from my One X using Tapatalk 2
So I've been working on this all night last night and all day today.
The issue- phone will boot, get to the red Verizon boot screen, sit there for approximately 45-60 seconds, then go to the lock screen. Within a couple of seconds, Then a message pops up that says process com.android.phone has stopped, then the phone reboots.
What I've tried- flashing various Vralec boot strings through Odin 3.2 and 1.3. Also tried five different stock ROMs and a CF Auto Root, in the hopes unlocking the bootloader would allow me to get a ROM to flash. Each and every one of these things has had an AUTH fail in Odin. Can anyone help me please?
I've also googled stuck red verizon screen, verizon s3 boot loop, process com.android.phone has stopped. None of the solutions I've found have been helpful, and are usually what led to the actions tried above. I believe I've encountered this before, but I checked my post history and wasn't able to find a thread, so I assume I found the solution on my own the last time.
Any assistance would be greatly appreciated!
What software version are you running? What baseband?
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
What software version are you running? What baseband?
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
This is a warranty replacement from Verizon. Since I can't get it to boot, is there an alternative method to find those versions?
I have another S3, replaced less than a month ago, so I would assume they are the same software version and basebands, and that one is running 4.4.2 and I535OYUDNE1
The soft bricked, boot loop, S3 belongs to my girlfriend.
Flashing other ROMs on the S3 4.3 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
I hope that helps.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
Flashing other ROMs on the S3 4.4 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Flashing the ROMS through Odin failed every time, and none of that was done until AFTER the phone went in to a boot loop. It was already soft bricked, so I tried various different methods. Now I know, for future reference, that attempting to flash ROMs without unlocking the bootloader will brick it. Good to know.
If I can work around the Odin failed authorization, I believe I can flash a stock ROM to the phone and be all right, OR if someone can tell me how to unlock the bootloader, I should be able to flash a custom ROM, correct? It seems that the boot partition permissions were changed and have now affected the boot process, from what I've been reading.
Hybridnoob said:
Flashing other ROMs on the S3 4.3 and newer will brick it. The bootloader was never unlocked. I'll try to find the thread describing the issue and post it here.
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:37 PM ----------
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my SCH-I535 using Tapatalk
---------- Post added at 01:40 PM ---------- Previous post was at 01:40 PM ----------
I hope that helps.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Reading up on your link now, will let you know result. Thank you!
edit: ok, I looked at the download mode accessible link, and that is one I'd tried before. Flashed the ALL I535 .tar and ran in to the auth fail message on odin. Going to try the other method now.
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I got towelroot to work to get my S3 to be able to install SuperSU and then Titanium Backup, but haven't found a bootloader unlock either. So, the phone is pretty much bricked?
jester369 said:
I got towelroot to work to get my S3 to be able to install SuperSU and then Titanium Backup, but haven't found a bootloader unlock either. So, the phone is pretty much bricked?
Click to expand...
Click to collapse
Bricked no, if your able to install apps it's far from bricked. He is correct however once the bootloader is locked your pretty much stuck. Replacements directly from verizon are coming back with 4.4.2 installed.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
As I just stated in the post above yours if you can install apps the phone isn't bricked. Bootloader unlocking on the S3 with 4.3 or 4.4 is merely a possibility but probably unlikely
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Hybridnoob said:
No one has been able to unlock the bootloader since 4.3. I doubt anyone's really trying now because the phone is older. Sorry man.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
All right, tried the recover from computer, it's to recover a bricked bootloader. My bootloader isn't bricked, it's the actual ROM that's non functional. So that didn't help. Just need a stock ROM to flash to the phone, can still get to download mode, which connects to Odin, no problem, can also get to stock recovery, Volume Up, Menu, power. Just need a stock ROM that works, or a way to get whatever authorization Odin or the phone wants in order to flash a boot chain and stock ROM. (I do know now not to flash a custom ROM, thank you for that!)
ShapesBlue said:
Bricked no, if your able to install apps it's far from bricked. He is correct however once the bootloader is locked your pretty much stuck. Replacements directly from verizon are coming back with 4.4.2 installed.
Sent from my SCH-I535 using Xparent ICS Tapatalk 2
Click to expand...
Click to collapse
Sorry, some clarification. I have TWO S3s, MY S3 is fine, and can install apps. The girlfriend's S3 is soft bricked and in a boot loop. Bootloader is fine, download mode is fine. Just hangs on red Verizon boot screen, when it gets to lock screen says process com.android.phone has stopped and reboots.
Hybridnoob said:
Unless you can find a fully stock ROM to flash via Odin, you may be in trouble. Unlocking the bootloader isn't an option. Without seeing your phone, I won't say it's bricked though.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Been trying to find a fully stock ROM and been unsuccessful. Any I've found have failed in Odin and failed to flash in stock recovery mode, something about a certificate failure.
jester369 said:
Sorry, some clarification. I have TWO S3s, MY S3 is fine, and can install apps. The girlfriend's S3 is soft bricked and in a boot loop. Bootloader is fine, download mode is fine. Just hangs on red Verizon boot screen, when it gets to lock screen says process com.android.phone has stopped and reboots.
Click to expand...
Click to collapse
I definitely would not call that soft bricked. Can you get into recovery and try clearing cache and reboot? Worst case, factory reset from recovery and you should be good to go.
Sent from my SCH-I535 using Tapatalk
Hybridnoob said:
I definitely would not call that soft bricked. Can you get into recovery and try clearing cache and reboot? Worst case, factory reset from recovery and you should be good to go.
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
I can get in to recovery, I've tried clearing cache, factory reset, no dice. Exact same thing.
have you tried using odin or kies to just flash the stock NE1 4.4.2? youll have to reroot with towelroot afterwards but atleast the phone will be functional. as for the bootloader, sounds like its locked anyways so it wont be no worse than the shape youre in already.
4.4 and 4.3 Sticky Roll-Up Thead
http://forum.xda-developers.com/showthread.php?t=2639337
TouchWiz 4.4 Download List
http://forum.xda-developers.com/gal...4-download-list-7-10-14-t2812189/post54062704
VRUDNE1 (Android 4.4.2 - Kit Kat) No-Wipe Factory Image
http://forum.xda-developers.com/showthread.php?t=2795659
-somebody- said:
have you tried using odin or kies to just flash the stock NE1 4.4.2? youll have to reroot with towelroot afterwards but atleast the phone will be functional. as for the bootloader, sounds like its locked anyways so it wont be no worse than the shape youre in already.
Click to expand...
Click to collapse
I have tried that, I believe I haven't been able to find a stock 4.4.2 ROM though. I'm fine with rebooting and re rooting, that's not my concern, even if I can't root, I don't care about that. Could you point me to a solid stock ROM image?
The images I've tried, numerous labeled stock ROMs, and, out of desperation last night, two custom ROMs. Through either recovery mode, or Odin, all failed, through recovery it was a certificate error, and through Odin it was an authorization error. AUTH FAIL, specifically.
jester369 said:
I have tried that, I believe I haven't been able to find a stock 4.4.2 ROM though. I'm fine with rebooting and re rooting, that's not my concern, even if I can't root, I don't care about that. Could you point me to a solid stock ROM image?
The images I've tried, numerous labeled stock ROMs, and, out of desperation last night, two custom ROMs. Through either recovery mode, or Odin, all failed, through recovery it was a certificate error, and through Odin it was an authorization error. AUTH FAIL, specifically.
Click to expand...
Click to collapse
that last link i believe is the actual tar file for NE1 if i remember correctly, i used kies when i updated mine and i didnt encounter any errors. did you delete the .md5 so it was just .tar (not .tar.md5) before trying it in odin? i know most people prefer odin over kies but if youre having this many problems kies is worth a shot.
worst case i can upload the one i have
-somebody- said:
that last link i believe is the actual tar file for NE1 if i remember correctly, i used kies when i updated mine and i didnt encounter any errors. did you delete the .md5 so it was just .tar (not .tar.md5) before trying it in odin? i know most people prefer odin over kies but if youre having this many problems kies is worth a shot.
worst case i can upload the one i have
Click to expand...
Click to collapse
I will try that and report back. Thank you!