Coming from a DX, the process to root / flash on the galaxy doesn't seem that much different. Although, there seems to be greater risk for issues around imei information, etc....
So, I've read about everything I can on the forums, trying to make sure I understand all of the ins and outs and I'm starting to feel pretty comfortable with the process, however I would like someone to just confirm that i've got everything correct......
Based on this guide ( [GUIDE][VZW Edition]How to root your Galaxy SIII & More!(ROMs/CWM/Stock)) , this is how I understand things if somone could either comfirm or correct my information I would greatly appreciate it!
1. using section 2 in the guide for windows users, I use the RootDebugFS bat file to root the phone.
2. After rooting, and prior to unlocking the boot loader, I backup my IMEI using Comprehensive IMEI/EFS Backup method listed in the guide.
3. From here I can unlock the bootloader and install CWM reovery.
4. At this point, back in the droid X world I would take a back up of my system so I have a semi - stock image to go back to.
5. Now I can download any of the different custom roms listed and follow the instructions in the OP to flash that rom.
Going back to stock.
1. Should I need to go back to Stock, I would just use the ODIN tool to flash one of the stock images.
Again, If someone could just let me know if i've missed anything or if I'm WAY off base I would appreciate it.
Thanks again, and I love the forum and the community!
yep you got it correct...also if you have any questions feel free to post in my thread!
droidstyle said:
yep you got it correct...also if you have any questions feel free to post in my thread!
Click to expand...
Click to collapse
Thank you very much, I really appreciate it!! Can't wait to get started.
I did try to post in your thread, but apparently I'm to much of a NOOB to do so LOL!
nickjensz said:
Thank you very much, I really appreciate it!! Can't wait to get started.
I did try to post in your thread, but apparently I'm to much of a NOOB to do so LOL!
Click to expand...
Click to collapse
I've got 2 more questions....
1. I tried to flash the synergy backup for the IMEI/EFS using stock recovery as per the instructions and I got a message that the signatures or something like that wasn't correct and it was aborted.... Thoughts?
2. As far as custom recoveries go.... I'm used to CWM, but I've heard a lot of good things about TWRP. Which would you recommend?
nickjensz said:
I've got 2 more questions....
1. I tried to flash the synergy backup for the IMEI/EFS using stock recovery as per the instructions and I got a message that the signatures or something like that wasn't correct and it was aborted.... Thoughts?
2. As far as custom recoveries go.... I'm used to CWM, but I've heard a lot of good things about TWRP. Which would you recommend?
Click to expand...
Click to collapse
#1-Have never had to use it as I have never lost IEMI. May be a way to disable signature check in recovery. Can do permanent fix with terminal emulator.
Type:
su (enter)
reboot nvbackup (enter)
#2- Recovery is personal choice. I have been using TWRP since pre-order release and never had a bad flash or backup. As far as I'm concerned it rocks. Easier navigation and looks good. Some prefer CWM. To each their own. Don't recommend flashing via Rom Manager. Flash straight from recovery.
prdog1 said:
#1-Have never had to use it as I have never lost IEMI. May be a way to disable signature check in recovery. Can do permanent fix with terminal emulator.
Type:
su (enter)
reboot nvbackup (enter)
#2- Recovery is personal choice. I have been using TWRP since pre-order release and never had a bad flash or backup. As far as I'm concerned it rocks. Easier navigation and looks good. Some prefer CWM. To each their own. Don't recommend flashing via Rom Manager. Flash straight from recovery.
Click to expand...
Click to collapse
Thank you very much for the advice! I really appreciate it!
signature verification error means you were in stock blue recovery and not cwm recovery.
droidstyle said:
signature verification error means you were in stock blue recovery and not cwm recovery.
Click to expand...
Click to collapse
Thanks DroidStyle Wouldn't have gotten this far without the help! Finally got CWM on and flashed i that way and it worked great!
Speaking of CWM though.... in EZRecovery, do I need to hit "FLASH" and then "Reboot" recovery everytime I want to go into CWM or TWRP? If I don't it just takes me to stock recovery.
nickjensz said:
Thanks DroidStyle Wouldn't have gotten this far without the help! Finally got CWM on and flashed i that way and it worked great!
Speaking of CWM though.... in EZRecovery, do I need to hit "FLASH" and then "Reboot" recovery everytime I want to go into CWM or TWRP? If I don't it just takes me to stock recovery.
Click to expand...
Click to collapse
you should only need to flash cwm or twrp once, then reboot recovery to get into cwm. im not sure why its not sticking but it should.
Related
I am new to this posting and asking questions. I have a xoom and rooted it and updated it with 3.1 and then I went and updated it with the new rom which came out the other day. I did something studpid and didn't wait for the resolution to the sdcard not being seen after flashing the new deodex rom. I looked on the kernal manager and when I what I thought was the latest kernal I decided to flash it. I now can only get to recovery mode and I don't want to make another mistake. Can someone tell me if I can safely do a wipe data/factory reset? Will that get me back so I can flash the deodex rom back? You dev guys are really awesome and I really appreciate all of your work. Thank you for your support.
razor532 said:
I am new to this posting and asking questions. I have a xoom and rooted it and updated it with 3.1 and then I went and updated it with the new rom which came out the other day. I did something studpid and didn't wait for the resolution to the sdcard not being seen after flashing the new deodex rom. I looked on the kernal manager and when I what I thought was the latest kernal I decided to flash it. I now can only get to recovery mode and I don't want to make another mistake. Can someone tell me if I can safely do a wipe data/factory reset? Will that get me back so I can flash the deodex rom back? You dev guys are really awesome and I really appreciate all of your work. Thank you for your support.
Click to expand...
Click to collapse
If you can get to recovery, just re-flash the rom, it includes its own kernel.
Ok I will and let you know if I am successful. Thank you
I tried to use recovery but my xoom won't see the sd card. I have adb running but really am afraid to use it without some help. Don't want to brick my xoom. I have the kernal zip but don't 1.4.4 and thought if I could flash the kernal to my xoom that would maybe fix it. I read somewhere that you shouldn't flash a zip file, so I don't know what to do. any help would be appreciated. Thank you
razor532 said:
I tried to use recovery but my xoom won't see the sd card. I have adb running but really am afraid to use it without some help. Don't want to brick my xoom. I have the kernal zip but don't 1.4.4 and thought if I could flash the kernal to my xoom that would maybe fix it. I read somewhere that you shouldn't flash a zip file, so I don't know what to do. any help would be appreciated. Thank you
Click to expand...
Click to collapse
Please don't flash any xip file through adb! Why not go into RomManager app and look for an earlier version of recovery, maybe 3.0.2.5, and flash that. A good recovery should allow you to flash from your sdcard through clockwork mod recovery.
I can't get to the rom manager app. Am I missing something? The OS won't boot up and I only have version 4 of the clockwork recovery. What should I do?
razor532 said:
I can't get to the rom manager app. Am I missing something? The OS won't boot up and I only have version 4 of the clockwork recovery. What should I do?
Click to expand...
Click to collapse
There is your problem, you did not read the warnings...DO NOT USE CWM 4.
Grab Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT from this post.
http://forum.xda-developers.com/showthread.php?t=1074979
Fastboot flash it, if you don't know how read the post or read my sig. Once you have a working recovery, try my post above.
bwcorvus said:
There is your problem, you did not read the warnings...DO NOT USE CWM 4.
Grab Recovery Image (solarnz-R4c-100611-1150) FLASHED THROUGH FASTBOOT from this post.
http://forum.xda-developers.com/showthread.php?t=1074979
Fastboot flash it, if you don't know how read the post or read my sig. Once you have a working recovery, try my post above.
Click to expand...
Click to collapse
Flash the .img file as bwcorvus says, not the .zip.
Take your time.
OK, Thank you very much,,, I will be more careful in the future. I am back up and running the new rom with an older recovery. That taught me a good lesson never to install an earlier version of a kernal and never to try and flash a .zip file from adb. Thank you for the instructions. Is there a book for "adb for dummies"? My name should be in it...
thank you again...
Np, glad you got it working. And guess what? You got to learn something .
razor532 said:
OK, Thank you very much,,, I will be more careful in the future. I am back up and running the new rom with an older recovery. That taught me a good lesson never to install an earlier version of a kernal and never to try and flash a .zip file from adb. Thank you for the instructions. Is there a book for "adb for dummies"? My name should be in it...
thank you again...
Click to expand...
Click to collapse
There is actually an ADB tutorial somewhere on this site...seriously, do a search. It had a lot of great information. I like to know what I'm doing...it makes me more nervous to just blindly follow instructions with something like this, but I'm still mostly blind (sigh).
So here's the deal. I'm running CM9Alpha13. And while I love having my phone rooted and playing around with it, I was really only interested in getting ICS for my phone. No I know I'll miss Francisco.Franco's kernels and I'll miss Koush's awesome ROMs but I just really want a stable ICS.
So my question is how long before I can root my ICS if I do the official downgrade to GB and Upgrade to ICS?
Any guestimate would be great!
Thanks in advance.
Jon
I am sure it wont take long...just give the devs a day or so to play with things and get everything worked out.
Sent from my Nexus S using Tapatalk
I'm wondering about this too... I need a stable one but I need it to be rooted too...
http://www.megaupload.com/?d=S67I9Q0L
EDIT: flashable with CWM.
+ read this: http://forum.xda-developers.com/showpost.php?p=20395808&postcount=25
Chamb' said:
http://www.megaupload.com/?d=S67I9Q0L
Click to expand...
Click to collapse
This is a su-update.zip file flashable with CWM
it did the trick for me, just simply flashed it and now have working root
Anyone else confirmed this working?
EDIT: Oh, and mirrors please?
Read this: http://forum.xda-developers.com/showpost.php?p=20395808&postcount=25
Chamb' said:
http://www.megaupload.com/?d=S67I9Q0L
EDIT: flashable with CWM.
+ read this: http://forum.xda-developers.com/showpost.php?p=20395808&postcount=25
Click to expand...
Click to collapse
rooted~
but superuser fc...
FLyTula said:
So my question is how long before I can root my ICS if I do the official downgrade to GB and Upgrade to ICS?
Click to expand...
Click to collapse
While we're at it, is there a downgrading/upgrading guide somewhere?
fromthestars said:
This is a su-update.zip file flashable with CWM
it did the trick for me, just simply flashed it and now have working root
Click to expand...
Click to collapse
Confirmed that this worked on Google issued phone (same as T-Mobile version). The following is the order I used to come from CM9 Alpha 11:
1. Backup using Titanium, reboot to recovery.
2. Use CWM to flash stock 2.3.6.
3. Use CWM to flash stock ICS 4.0.3.
4. Wipe all user data.
5. Install the linked superuser through CWM (I had previous tried older and newer versions, which did not work).
6. Reboot phone, go through setup, download Titanium, and restore. Phone is definitely rooted (otherwise Titanium is unusable). I did not try to update the su binaries and will avoid doing so.
any way to root with something like superoneclick?
I'd like to avoid flashing custom stuff on it. just need root.
xd4d3v said:
any way to root with something like superoneclick?
I'd like to avoid flashing custom stuff on it. just need root.
Click to expand...
Click to collapse
Then fastboot boot recovery and flash the latest su zip. Even if you flashed the custom recovery it would be overwritten when you boot up the os.
I'm very new to android and have been using Clockworkmod Recovery basically since day 3 or 4 since I got my HTC One XL...
I'm just wondering how many of you are using TWRP instead of Clockworkmod Recovery.. and if so, do you recommend me flashing that instead of CWM?
I have no real complaints with CWM and dont mind using the volume keys to navigate. But besides that, are there any real advantages besides the touch interface?? also, can someone post a link where i can find TWRP ?
thanks guys!! I LOVE the community on here!! it's great!!!
also, when people refer to "Touch Recovery" are y'all referring to TWRP ?
trichrome1 said:
I'm very new to android and have been using Clockworkmod Recovery basically since day 3 or 4 since I got my HTC One XL...
I'm just wondering how many of you are using TWRP instead of Clockworkmod Recovery.. and if so, do you recommend me flashing that instead of CWM?
I have no real complaints with CWM and dont mind using the volume keys to navigate. But besides that, are there any real advantages besides the touch interface?? also, can someone post a link where i can find TWRP ?
thanks guys!! I LOVE the community on here!! it's great!!!
also, when people refer to "Touch Recovery" are y'all referring to TWRP ?
Click to expand...
Click to collapse
I personally use twrp I like its setup look and feel and it is a little speedier than cwm when making backups, flashing etc in my opinion. I used cwm on every phone I had except this one x. After twrp was introduced I switched and love it.
Sent from my HTC One X using xda premium
i believe CWM is also touch screen, just no buttons, so you gotta be careful not push a wrong link - but they have conf screen as well.... haven't tried TWRP - would also like to know if it has any advantages... thanks!
will try
eraste said:
I personally use twrp I like its setup look and feel and it is a little speedier than cwm when making backups, flashing etc in my opinion. I used cwm on every phone I had except this one x. After twrp was introduced I switched and love it.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks for the reply,
I'm going to flash twrp and try it out.. see what I think. I'm just enjoying playing with my phone
twrp ?
Can someone point me into the right direction to TWRP..
I can't seem to find a download link anywhere..
and correct command is ..
fastboot flash recovery twrp_file_name.whateverextentionis
?
trichrome1 said:
Can someone point me into the right direction to TWRP..
I can't seem to find a download link anywhere..
and correct command is ..
fastboot flash recovery twrp_file_name.whateverextentionis
?
Click to expand...
Click to collapse
here ya go http://forum.xda-developers.com/showthread.php?t=1677447
All needed info is there or the links provided there to the official page of TWRP
attempting first backup
just backed up my current rom... twrp seems a little more thorough with more options and there's even a progress bar when backing up.
eraste said:
here ya go http://forum.xda-developers.com/showthread.php?t=1677447
All needed info is there or the links provided there to the official page of TWRP
Click to expand...
Click to collapse
Would i able to flash CWM one click again....? did u ever try to go back to CWM....?
ted77usa said:
Would i able to flash CWM one click again....? did u ever try to go back to CWM....?
Click to expand...
Click to collapse
No never went back. Not sure what the process would be to get back to CWM. Dont see why the one click wouldnt work but dont take my word for it dont want to give any wrong information.
eraste said:
No never went back. Not sure what the process would be to get back to CWM. Dont see why the one click wouldnt work but dont take my word for it dont want to give any wrong information.
Click to expand...
Click to collapse
I'm just curious....but so far i have no problem with CWM....if ain't broke don't fix it right.....
trichrome1 said:
just backed up my current rom... twrp seems a little more thorough with more options and there's even a progress bar when backing up.
Click to expand...
Click to collapse
Just FYI... u can't restore ur CWM back up file with TWRP.... it's totally different
process
ted77usa said:
Would i able to flash CWM one click again....? did u ever try to go back to CWM....?
Click to expand...
Click to collapse
to go back to CWM, all you would need to do is place the CWM.img in the fast boot folder, and
go to the dir where u have fastboot files (mine is c:\fastboot ) but i am also running a virtual machine on a mac.. process should be the same since i'm still using windows..
anyways in command prompt.. navigate to c:\fastboot
and then,
fastboot flash recovery CWM.img
(or whatever your clockworkmod recovery image is named)
I haven't tried this, but it's how i originally flashed cwm and it's how i just flashed twrp.... so far it's sweet, a lot more options as well.. don't see myself going back anytime soon. (sorry cwm devs, still love cwm)
trichrome1 said:
to go back to CWM, all you would need to do is place the CWM.img in the root of your sdcard on the phone, and
go to the dir where u have fastboot files (mine is c:\fastboot ) but i am also running a virtual machine on a mac.. process should be the same since i'm still using windows..
anyways in command prompt.. navigate to c:\fastboot
and then,
fastboot flash recovery CWM.img
(or whatever your clockworkmod recovery image is named)
I haven't tried this, but it's how i originally flashed cwm and it's how i just flashed twrp.... so far it's sweet, a lot more options as well.. don't see myself going back anytime soon. (sorry cwm devs, still love cwm)
Click to expand...
Click to collapse
+1. Yea it's easy to flash back and forth between recoveries. Just do it the same way you flash the first one.
cwm twrp incompatibility
ted77usa said:
I'm just curious....but so far i have no problem with CWM....if ain't broke don't fix it right.....
Just FYI... u can't restore ur CWM back up file with TWRP.... it's totally different
Click to expand...
Click to collapse
right, wish I'd known that before. I ended up in bootloops when using twrp to ry and restore a cwm nandroid. luckily, i was able to reflash a beans rom and get it running again, but in the process, I believe I have messed up something. the kernel, bootloader, maybe how the file system is set up. dont mix them up. choose one and stick with it.
Well, I'm pretty sure that one, twrp is simpler, more pretty, more useful, faster, easier.
Also Pretty sure cwm in some cases ruins your phone forever.
Go a head and use cwm though.
TWRP has and official release for the One XL although last time I checked CWM only has a port. I highly suggest using TWRP. It should work better
Sent from my HTC One X using xda premium
Another advantage of TWRP is that the sdcard can be mounted while in recovery mode. I don't think that's supported in CWM.
That may be the case for the htc, the thing is, I am on a verizon samsung galaxy s 3.
I wonder if that makes a difference!?
I was reading elsewhere in these forums that the non kexec kernels ( meaning that the bootloader is actually unlocked) don't work as well on twrp
Sent from my SCH-I535 using xda app-developers app
fritzboyle said:
That may be the case for the htc, the thing is, I am on a verizon samsung galaxy s 3.
I wonder if that makes a difference!?
I was reading elsewhere in these forums that the non kexec kernels ( meaning that the bootloader is actually unlocked) don't work as well on twrp
Click to expand...
Click to collapse
Every device is different, this discussion is about the One X(L). If you want more info on CWM vs. TWRP on the Galaxy S3, head over to the forum for your device. Don't follow the GS3, but would assume that its officially supported by CWM (which makes a huge difference). That is not even the case for the One X. Its not yet officially supported, and the CWM we have is just a port. Although an official version is in testing.
redpoint73 said:
Every device is different, this discussion is about the One X(L). If you want more info on CWM vs. TWRP on the Galaxy S3, head over to the forum for your device. Don't follow the GS3, but would assume that its officially supported by CWM (which makes a huge difference). That is not even the case for the One X. Its not yet officially supported, and the CWM we have is just a port. Although an official version is in testing.
Click to expand...
Click to collapse
I needed help how do.you erase battery history with twrp
Sent from my HTC One XL using xda app-developers app
htcbrazilian said:
I needed help how do.you erase battery history with twrp
Click to expand...
Click to collapse
On the main/home TWRP screen, go Wipe>battery stats.
But battery stats get wiped every time you charge the phone, anyway. There is not benefit to wiping it manually: http://www.xda-developers.com/android/google-engineer-debunks-myth-wiping-battery-stats-does-not-improve-battery-life/
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Make sure you're using a perm root method. and make sure you have the correct updated SU application. My root wouldn't come through because I didn't have the latest SU.
Hopefully I helped.
thispaininmyhead said:
curious if there is something i'm missing here... i've unlocked my bootloader successfully but whenever i fastboot flash a recovery or flash root files in recovery nothing seems to stick... not sure whats going on... i've heard of having to flash recovery everytime on devices with a locked bootloader but i didn't think that would apply here... any help is much appreciated... (this is also my first samsung/nexus device so i'm more familiar with methods used on the EVO line)
Click to expand...
Click to collapse
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Vs Nexus S4G using tapatalk2
Unlocked the boot loader with fast boot commands then flashed superuser.zip with clockwork 3.x.x and twrp 2.2.0 haven't tried flashing any Roms since nothing seems to stick...
Sent from my Nexus S 4G using Tapatalk 2
And Vidal I used the toolkit you linked me to in my last q&a post...
Sent from my Nexus S 4G using Tapatalk 2
vidaljs said:
Hi,
What root method did u use?
What recovery are u using?
What ROM are u flashing?
The more info, the better
Also after looking into the scripts and files in the method with the toolkit it seems none of the files get pushed to the device to begin flashing
Sent from my Nexus S 4G using Tapatalk 2
Click to expand...
Click to collapse
By default, any recovery you flash on the system will be gone by the next reboot. This is a security measure the android os does I think.
1. You can flash a ROM. Anyone. I prefer aokp or cna. That way the recovery sticks (the recovery sticks on all the ROMs besides stock)
OR
P.S. You will need the latest cwm recovery
2. So all you need to do is to flash the recovery of your choice. I would recommend CWM for this short guide. Then once flashed go to the recovery make a backup. Then if it reboots flash the same recovery again. Boot into it and restore that backup. When you restore it and go reboot system now it should come up with a menu saying recovery flash fix (or something around those lines). Hit/navigate to yes and you should get a sticky recovery from there. BTW I have not tried this method.
You cannot blame me for bricking, damaging or done anything to your phone
Hope this helps.
Regards,
UselessSniper001
P.S. I don't know how root isn't sticking. I mean if you have flashed the su is the recovery already well then you are all set to go. Unless you haven't actually flashed the su in the recovery. Then flash the recovery from your PC boot into the recovery and flash the su files in the recovery. Reboot and enjoy. Then follow this guide above. Or follow this link:
http://forum.xda-developers.com/showthread.php?t=875875&page=2
I finally figured out the SU and CWM I was flashing was ancient so I found the newest and they stuck with help of the fix ya mentioned inside CWM... Thanks
Sent from my Nexus S 4G using Tapatalk 2
I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated
melog69 said:
I have a Galaxy Tab 2 VZW and was trying to install the ClearRom, but I guess I forgot to unlock bootloader, so now everytime I turn the tab on I get message statitng " System Software not authorized by Verizon Wireless has been found on your phone."
I have a backup from before I tried installing the ROM but don't know what to do with it
Any help will be appreciated
Click to expand...
Click to collapse
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.
DigitalMD said:
HOw did you make the backup? CWM? If so, then install CMW recovery and do a restore.
Click to expand...
Click to collapse
I tried getting into recovery mode, but I get the following screen everytime, I think I need the Stock Firmware to flash with ODIN but I don't know where to find it.
<iframe src="https://skydrive.live.com/embed?cid=47A1A726F16BDCFD&resid=47A1A726F16BDCFD%212570&authkey=AE3MPZ8PewFeQos" width="180" height="320" frameborder="0" scrolling="no"></iframe>
Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.
MrHyde03 said:
Always, ALWAYS, follow directions exactly how they're laid out.
What you need to do is download the aboot.img to your sd card. Reboot into recovery, ADB Shell into your device (you may need linux for this part as Windows doesn't recognize the device in recovery mode). Once you ADB into recovery, make sure you are root (noted by # instead of $).
Then:
dd if=/sdcard/aboot.img of=/dev/block/mmcblk0p5
reboot download
This should unlock you bootloader so you can get by verizons pesky warning.
We can't see the picture you tried attaching.
Click to expand...
Click to collapse
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother
melog69 said:
I cannot get to recovery mode, only download mode, also ClearRom did not specify that the bootloader, that is why I did not even bother
Click to expand...
Click to collapse
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.
MrHyde03 said:
You'll more than likely have to send it back. There has been no official release of stock firmware, unfortunately (none that I have found at least). In the root thread there are steps 1 - 3 for a reason. 1 - Root, 2 - Unlock and Recovery, 3 - Custom ROM. Always follow directions.
Click to expand...
Click to collapse
Well, thanks guys now I know what to do when it's fixed
melog69 said:
Well, thanks guys now I know what to do when it's fixed
Click to expand...
Click to collapse
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
---------- Post added at 04:04 PM ---------- Previous post was at 03:54 PM ----------
acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
Actually, according to here http://forum.xda-developers.com/showthread.php?t=1885558 you just need download mode to install the stock image and then follow the rest of the steps.
acefsw said:
Maybe try a stock 3100 rom? If the hardware is the same should work, just need to set APN etc.Then reroot, install recovery, install cuztom rom.
Click to expand...
Click to collapse
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.
imnuts said:
DO NOT INSTALL A P3100 ROM. It's not the same hardware (not really even close), so that would only make it worse.
Click to expand...
Click to collapse
I edited the post, read the link, it is for his device
imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.
MrHyde03 said:
imnuts is correct. These devices are extremely different and really does need it's own subforum so people don't keep getting confused. The i705 is closest to the i535 (s3), nearly identical actually.
Click to expand...
Click to collapse
Then wouldn't it be easier to flash an S Rom?
melog69 said:
Then wouldn't it be easier to flash an S Rom?
Click to expand...
Click to collapse
It still wouldn't work. boot, recovery, and system for the s3 are designed for the s3. The hardware is the same, but the software has it's differences. What differences, though, is beyond me.
I have the same issue, this is the first time I've ever "Bricked" a device. Thought I followed the instructions correctly, I can successfully flash recovery.tar.md5 on Mr.Hydes thread http://forum.xda-developers.com/showthread.php?t=1885558 but when it goes to reboot it gives me the Yellow ExclaTriangle "System software not authorized by Verizion , yadi, yadi ya da".
I can get into Download mode but NO RECOVERY, Tried flashing (With ODIN) CWM 6.0.1.9 located here http://forum.xda-developers.com/showthread.php?t=2044630 but ERROR with NAND WRITE FAIL.
Does anyone have a PIT file? I want give Heimdall a stab at it before I go throw it through Verizon's front window. Appreciate any help, like I said I understand the importance of following Instructions, I've done plenty of Android devices before including The Original GTab7, I dont mind cracking it open either, I've already had it apart to disconnect the battery but that did no help either, BTW it's really easy to open up.
Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app
MrHyde03 said:
Sounds like you didn't flash the unsecure bootloader
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I couldn't boot into Recovery to Flash, I'm Trying to flash now using Odin but get "Secure Check Fail". Any Ideas?
The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app
MrHyde03 said:
The bootloader needs to be flashed before the recovery using the dd command. Its listed first under step 2, before the recovery.
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
Yeah that's where I'm confused, I've had it rooted and unlocked since November following your original Development, I was on G3 not J1. Followed the Instructions and then crap.
Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed aboot.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app
iwSachin plain
MrHyde03 said:
Unlocked since Nov and it just now crapped? That doesn't make any sense.. When you boot into download mode right now, what orientation is the screen? Portrait or landscape? Landscape would mean a correctly flashed about.img (boot loader)
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
I followed this thread of yours in the beginning of NOV. http://forum.xda-developers.com/showthread.php?t=1942674 I was rooted and unsecured bootloader, had CWM and SuperUser, but there weren't any ROMS out yet. Everything was fine until I went to install CleanRom the other day.
Portrait Orientation in Download mode.