Related
Hello folks,
Generally loving my Vibrant, of course hungry for Froyo. I have two Vibrants, the first I've been using and have modded it with root and other enhancements. I gave the other phone to a friend as a gift, but when I wanted to root theirs using the same method I've used on multiple occasions, it would NOT boot into the recovery mode. I use the UP + DOWN push, plus the power button. No dice, just get the cheesy "come together" Tmobile screen, I tried up, down, waited for the Samsung to flash twice, no dice. It was not that complicated on my phone and I can continue to do so. I have looked up threads and there is suspicion that T Mobile disabled this on later vesrions? This version was shipped to me slightly after my own, within a week or so.
It would be disheartening if I couldn't root and make his phone more efficient to deal with the battery hog issues as well as other enhancments. Maybe I'm doing it wrong but I've treid multiple combinations and never get into the utility/recovery screen.
Any thoughts on this? I tried rooting before that with the Ryan one click lag fix, and it seemed to indicate it was done,b ut then Iwhen I opened ROM manager, it said it was not rooted yet. Then when I tried the one click app fix again, it mentioned it couldn't because soemthing about the SD card mounting,etc. I could put the stock PIT file on it via ODIN could I not? But I dont' want to go to all that hassle if it's something else. Is there a another app solution that can root for you? I can mount and drag the update zip there, but can't get tot he screen to reinstall packages.
Hopefully TMobile isn't stripping this down so we can't customize and it's something else but I'm trying all combinations short of doing the hokey pokey.
Thanks in advance!
Kelly
Samsung Vibrant
Apparently either Samsung or Tmobile are having the option disabled via the normal ways to get into recovery. There are numerous other threads regarding this throughout the forums detailing other peoples experiences regarding this.
Take a look here for one:
http://forum.xda-developers.com/showthread.php?t=771247
Join the club. I'm on my third vibrant with this same issue. I am returning it this week for a refund. My first....and last samsung phone.
thank you guys, I was afraid of that. one of the phones greatest assets was it's hackability. Froyo had better do something with battery consumption, speed, etc, or this phone will be a great screen and not much more. boo to hardware lockdowns! let the hackers hack and if you want to void the warranty, do it. I'll see about this ADB mode, I'm wondering if someone can create an app that would successfully root so ROM manager will work. I wonder why the one click fix lag app, which supposedly roots, did not. It seems like an overall lock down on this access?
At any rate, I'll try the other options but it's looking like more and more, my buddy will be a slave to Samsung release timeframe, and thats assuming froyo and updates will fix significant bugs and improve battery life.
thanks again guys! I'll keep trying.
And what about the download mode, can you get in it?
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?"
not sure, you mean the little digging android feller? I will try that, I gave the phone to my friend but sent him the page in this thread earlier regarding multiple attempts to get into either / or mode. would that actaully help install the packages aka root the phone? I only used that last time to reinstall via Odin, the T Mobile factory build because it was soft bricked due to a bad lag fix that froze the phone on the Samsung logo.
download mode , can that get it rooted? Or just wanting to know if all hardware access has been blocked?
Yeah, that the digging guy. It won't help you to get rooted, but i can't get in download mode, so if you can advise me how can i do that, i appreciate
I am an android noob and I have been very frustrated because the OS boot setup does not allow me to control which apps will boot-up at start. I’ve tried various startup managers and none of them can keep apps disabled as they seem to auto start themselves so I have to constantly close apps in order to preserve resources.
I Then sought to root phone to gain control by using a collection of root apps; Universal Androot – v1.6.2 beta 5, 6 & 7, z4root & Super One Clickv2.2 all w/o success. I do not know why they failed only that these apps seemed to do no harm to the phone otherwise. The phone is a Samsung Galaxy I5500M through PC Mobile, the carrier being Bell Mobile. The following is the particulars on the phone:
Model number: GT-I5500M
Firmware Version: 2.1-update1
Baseband version: I5500MUGKE3
Kernal version: 2.6.29-perf [email protected]#1
Build number: ECLAIR.UGKE3
When I dial *2767*4387264636#.
Product code: GT-I5500YKMBMC.
When I dial *#1234# I get;
PDA: I5500MUGKE3
CSC: I5500MUGKE3
Phone: I5500MUGKE3
I have an acquaintance that has the same phone from the same source that attempted to install a custom ROM using the method outlined on the madteam website "cyanogenmod-7-installation-guide-for-g5-users"
Unfortunately after rebooting that phone it simply boot looped on the Samsung & Android logos. After many attempts to fix boot loop the phone was put aside, to my knowledge that phone has yet to be repaired.
Anyway, I really want to take control of this phone but am afraid of bricking it. Any help to be able to at the very least root it or even better to install a custom ROM would be very much appreciated. Thanks very much to all those that have contributed to this forum… it is amongst the most informative I’ve come across.
Hello there!
If your phone isn't rooted you won't be able to install a custom rom or anything, so I shall try and help you as much as I can, I'm a noob at this kind of stuff too so I'd wait for somebody to confirm what I say before you try it.
I rooted and installed Superuser on my I5500 using Universal Androot, took a few tries though so it might be worth trying it again.
Basically, can you put your phone into download mode? (Turn off device, hold down power button and the volume buttons and it should boot into Download Mode) If so then you could install Clockworkmod (Don't hold me to this, wait for some confirmation from someone with more knowledge) I'm not sure if your device has to be rooted to flash Clockworkmod v4. Even if it doesn't then surely accessing Download Mode and opening KIES will allow you to reset your device and get out of the boot loop.
Here is how to install a custom rom- I use Cyanogenmod 7.1, I'd recommend that to be honest, plenty of customization and many options to tweak performance.
Root your device (I use Universal Androot, it worked for me)
Flash Clockworkmod v4 via Odin.
Put the 3 Cyanogenmod files onto your SD Card.
Reboot into recovery on your device.
Select install update from zip.
Select the 3 files in the specific order.
Wipe data, cache and dalvik cache then reboot.
Then you're running CM7.1.
You can find the files and a more in-depth guide on the Development section under our phones name.
I hope I have helped a bit.
oh I almost forgot, have you tried hard-reseting your device by holding down certain buttons in a specific order? If so then you can reset your phone like that and maybe sort out the boot issue, should fix it, but again don't hold me to it. Hold down the menu/home key, volume key and power off button whilst your device is turned off and that does a hard reset.
Hi CurtisAndroid5,
Thank you for responding. To give a little history I have tried repeatedly using Universal Androot – v1.6.2 beta 5, 6 & 7, z4root & Super One Clickv2.2 to able to gain Superuser access all w/o success. As far as the custom ROM... that would be the ULTIMATE! But as mentioned on the original post there is someone I know that has possibly bricked one using the exact instructions outlined by the madteam when installing cyanogenmod-7 & spent weeks trying to solve a boot loop... still not fixed. The only reason I have not attempted to do this is I don't want to see the same result.
I have literally booked marked a dozen or more threads, have read hundreds of posts trying to find a solution to rooting this Bell Samsung phone. In my searches I've found on Samsung Open Source website a zipped update; "GT-I5500M_OpenSource_eclair_update2" that I no idea how to use. I honestly think that there are some subtle differences in how Bell sets up their phones that prevents rooting & Superuser access.
I will delve deeper into your suggestion and view posts under the Development section under the phone name. Again your response is deeply appreciated. Thanks!
Ah I see, like I said, I'm not the most experienced person in this kind of stuff so I can't help you any more seen as though my knowledge is limited. I hope you managed to sort your phone out, it will probably be a minor error and will be easily fixed, your G5 will be an amazing little phone once you get it rooted and installed a custom rom!
I had the same problem with my samsung i5500, i just got odin, flashed clockworkmod with it then put in my custom rom, i'm currently on cyanogen mod 1.7.2
CurtisAndroid5 said:
your G5 will be an amazing little phone once you get it rooted and installed a custom rom!
Click to expand...
Click to collapse
I wish mine was -.-
Hello,
I have a Asus zenfone 6 however my problem also occurs on the zenfone 5 phones.
The poblem is as follows,
After updating from stock to latest android (v1,18 at the time) the phones battery display became incorrect making the Phone unreliable at bestand nothing seems to help fixing the problem.
I have tried a million calibratnig apps with zero success as suspect the phones software doesnt actualy understand that it has a 3230 mah battery.
I have found and compared files with a working zenfone6 where the file displays 2070mah for me and 3230 for the working Phone.
I then tried to manualy change this file had no acces even with root but every reboot or unplug it just resets the file anyway as it gets its data elsewhere.
I have tried a factory reset but not everything was actualy reset it just deleted my data but roo and all othr crap that the update screwed up was still there.
I tried ADB sideload but that didnt work and udupdates as ota so will not factory reset and remove root anyway.
I contaced asus but they are as clueless as a goats rear and just say a future update will adress it...Which we al know isnt going
to happen as this has bin a issue for some users for over half a year and they didnt fix it.
So as a final attempt to fix this Phone im planning on unlocking the botloader which i really didnt want to do as im new to all that and just want a rooted stock rom...
So to my question.
If i unlock the bootloader i know the Phone will be wiped. Will i just be able to flash any version of the stock rom via ADB or is there other things i need to do to either the Phone or the rom?
I cant go screw up my Phone without knowing how to fix and flash it again directly.
And do apps like the one asus provide usualy also allow relocking of he bootloader again after flashing the rom as i dont want to leave it open if there is no need to?
Any other ideas are welcome aswell but i have bin trying to solve this for over a month.
Heres a screenshot of the error i get when i try to reflash current rom with ADB.
http://oi60.tinypic.com/2eefzuv.jpg
But as long as that doest a full clean rom install its not helping me anyway.
i really hope someone has a easy and quick way to do a fresh install that will really make the Phone like it was just out
of the box software wise. no root no changes or anything as factory reset is not doing that for me.
Thanks in advance.
Hutjeflut.
This will save you 8-12 hours of your time if you are lucky. This means that it also includes the meaningful links of 8-12 hours of searching. Sentences in italic are important. 1 link is for the Odin official website, the rest are re-links back into XDA.
The device in question is a SM-925T Tmobile S6 Edge.
The problem was this. I rooted my phone and messed around with Greenify and the Play store. To prepare for rooting, I allowed unknown downloads, unlocked the bootloader, and turned my security lock off (I had set it to a finger print lock). After I was done rooting, I immediately locked the bootloader again(<--A mistake that caused my bootloop/ soft-brick). After I was finished messing with the above apps (Greenify, etc), I wanted my phone to restart. So I held the Power button and selected restart, while I was on the lock screen (may not be important). I noticed that it took a long time to restart, and upon closer examination, I noticed another error under the "kernel is not seandroid enforcing" (which appears to be natural for rooted phones). The error was "Custom Binary blocked by FRP Lock". It was a new error. I investigated this new problem using the internet , and this dude was panicking like hell, but he didn't appear to fix his problem. He did hint that returning to the bootloader to its locked state was a mistake. Looked a bit more and this guy pointed to another thread, which introduced me to flashing and more importantly his fix, which was to flash the stock 5.1.1 image through odin. He used this link, which contains all the stock firmware for the majority of the new Samsung S6 and S6 edge versions. To make a long story short, most of these fixes involved flashing your firmware to the stock version. So I went to the Odin Website, and downloaded every version, as a couple threads have said that different versions worked for them. Here is a thread with everything you need for Odin. Now, after sorting through and finding micro USB cables that are detectable by Odin, an important step because Odin might develop a pattern of detecting then failing to detect your device through that cable, and testing all the usb 2.0 ports, I was ready, and had Odin with my stock firmware. Odin kept saying "NAND Write", then in the next line "FAIL". This was annoying as Odin wouldn't detect my device again unless I unplugged it, restarted it to download mode, then restarted Odin before plugging it back in. I got confused and found links for somehow fixing the .tar files, stock roms, .pit files (DO NOT MESS AROUND WITHOUT KNOWING WHAT THOSE THINGS DO), and other threads/websites that say to boot into recovery mode , factory reset, then wipe your cache. I could only do that once. After me messing around with all of the above file variants and supposed fixes to help with my issue, I couldn't boot into recovery mode, it got stuck on the "Samsung Galaxy S6 Edge" logo. It did not fix the NAND write failing. There however, are a lot of websites allowing you to download stock software for your phones, and I don't think I can link them as it might break a rule. Surprisingly, some have claimed that using a stock file for another device worked to fix their problem. This thread, which convinced me to use Smart Switch when it failed for everyone else, was very useful, although I recommend downloading Smart Switch from the official website of Samsung. None of the Odin flashing had worked so far, including the Roms and .pit files so I tried Smart Switch. I opened it, and upon selecting the "more" tab on the upper right corner, a bunch of tabs drop down. One should be "Emergency Software recovery and initialization". I had to find my S / N (Serial) number, and I was very confused on how to obtain that number as I was locked out. But to obtain it, do the same process to boot into download (hold volume down, home key, and power key), but stay on the prompt and don't go to the screen that has the word download in the middle. Don't do anything other then reaching the prompt confirming if you want to install a custom ROM. Then, press the home key and it should show your S / N number along with your IMEI number. Once I imputed the code I saw on my phone into Smart Switch, it told me to connect the device. Now, by this time, I realized that Odin only detects my device if it is actually in the download screen. Why shouldn't my computer? I booted into Download on my phone and followed the steps on my computer, making sure that the computer can recognize my phone while it is using a valid USB port and Cable. And after some waiting, for me, my problem was fixed and I could use my phone again, it reverted to it's out-of-box state. I hope this drawn out but very specific explanation helps you guys. It's my first post And also, this thread confirms that you can use a USB hub for flashing(at least for ROMS), Smart Switch, and for rooting.
Thank you for this detailed account, however nothing of the above has worked for me. Odin won't flash the firmware of 5.0.2 (and I tried 5.1.1) and Smart switch does not recognize the device to do anything. BTW phone has been rooted for months and last night decided to turn on its FRP lock randomly and now I'm stuck. Any help would be greatly appreciated.
Explain throughly what you have tried. Especially different ports, cables, and computers. Did you have the right device drivers? Did you do anything else?
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Xalmey said:
I followed your footsteps and and the step where it has to show me the S/No and IMEI, it only shows IMEI number. I am unable to find the S/NO any suggestions?
Click to expand...
Click to collapse
press vol down home keys and power key once you get to the first blue screen release vol and power keep holdind home but I already tried smart swich didn't help
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
EsperaKing said:
Hi everyone!
I also got a Samsung S6 Edge + from a friend with custom binary blocked by FRP. I don't know what he was planning to do but I guess it was rooting.
He said he want me to backup any files before I try anything. Don't know how to proceed. But as suggestion, I want to ask if using "fastboot oem unlock" command would fix that.
Click to expand...
Click to collapse
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
callumbr1 said:
I'm pretty sure fastboot isn't for Samsung devices. Hard to back up any files u less you can get into TWRP or the phone. If you flash stock firmware is highly likely the files will be wiped
Click to expand...
Click to collapse
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
EsperaKing said:
There is no TWRP recovery on the phone. Yeah you're right about backing up files. I don't even know how to proceed and I can tell you I have huge experience on that stuff, rooting flashing custom recoveries and roms, etc... but in this case, I can't say if files can be backed up.
Click to expand...
Click to collapse
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
callumbr1 said:
The only way is to 're flash the exact same firmware he is currently using now using the 5 files firmware package. But yo ensure csc_home is used so the data will not be wiped.
Click to expand...
Click to collapse
Thank you for you reply.
Please can you tell me where I can find such software or how to do it clearly! I know how to use Odin but I don't know how to exclude user_data to be wiped. Thank you
Bonafid3 said:
5.1.1 has FRP lock auto turned on whenever you have a google account on the device... This is probably going to cause a lot of problems with all newer devices that get rooted. I even tried removing all google accounts, flashed recovery and flashed boot img back to stock after rooting and still FRP was bricking the device. I got supersu onto the device, all working fine for a 3rd time, as soon as I added a google account onto my device and restarted, it was FRP lock blocked and soft bricked again.... I used kies to restore to factory again, re-rooted it for the 4th time when I finally discovered an option in developer options called OEM unlock, Turning OEM unlock on turns off the FRP lock security feature.
My conclusion, If your going to root 5.1.1 make sure you remove all accounts from the device first, do not change google passwords for 72 hours prior to rooting, once rooted, YOU MUST TURN OEM Unlock ON in settings>developer options before adding any google accounts to the device.
Click to expand...
Click to collapse
Thank you thank you thank you!!! This is exactly what I was looking for I had just rooted my note 4 running 6.0.1 and had no idea what the oem option was as no rooting method talked about it at all so naturally as soon as i added my Google account phone restarted and locked up.
Kies was the answer I needed as frp lock was active in download mode and my factory reset in recovery failed everytime but running Kies firmware upgrade and entering my model and serial number it installed perfectly in download mode with frp lock still active saved me alot of hassle ?
Hello,
The last week or so I have been trying to flash TWRP onto my Samsung Galaxy A40 (SM-A405FN) to install LineageOS. However, as I started following different guides and methods I have run into several problems that I can't get around and I was wondering if anyone here has had a similar experience or knows the solution.
The first problem I ran into was that when trying to flash onto the phone, neither ADB nor Fastboot detected the phone in download mode (when it was turned on normally they did). I tried various things to solve it: uninstalling and reinstalling different drivers, trying to find the device in device manager (it wasn't there) and nothing worked. I got around it, however, using Odin to flash. Odin did recognize the phone. I had already unlocked the bootloader and made sure VaultKeeper didn't lock it again. I believe it is fully unlocked now, I have even waited the week period to remove the RMM thing (I'm not entirely sure what it is and if I've done it properly, it's been a while since I've messed with android, but it used to display "KG state: checking" and now it's gone).
So, with Odin recognizing the phone I tried to flash the official TWRP recovery for it, following the instructions on the website. However, after flashing it, the phone bricks and boots into download mode all the time, with the error "Error validating footer (6)" on the top left corner. I have googled far and wide and the only solution I find is to reflash the stock ROM. Of course, this works, but I would like to be able to install LineageOS on the phone.
Thank you for in advance and let me know if you need more information or pictures of some sort.
Bump
Hello,
You can try the tuto on the following link:
It's for samsung A20, but you can apply the same practice for the samsung A40.
The first part of this tuto is woking for me (TWRP) but not the last one: "Rmm bypass"
Best regard's, Gregory