Related
I've read in several posts that they found the way to return 3-button download mode to i9000 samsung.
But i haven't found anything about any methods of returning it to Vibrant. So if there is any way to do that or not?
saylas said:
I've read in several posts that they found the way to return 3-button download mode to i9000 samsung.
But i haven't found anything about any methods of returning it to Vibrant. So if there is any way to do that or not?
Click to expand...
Click to collapse
Wait for Samsung to patch the Vibrant.
OR
If your phone does not enter Recovery Mode, it is defective and T-Mobile will replace it.
P.S. Search before posting.
That was based off of a release by Bell for their series of Galaxy phones. To my knowledge, a port hasn't been made for the Vibrant.
My phone does not enter either recovery nor download modes from buttons. But i'm 6000 miles from US now, so I believe it's not possible to return it. And besides problem with getting the recovery mode is not critical, i can reach it through adb. But without hard download mode i'm very afraid of flashing new ROMs, because have a great risk of getting bricked.
So i'm wondering why nobody from developers has ported that fix to Vibrant, because i thought that at least one on them has the same problem
saylas said:
My phone does not enter either recovery nor download modes from buttons. But i'm 6000 miles from US now, so I believe it's not possible to return it. And besides problem with getting the recovery mode is not critical, i can reach it through adb. But without hard download mode i'm very afraid of flashing new ROMs, because have a great risk of getting bricked.
So i'm wondering why nobody from developers has ported that fix to Vibrant, because i thought that at least one on them has the same problem
Click to expand...
Click to collapse
U might want to try using adb to get into download mode. "adb reboot download". Thats what I usually do to get into download mode.
I can get into it that way of couse, but as i've said if something happens during flashing, i'll get unrecoverable brick
Please post in the appropriate section
The latest leaked ROM for the Vibrant I noticed has bootloader files. Whether or not they updated it to fix this problem I do not know.
My Vibrant doesn't have this issue so I am not going to mess with it.
The latest leaked ROM for the Vibrant I noticed has bootloader files. Whether or not they updated it to fix this problem I do not know.
Click to expand...
Click to collapse
wow, it's interesting. May be someone from developers can know?
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
JJMT said:
My Vibrant is telling me that T-Mobile has kindly sent me an update. I think it must be the GPS fix. It is rather persistent in that it won't let me choose when to install it. It will only allow me to delay for at most a day. This is quite annoying as I am preparing for a trip and really don't want to mess around with my phone right now.
I am running Vibrant9. Do I want to install this update? Is it gonna break anything? Thanks!
Click to expand...
Click to collapse
Shouldn't break anything. Most are still waiting for the update. Personally I was impatient and flashed it through ODIN last night.
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
JJMT said:
OK. I accepted the update. Phone is now stuck on "Vibrant" at reboot. Sigh. Proceeding to trying to restore ROM.
Click to expand...
Click to collapse
Go to the Development section that are a few threads about this. I looks like anyone with a lag fix, or GPS fix (from JI2) where having this issue, plus I have seen stock people having it too.
Or you can go read my blog post here. the post tells the steps I took to get back the JFD, but you could flash JI6 instead.
you will need to flash JI6 with ODIN to restore, you can not just do a nandroid restore, it is an issue with the kernel and nandroid does not restore/backup the kernel.
*facepalm*@Samsung
http://forum.xda-developers.com/showthread.php?t=803492
Anderdroid said:
*facepalm*@Samsung
Click to expand...
Click to collapse
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
dan0zone said:
This is why t-mobile had the G2 nand locked..... so this type of user error won't cost them millions, replacing phones that the user messed up with blind stupidity.... that's only for the ones under warranty, you can still call in a lost phone and get replacements..
Click to expand...
Click to collapse
So now instead, they get flooded with returns because the phone isn't what people expected.
zephiK said:
It's not Samsung or T-Mobile.. its that the OP performed tweaks so the ROM wasn't a 100.00% version of Stock. Tweaks including lag fixes, GPS fix, etc can cause this.
Personally, I don't know why if you're performing tweaks on your phone and are on a stock ROM. If you're going to tweak your phone, go the full way and tweak everything.
Click to expand...
Click to collapse
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
camalot said:
That's not true, it is Samsung/T-Mobile fault. I know 3 people with 100% stock, unrooted, vibrants, 2 of them got stuck when they updated. the t-mobile forums filled with stock users with their phone stuck at the vibrant screen as well.
Click to expand...
Click to collapse
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
zephiK said:
And what are the chances of this?
Everybody lies.. especially when they're desperate and unwilling to accept the fact that they modified their phone. I don't see any reason why they wouldn't lie to T-Mobile and say that they didn't modify their phones if its "bricked." Because it is not bricked, all it takes is download mode and Odin. There are threads out there that break down on how to use Odin, it's not that difficult to do.
This is why I don't endorse "One Click" anything unless it is a long process. Sure, it makes everything easier but it makes people not think about what they're doing before they do it. Before one clicking, rooting was so simple, put something on your internal sd and boot into recovery and hit reinstall packages. If something like that is too difficult then they shouldn't be doing any modifications in the first place unless they understanding what they're doing.
The T-Mobile forum is not a valid source because there is no concrete proof that they didn't root their phone and modified something. Even rooting and removing bloatware then removing access to root would cause this.
Edit: Looking at the OP's recent posts.. he did indeed run a custom ROM but has possibly did some tweaking after reverting back to stock?
Click to expand...
Click to collapse
Well, I know the 2 people that updated stock and got stuck at the vibrant screen were 100% stock because they both called me on what they need to do. one came over and I fixed it with ODIN back to stock (JI6) and the other just said he'd call TMO and get a replacement. they dont even know what rooting is, or that there is a site like that that they can get files to do "one click root"
OK. I'm the OP and I'm back. I was traveling today (with a phone flashed back to stock - that's as far as I got before getting kicked out of the hotel). I've now got the ROM restored and I'm where I was before trying to install the update.
My question is this (probably simple): my phone still wants to do the update. How do I make it go away? I can't install it, and I don't want to have to postpone it every day. Is there a cache I can clear or something?
You could just update it through Odin. I'm on stock with root and JAC's oc/uv kernel and the OTA failed but Odin worked perfectly.
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
JJMT said:
Yes, I will try to flash it with odin when I have the time and interest, but for now I have neither, and I just want the phone to stop bugging me. Ideas?
Click to expand...
Click to collapse
It will only stop once you are on JI6
camalot said:
It will only stop once you are on JI6
Click to expand...
Click to collapse
OK. I guess I will have to try to push the update through odin. Can someone point me to a link to the files?
I'm kind of irritated by this whole thing. I'm pleased with tmo for pushing the update out, but I mean, really, even Windows allows you to decline to install an update.
http://forum.xda-developers.com/showthread.php?t=798125
chad658eku said:
http://forum.xda-developers.com/showthread.php?t=798125
Click to expand...
Click to collapse
Thanks for the link. It really looks to me that I'm going to need to flash to a stock ROM before flashing JI6. That, as they say, is a bummer.
As I am actually quite content at the moment with Vibrant9, it really seems to me that it would be easier to somehow remove whatever it is on my phone that is requesting that I update. Presumably there is an update.zip file sitting somewhere, that will be copied into sdcard before the updater involves reboot recovery. Any ideas where to look?
I would really rather not do any further flashing until is an official Froyo to flash to.
JWhipple said:
So now instead, they get flooded with returns because the phone isn't what people expected.
Click to expand...
Click to collapse
Flooded with returns by morons who think they are smart.
Hi All -
New to this phone obviously (RAZR MAXX). Trying to get a grasp on it, as it's way more complicated than HTC and Samsung phones. I've rooted and installed 100s of custom ROMs with those brands before. This is my 1st Motorola since the Motorola V120c if anyone is old enough to remember that dinosaur. On nTelos' network nonetheless.
I have some questions that I would like answered and I hope someone will do me the honor as the content is really sporadic.
What is Fastboot for this device, what does it do?
Safestrap & Bootstrap? What's the difference? Which is better?
Can I flash ROMS through CWM like I have in the past?
What purpose does RSD Lite serve other than to flash Fasboot files?
Why would I want to flash fastboot? (Redundant question I think)
Thanks to anyone that takes the time to help me out.
I rooted and flash the crap out of my last phone which was Samsung. This phone seems really complex. I'm really on my toes, don't want to brick my phone. But I do want to root to get rid of the bloatware and test out some roms. The stock OS is laggy at times.
Honestly I really like the Stock OS as is. It does seem laggy at times, but nothing worse than I've run into on HTC or Samsung phones.
HTC Sense UI was/is terrible since it's so bloated and Samsung couldn't make a GPS radio capable of locating a mall let alone provide directions to anywhere. Terrible phones.
So far this phone is awesome, really bought it for the battery life honestly.
I too would like to DELETE the garbage that Verizon has installed on this thing. In terms of bloat, Verizon takes it to a whole new level. Just wow.
I'm in the same boat. Only had the phone for 2 days so far. I've already rooted it, but haven't gone any farther. But in some of my reading, I thought I saw that removing the bloatware can cause OTA updates to not happen. Hopefully someone can shed some more light on that issue.
midas69 said:
I'm in the same boat. Only had the phone for 2 days so far. I've already rooted it, but haven't gone any farther. But in some of my reading, I thought I saw that removing the bloatware can cause OTA updates to not happen. Hopefully someone can shed some more light on that issue.
Click to expand...
Click to collapse
I rooted mine 5 mins after activating it haha. As far a bloat, just use titanium pro and freeze it. Very simple. I froze around 35 apps and haven't had any issues associated w it. Should an ota come I should be prompted still. Just unfreeze all apps. Accept ota, reroot. If it breaks root completly then eventually it will get root again. I actually Ind, e system to run very well but honestly have no idea how just stock runs as I froze these apps instantly. I did not safe strap or bootstrap but I had previous knowledge of things I should be able to freeze and not and I figured it out myself
I find this phone so easy. There YouTube videos on everything.
To Get bootstrap, all you need to do is press one button, this phone has to be the easiest I've been on. The only people that struggle are the desperate ones that cba to search the forums And YouTube
Ask us any Android Related Question @FeraLabsDevs on Twitter
IdowhatIwant said:
Hi All -
What is Fastboot for this device, what does it do?
Safestrap & Bootstrap? What's the difference? Which is better?
Can I flash ROMS through CWM like I have in the past?
What purpose does RSD Lite serve other than to flash Fasboot files?
Why would I want to flash fastboot? (Redundant question I think)
Thanks to anyone that takes the time to help me out.
Click to expand...
Click to collapse
- Fastboot: its just the stock bootloader, can flash moto updates/factory reset/wipe cache. it also lets you into AP fastboot, which is where u recover stock with rsd.
- Safestrap/bootstrap: bootstrap is currently our only way of CWM on the gsm phones, i understand safestrap is pretty much like dualbooting except its not(only its not completely compatible with gsm)
- can you flash with cwm: YES!
- another purpose for rsd: i have only used it for recovering after ics, so idk.
- why flash a fastboot image?: if you mess up badly or get a bootloop you can recover back to stock
midas69 said:
I'm in the same boat. Only had the phone for 2 days so far. I've already rooted it, but haven't gone any farther. But in some of my reading, I thought I saw that removing the bloatware can cause OTA updates to not happen. Hopefully someone can shed some more light on that issue.
Click to expand...
Click to collapse
removing bloatware will cause you to be unable to get ota's (freezing and then unfreezing with TiB before ota update works fine, as long as you don't uninstall).
but i think its enough to just flash a fastboot with rsd (fully return to stock), then you can get the ota
Look here:
aashrey99razr.wordpress.com
Helped me out a lot!
Gesendet von meinem XT910 mit Tapatalk
Addictd said:
removing bloatware will cause you to be unable to get ota's (freezing and then unfreezing with TiB before ota update works fine, as long as you don't uninstall).
but i think its enough to just flash a fastboot with rsd (fully return to stock), then you can get the ota
Click to expand...
Click to collapse
I'm afraid I deleted one app before I was aware of this. TiB shows that I made a backup of it, but doesn't give me the option to restore it. Guess I'm screwed.
hehe, probably not
did you make a cwm backup prior to uninstalling the app(s)?
then you could just restore that
if not the titanium backup file should be on your internal sdcard in /mnt/sdcard/TitaniumBackup as a gzipped .apk with a kinda cryptic filename
you could try ungzipping it and installing with a file explorer.
or you could just backup with cwm and flash the correct fastbootimage for your phone from here: http://forum.xda-developers.com/showthread.php?t=1362956
usind rsd lite
and that should do it
but why not just flash a fastboot and isntall arctic 3.0.5?
Addictd said:
hehe, probably not
did you make a cwm backup prior to uninstalling the app(s)?
then you could just restore that
Click to expand...
Click to collapse
Of course not, that would be too easy
if not the titanium backup file should be on your internal sdcard in /mnt/sdcard/TitaniumBackup as a gzipped .apk with a kinda cryptic filename
you could try ungzipping it and installing with a file explorer.
Click to expand...
Click to collapse
There is a file there, but it doesn't have an .apk. There's a gzip file, inside that is a tar file. In there are imbedded data directories, but no actual files.
or you could just backup with cwm and flash the correct fastbootimage for your phone from here: http://forum.xda-developers.com/showthread.php?t=1362956
usind rsd lite
and that should do it
Click to expand...
Click to collapse
Might take that route when the next update is ready.
But why not just flash a fastboot and isntall arctic 3.0.5?
Click to expand...
Click to collapse
Well, as I said, I only got the phone Saturday, and I work weekends.
But I've got an issue hooking up to my work email account. I was unable to get it working on my Touchpad using CM7 or CM9. I originally bought a Galaxy Nexus and had no luck with that either, thus I bought the Razr. I still can't get the native apps to work, but at least Touchdown semi-works (no Activesync). So I'm actually a little gun shy about trying new things.
Addictd said:
- Safestrap/bootstrap: bootstrap is currently our only way of CWM on the gsm phones, i understand safestrap is pretty much like dualbooting except its not(only its not completely compatible with gsm)
Click to expand...
Click to collapse
Does that mean that we can't use ROM Manager or do we just need to use Bootstrap to install CWM and than use ROM Manager like we otherwise would? I got used to that app on my old phone.
I got a GSM RAZR and I have just rooted, the root script pushed in my phone some app called Bionic Bootstrapper, which gives me options Bootstrap Recovery and Reboot Recovery, what does each of them do? I don't plan on changing ROMs for now, but I definitely need to be able to recover the system.
It appears there isn't any real root on this device since the bootloader is locked. Samsung and HTC devices have their BLs unlocked so it's easier to make a permanent Recovery that will persist on reboot. I'm speculating of course, so someone correct me if I'm wrong.
Reboot recovery should reboot the phone to a ClockworkMod style "DOS" menu that allows you to preform functions like Back up, install zip files or even a new ROM.
When I did it, it rebooted a triangle and exclamation point, with an android guy on it. I was worried at that point. I hit the power button and the Recovery loaded instantly. Not sure if that's normal, but it's quite shakey compared to other devices out there.
I love this phone, so don't me wrong. It's just going to take some getting used to.
i dont think all of rom managers functions will work :/
bootstrap recovery: installs recovery (you only have to do this once)
reboot recovery: reboots your phone into cwm
the thing is the bootloader is locked, so we cant put cwm into the stock fastboot.
there is however a little workaround made by J.Y.Daddy that starts cwm everytime you boot, but this is installed in your rom, not in the stock fastboot, so you have to reinstall it when you flash a new rom :/
onboot cwm link: http://forum.xda-developers.com/showthread.php?t=1385283
Addictd said:
i dont think all of rom managers functions will work :/
bootstrap recovery: installs recovery (you only have to do this once)
reboot recovery: reboots your phone into cwm
the thing is the bootloader is locked, so we cant put cwm into the stock fastboot.
there is however a little workaround made by J.Y.Daddy that starts cwm everytime you boot, but this is installed in your rom, not in the stock fastboot, so you have to reinstall it when you flash a new rom :/
onboot cwm link: http://forum.xda-developers.com/showthread.php?t=1385283
Click to expand...
Click to collapse
Is there some way to otherwise boot into CWM enviroment, some combination of keys or something like on other phones? Not much use for CWM if you brick your phone and can't boot into it. Also, is installed CWM not going to cause a problem for regular OTA updates and do we need to reinstall it afterwards?
From what I understood, Motorola has put some sort of recovery environment on this phone already, but I don't know what it can be used for.
And I have GSM version, bootloader is not locked, so I don't have to worry about that.
laserburn said:
Is there some way to otherwise boot into CWM enviroment, some combination of keys or something like on other phones?
Click to expand...
Click to collapse
there's a workaround by J.Y.Darry that makes it boot into cwm on every boot.
there is no keycombo for cwm booting. but you can boot into fastboot with both volumekeys + power
where you can go into stock "recovery" and AP fastboot
you will use AP fastboot in combination with RSD lite to flash back to stock if u mess up, there are also more options in fastboot, but i have never used them.
laserburn said:
Not much use for CWM if you brick your phone and can't boot into it. Also, is installed CWM not going to cause a problem for regular OTA updates and do we need to reinstall it afterwards?
Click to expand...
Click to collapse
you will use cwm to flash custom roms and make backups
then if you mess up and want to recover a backup you have to
- set phone in ap fastboot mode
- connect razr to computer
- use rsd lite(or an alternative flashtool) to flash the fastbootfile for your phone
- root and install bootstrapper
- reboot into cwm and restore backup
i dont think cwm in itself will cause any problems for OTA's. but if you install a custom rom its a different story
as long as you have the bootstrapper app installed on your phone, you should be able to bootstrap recovery and boot into cwm
laserburn said:
From what I understood, Motorola has put some sort of recovery environment on this phone already, but I don't know what it can be used for.
Click to expand...
Click to collapse
yes they have put a rudimentary recovery in it. but you can only use it to apply updates from sdcard (to manually download ota and install), wipe and factory reset. (someone correct me if i'm wrong here)
laserburn said:
And I have GSM version, bootloader is not locked, so I don't have to worry about that.
Click to expand...
Click to collapse
sorry to be the bringer of bad news. but i have gsm too. mine is locked, so i'm pretty solid your bl is too
troollolotorola -.-
Damn, how I miss my old phone where rooting was 1 click on the app and you could swap ROMs as easy as swapping socks.
How could I check if the bootloader is locked and what consequences does it have?
laserburn said:
Damn, how I miss my old phone where rooting was 1 click on the app and you could swap ROMs as easy as swapping socks.
How could I check if the bootloader is locked and what consequences does it have?
Click to expand...
Click to collapse
Yeah I agree with you. Rooting, flashing, CWM all 100 times easier on HTC and Samsung phones.
Don't get wrong though, I Love my RAZR Maxx, and the default OS is actually OK. Which is good because it seems that there is little to zero developement for the CDMA version of the droid RAZR/MAXX at the moment, if at all.
they're all over on the HTC/Sammy forums =D
laserburn said:
Damn, how I miss my old phone where rooting was 1 click on the app and you could swap ROMs as easy as swapping socks.
How could I check if the bootloader is locked and what consequences does it have?
Click to expand...
Click to collapse
if/when we get the BL unlocked this phone will be a dream
there is this utility made by mattlgrof u can use to check bl lock
http://forum.xda-developers.com/showthread.php?t=1486718
IdowhatIwant said:
Yeah I agree with you. Rooting, flashing, CWM all 100 times easier on HTC and Samsung phones.
Don't get wrong though, I Love my RAZR Maxx, and the default OS is actually OK. Which is good because it seems that there is little to zero developement for the CDMA version of the droid RAZR/MAXX at the moment, if at all.
they're all over on the HTC/Sammy forums =D
Click to expand...
Click to collapse
Ain't no agruing with that, but they don't make as sweet looking and solid phones i hope motorola pull their head out of their ass soon...
Development for the cdma version is found mostly on droidrzr.com (plenty of beta/alpha ICS and some GB roms) but they are missing some parts, so we have to wait till motorola release ics be4 they will be complete.
http://www.droidrzr.com/index.php/index
for all you non-cdma users out there, u should check out the cdma to gsm patch
http://www.droidrzr.com/index.php/topic/1233-cdma-port-cm9aokp-givesomelovetogsm/
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Are you asking for info for your Atrix or SGS2 device?
Sorry, I am asking about the SGS2.
ds1904.ds said:
I understand that this may have been asked, and I've been looking at similar threads, but I'm having a hard time finding a direct answer, so I apologize.
I have some experience rooting with an Atrix, but I just got this phone two days ago, this morning I used the 1-click method from rootwhiz to install the ICS leak. No problems having it run at all. I need to know, directly, did this install change my bootloader and change the binary count? I can't remember if I saw anytime of yellow triangle as people talk about. If it changed the bootloader what is there a safe method to return to the older bootloaders, and or do I even need to do so to root and install other roms?
I know that the Atrix had some problems in terms of returning to prior versions of things, and in my research I haven't found a direct answer to this question too.
Basically, did my bootloader change? Can I root using the heimdall method I keep seeing about safely? What would be the best way to root and install custom roms, neglecting the binary counter if I can get a jig or something?
Forgive me again for asking, I just need to have better answers before I try anything.
Click to expand...
Click to collapse
If you used the 1-Click method, yes. Your bootloaders are changed. Wouldve been much better to use the Heimdall method or just root your phone then flash the Leak ROM that task650 and Fenny made. As far as reverting bootloaders to stock, thats out of my range of knowledge. Im sure there is a way to do it though.
EDIT: For rooting, best way is to be on stock 2.3.4 and use the Zergrush exploit.
I've seen you're using the past tense a lot, I thought you already DID.
Anyway, for rooting and installing custom ROM, follow this thread:
http://forum.xda-developers.com/showthread.php?t=1311081
I can't pinpoint exactly what to do since having no info.
Thanks for the answers so far, now that I know my bootloaders have been changed I need to figure out how to either change back / and how to safely root. I may just have to wait it out I think though, no problem with that really, working just fine now. And never use the alarm
For clarification, my rooting experience is limited to the Atrix, the SGS2 is new as of Monday, and I am having trouble sifting through information. What I've learned so far is that maybe it was a little hasty to install the ICS leak the way I did. Prior to the ICS leak there was nothing changed on the phone.
You're going to have to get some experience with ODIN. Here is the bootloader you'll want to flash back to, however, then you'll probably need to flash a kernel with CWM (clock work mod) and then boot into cwm to flash a rom such as Tasks stock ICS leak. http://forum.xda-developers.com/showthread.php?t=1316726
So if I follow correctly the ICS leak I installed added newer bootloaders that prevent jigging in the future if it was needed. My two options are apparently to use the method that bypasses the counter, which was posted, or to use ODIN and flash the older bootloader, but this can be dangerous if done incorrectly.
The danger of bricking scares me a little, but I successfully used RSD Lite to unlock the bootloader on my Atrix, don't know if it's similar. Perhaps I should take the Atrix and attempt to install an older bootloader on it to get a feel for things? I figure that it wouldn't make much of a difference however...
I figured out that even though I have a newer bootloader now I still have a 0 for the binary counter, as the leak is considered a samsung official release, of course I don't know how that would effect any given warranty.
So, I still feel that these following questions are unanswered, I apologize if I am not understanding correctly:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lote).
Sorry if these are stupid questions, I hope I am asking good enough questions to help others out in the future
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
ds1904.ds said:
1. Is it safe for me to root with the heimdall method even with the newer bootloaders
Click to expand...
Click to collapse
Dont believe you can root since you already flashed it with ODIN 1-Click
ds1904.ds said:
2. Is it safe for me to install custom roms without reverting the bootloader, as long as I am using the bypass method to prevent my counter from changing?
Click to expand...
Click to collapse
You cannot install custom ROM's because you dont have CWM.
ds1904.ds said:
3. What is the exact risk to flashing the older bootloader, and what precautions should I take before doing so? If I flash the older bootloader without reverting to stock firmware will that cause a brick? Or is the risk just associated with fudging up the process of the flash itself, and hoping that the connection doesn't get cut (on that note, the phone, usb cord, and computer I'm using are all less than 4 months old, so that risk doesn't concern me a whole lot).
Click to expand...
Click to collapse
Really not sure on these questions. Any takers?
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Click to expand...
Click to collapse
No; Only download mode (Odin/Heimdall) flashes trigger changes to the warning screen.
ds1904.ds said:
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
Kernel is a set of drivers that tells the hardware what to do. Firmware is like a new base. (XXLPQ, DXLP7 etc.) A ROM is the whole package.
Please if I missed anything or am incorrect about some/all of this, somebody correct me.
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
D3M3NT3D_L0RD said:
Should be fine. NONE of the ROMs you find on the I777 boards in Ported or Original will have bootloaders so no worries. And yes after root use Mobile ODIN to install a zImage which will give you CWM. Highly recommend Siyah 2.6.14. Please stick to just trying some GB ROM's and get the hang of making nandroids etc before moving on the ICS ROM's.
Click to expand...
Click to collapse
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
ds1904.ds said:
All I get is an apk file, I've been searching all night for a zimage... The file says i777 flashkernal, and it's just an .apk. Mobile Odin can't see it unless I name it zimage with no file extension. I tried that and it seemed like it was soft-bricked so I used odin on the PC to reflash the stock root think mentioned in the thread.
I was thinking of CM7 if it will work flashing as a zip from CWM, if I can get CWM on there that is.
Click to expand...
Click to collapse
Where in the hell are you getting an apk from? If you dl Siyah or Entropy kernel, the zImage is in the zip. Pull that and put it on your SD card
I am interested because I was in your position. Did the ICS leak 1 day too early and lost root. So what method did you use to go back to GB? Did you have to flash a new bootloader or was that all done in one package? Was it Entropy's "return" method?
I was seeing if I can keep the ICS leak and root. A dev here advised that all I need to do is re-flash the zip filed ICS leak. However since I have no root, I can't CWM recovery...I don't know another method to flash the rooted ICS leak.
So I'm thinking I have to wait for an exploit, or flash back to an old GB, root, ensure I have CWM, nandroid (I nandroided my rooted GB before upgrading to ICS leak), then flash the zip ICS leak.
Does anyone else have alternatives?
ds1904.ds said:
Okay I think I'm starting to figure this out. I downgraded to 2.3.4 using an unroot/stock method I found, using odin and it worked. It would not accept the OTA update however, but I believe this is due to the ULCL2 baseband? Someone correct me if I am wrong.
Now I am going to use method 2c found here:
http://forum.xda-developers.com/showthread.php?t=1311081
to root and restore to the other baseband, which also happens to be the one that's best for my area I believe. From there, I can install CWM using one of the 31-c methods, and use CWM to install custom roms as long as they don't have bootloaders, correct? Or does it not matter if the packages have bootloaders.
Someone correct me if I am wrong, I don't want to ruin anything here. I think it's safe to install the files that come from the 2c method but wont be doing anything else until I know it's safe.
Click to expand...
Click to collapse
SMH...root is not needed for CWM... a custom kernel is
Pirateghost said:
SMH...root is not needed for CWM... a custom kernel is
Click to expand...
Click to collapse
True but to do it with Mobile ODIN you need root
ds1904.ds said:
After some more reading, here's another question as well:
Does the SGS2 technically have an unlocked bootloader already? It just counts how many times you install non samsung firmware?
Also just so I know that I'm not wrong, are Kernal, Firmware, and "Roms" all the same thing? How can you tell if a "package" or "rom" comes with bootloaders, as this is something I apparently am supposed to avoid.
Click to expand...
Click to collapse
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Entropy512 said:
"ROM" is an improper name for the firmware flashed to a phone. (the memory in question isn't read-only by any means. In Windows Mobile devices, you had to flash the firmware image all in one go - but on Android, /system contents can be modified on the fly as they're a normal file system.) garyd9 started a little crusade against the term ROM and I try to continue it (but I slip up sometimes).
Kernel contains the most basic low-level hardware drivers for a device. It's a small portion of the firmware for a phone. The remaining portion is the system partition - /system - kernel and /system together make a complete firmware package.
And you are correct - our bootloaders are fundamentally unlocked, the only code signing enforcement is the custom binary counter. It can be reset either with the jig or with TriangleAway (TriangleAway requires ICS)
Click to expand...
Click to collapse
Glad you chimed in. I now feel stupid at my lack of knowledge
I almost think that the issue is that your "unzipping" the zip image files that you are downloading.
Why is it so important that you keep the phone in a reversable mode? Are you planning on returning it or perhaps selling it and do not want it to be known that you have flashed it?
Personally I am not knowledgeable enough to offer much advice, I just read the forums as most and try to put together the peices of information that fit my situation.
The Dev forum is by far the best place to look and get your questions answered and there are a bunch of guides on step by step processes. The only real advice I can give you is to google each term and understand what it is you need and then post your question.
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
I dont own a Z3V however i own a Z3, i haven't experienced boot loop on the Z3, however i have with previous Xperia Devices i solved the issue by installing Flashtool and downloading my stock FTF file.
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
Whoever told you that you can install these doesn't know the z3v. It's a different phone from any other z3 and can't take those custom Rom.
Your best solution is to try the tft install as described in the downgrade section of the root thread. That would bring you back to a stock Verizon.
Seannnn said:
Alright so I have a rooted D6708 device. I got an itch today and wanted to explore some custom roms. I was told that I could flash one of these roms onto the device and it would work.
So I did so with the use of TWRP. TWRP said the install was a success and I needed to reboot. So, I rebooted and now it won't load anything. I can get into the stock System Recovery Menu but nothing else. I can't get back into TWRP and I can't get the device to connect to my PC.
What can I do to fix this?
EDIT: I can get the computer to recognize it as "S1 Boot Fastboot" Anything I can do from here?
Click to expand...
Click to collapse
Sorry I did not check your PM much earlier to prevent you from doing this. Whoever did tell you about flashing a custom rom sure does owe you another phone. You have to wait until Verizon brings out the Lollipop rom, but until then, you have to somehow flash back to the original rom that came with. 4.4.4 is enjoyable enough as it is, just the lack of volte is what's the wait for on the Lollipop rom.
A rep told me today that when the Z4v, there's sure likely a quick follow up on releasing the update since they may as well base it off of it. And that's hoping if the new one even gets VoLTE...
Thanks for the help guys, I can access the phone via USB with fastboot. I am trying to flash the ftf file but I don't think I am doing it right or its not working. Is there any way I can switch it to adb mode through a fastboot command?
Sorry I don't entirely know what I am doing.
Seannnn said:
Thanks for the help guys, I can access the phone via USB with fastboot. I am trying to flash the ftf file but I don't think I am doing it right or its not working. Is there any way I can switch it to adb mode through a fastboot command?
Sorry I don't entirely know what I am doing.
Click to expand...
Click to collapse
to connect in flashmode you need to hold volume down and connect the phone to the pc with a usb cable
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Seannnn said:
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Click to expand...
Click to collapse
It's a good thing you were fortunate enough to have it replaced with no charge. Now don't make that same mistake again and wait like the rest of us. At least you confirmed for sure that flashing an incompatible ROM is death of the phone. lol
Seannnn said:
Unfortunately I was not able to get it into flash mode.
Good news is that the phone was still in warranty and I got it replaced for no charge.
Click to expand...
Click to collapse
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
sherdog16 said:
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
Click to expand...
Click to collapse
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
tsachi said:
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
Click to expand...
Click to collapse
yes you can... simply exclude warranty on non OEM code... very simple to solve....
sherdog16 said:
I'm aware that I'm coming across as a jerk for this. That is THE reason they don't want us rooted and such. When people screw it up they expect someone else to pay for the mistake
Click to expand...
Click to collapse
That is why the Z3v has a hash code on the phone that shows when you root it and can't be flashed over so they know if it has been rooted even if you flash back to the correct firmware. "Settings>About phone>Status" You send it in they charge you full price.
tsachi said:
I agree. People always complain about carriers preventing root and locking boot loader. The main argument is that it doesn't damage the phone. Unfortunately, I've seen many people on xda abuse the system. When they brick their phone through bad flash or when their phone dies after it overheated because they over clocked, they go for warranty replacement.
Can't blame Verizon for trying to avoid these extra costs.
Click to expand...
Click to collapse
Uh, VZW says it is about the "network", not bad flashes on phones. So which is it?
If VZW wasn't so anal about rooting Sony lets you root in a foolproof way, failed rooting is VZW's fault if it happens.
Any one got the solution.... my phone not working
shashikiran said:
Any one got the solution.... my phone not working
Click to expand...
Click to collapse
What did you do this time?
no recovery mode
GigaSPX said:
What did you do this time?
Click to expand...
Click to collapse
flashed flashable prerooted.zip file and not even getting recovery mode, no charging symbol, only can access fastboot mode. continiously rebooting with vibration. no display
My Z3v is rooted and is working just fine, except the annoying ads I get on my quick charge screen, now.
Anyway... I assume you haven't tried to use the Sony/Verizon Software Upgrade Assistant? It comes on your phone to install to your PC and lets you upgrade (probably never gonna get an upgrade) and factory your phone over USB. Not sure if you can download it, or if it only comes on the phone as a separate partition to install from. Can't hurt to try.