We now know that the new vibrant phones have the hardware key disabled to enter recovery mode. But these phones are not defective. The hardware key has been purposefully disabled as part of a misplaced strategy to secure a phone that has basically no security built into it.
Therefore it is really easy to gain root access to these phones. However the process requires the use of the adb program that is part of the google android sdk. This program likes to run on a 32-bit linux distribution. Since it will not run on a 64 bit system, here is how I managed to gain root access to my phone:
1. Download the sdk from google.
2. Boot into linux on a 32 bit machine. (I used ubuntu live cd on an old Toshiba laptop with an available linux partition to mount on the hd. Your mileage may vary.)
3. If you are not using ubuntu make sure that your c library is compatible.
4. Install the google android sdk on the hd linux partition, e.g. /home/android.
5. Plug your Samsung vibrant into the usb port on the linux machine.
The following steps are specific to ubuntu. The important thing to remember is that the adb program must run its server as root to gain the access we desire.
6. Start the terminal app: Applications > Accessories > Terminal
7. Mount the partition and change to the sdk directory:
sudo mount /dev/sda2 /media
cd /media/*/home/android/tools
7. Start the adb server:
sudo ./adb start-server
8. Make sure your device is recognized:
./adb devices
If you do not see your device connected you have some troubleshooting to do.
9. Reboot your phone into recovery mode:
./adb reboot recovery
Congratulations! You just gained root access to your hardware locked vibrant.
This message has been posted by my old g4 laptop while tethered through t-mobile 3g using wireless tether on my brand new Samsung vibrant.
M_T_M said:
Hmmmm..good enough to stick!
Click to expand...
Click to collapse
Yeah it's good, but you should move this thread to Samsung Vibrant forum.
This works on any android phone.
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
r2d4 said:
Although the method was inspired by the desire to use my vibrant as a g3 modem, the adb program is a general android maintenance tool that runs on linux. So it really doesn't matter what kind of phone you have. Once you have started the adb-server as root the reboot command will boot any android phone plugged into the linux box.
Click to expand...
Click to collapse
Would this also work for the new T-mobile G2 4G ?
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
r2d4 said:
I'm sure we will be seeing more locked phones besides the vibrant and g2. This fix should work for them all. The adb-server gives you root access to your phone provided that you have root access to the machine upon which it runs.
Click to expand...
Click to collapse
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Installing the root update
tjhart85 said:
Keep in mind that no matter what you do on the G2, it'll be wiped on reboot. You can gain root temporarily, but when you reboot, it's gone
Click to expand...
Click to collapse
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
Running the 32 bit distribution cd on your 64 bit system should be fine.
Need help
Hello I need help to unlock my samsung vibrant
can someone tell me where i can fin the link
thank you
r2d4 said:
If you want to keep root after your next reboot, you need to update your filesystem. The first step is to install the programs busybox and su.
Before you boot into recovery mode, make sure you have the update.zip file downloaded onto your phone's internal memory card. Whatever is on this card will be left alone even upon a factory reset. But the phone's internal memory will be wiped. The update.zip file merely installs those two programs to the internal memory and doesn't wipe anything.
1. Download the root update for your phone. Rename the file update.zip and place it on the root directory of your device's internal flash memory.
2. Once you are in recovery mode, use the volume keys to scroll and the power key to select "reinstall packages". (This works on the vibrant. The g2 may be slightly different.)
3. Your phone will reboot and you will find the Superuser app has been installed. This app lets you grant root access to applications that need it.
Now you can download powerful apps from the market to gain even more control over your phone.
I hope this helps.
Click to expand...
Click to collapse
Does boot with a live CD of 32 bit ubuntu on my AMD64 work?? or do i need to boot on a computer with a 32bit processor as well?
unlocking on root system
I was wondering if it was okay to unlock a Samsung Vibrant when it is already rooted?
the JI6 OTA update fixed this issue.
If you upgraded using Kies or ODIN, you may still be HWL, BUT, there is a fix:
If you can not get into download mode, please try this:
** Please note this is for JI6, if you are running froyo do not do this **
untermensch has a fix for those who are HWL'd that seems VERY effective. I always heard some who updated from JFD to JI6 had the HWL fixed automatically, but that was not the case for everyone. It appears those who updated OTA got the fix, but most who did ODIN or Kies did NOT get the HWL issue fixed.
Please see his excellent thread by clicking here. Hope this helps.
If you are using froyo, I imagine you could revert back to JI6 and flash this to fix the HWL.
HWL but scared to update.zip
Hi all. I am running Ji6 and i am still hardware locked. I just want to root my phone so i can delete some stock bloatware.
Can root my phone without having to "fix" HWL. I am wondering, how Kies successfully upgraded my phone to JI6 with HWL? If I upgrade to froyo (once available) will the upgrade access recovery? WIil the upgrade brick my phone?
I know for Froyo there is z4root which seems to be an easy, safe way to root..
So should i plan on waiting for Froyo??
Just fyi... I just had my vibrant warranty replaced through tmobile, when I registered it with samsung the manufacture date showed november. I had no issues getting to recovery using the keypresses.
The whole warranty swap went alot better than I was expecting, phone looks new not refurbed, it came in like 1 or 2 days from when I called, AND they unlocked it for me even though I was at my unlock limit since it was a warranty replacement, just make sure they specify that in the request.
Sent from my Samsung Galaxy S - powered by Team Whiskey™
Thanks for help, T-mobile's Vibrant is hardware locked.
Of course, you don't need either Linux or 32-bit, it worked just fine from a Windows 64-bit machine (and will from any that has a version of ADK for it). Just Shift+right-click in "android-sdk-windows\platform-tools" and select "Open command window here", enter "adb devices" to launch the daemon and make sure your device is connected properly (it needs to be in "USB debugging mode", which you can select in settings), and then enter "adb reboot recovery". Phone should restart, select "Reinstall Packages" using volume keys and power key to enter.
Bought Samsung Vibrant - SGH T959 - Have questions...
Hi all,
I joined the forums recently to learn about rooting my EVO. With the help of a number of people on the forums I was able to easily root my EVO and install a custom ROM. Still haven't flashed any new Kernels yet but I may do that soon.
Anyway, I bought a Samsung Galaxy S (Vibrant) which of course is T-Mobile phone. I got it from my friend for $50 because I know they sell on eBay for anywhere from $250-$350.
However, I recently upgraded the phone for him before I bought it to 2.2 (Froyo). This seems to be bad for me because now I want to Unlock the phone so that it can be used with any carrier, or a carrier aside from T-Mobile but I've read in the forums here that it's hard to Unlock the device if you've upgraded to Froyo via Kies.
Can anyone help me with Unlocking my device and could someone give me a quick rundown of what the key commands are for this phone too? Such as how to access recovery to flash a ROM. Although I am not going to ROOT this device unless it is required in order to unlock the phone.
Thanks in advance for any help!!!
Oh, and I won't get mad if my post needs to be moved to another thread either so please move it to the right place if it needs to be.
Thanks!
PAinguINx said:
Hi all,
I joined the forums recently to learn about rooting my EVO. With the help of a number of people on the forums I was able to easily root my EVO and install a custom ROM. Still haven't flashed any new Kernels yet but I may do that soon.
Anyway, I bought a Samsung Galaxy S (Vibrant) which of course is T-Mobile phone. I got it from my friend for $50 because I know they sell on eBay for anywhere from $250-$350.
However, I recently upgraded the phone for him before I bought it to 2.2 (Froyo). This seems to be bad for me because now I want to Unlock the phone so that it can be used with any carrier, or a carrier aside from T-Mobile but I've read in the forums here that it's hard to Unlock the device if you've upgraded to Froyo via Kies.
Can anyone help me with Unlocking my device and could someone give me a quick rundown of what the key commands are for this phone too? Such as how to access recovery to flash a ROM. Although I am not going to ROOT this device unless it is required in order to unlock the phone.
Thanks in advance for any help!!!
Oh, and I won't get mad if my post needs to be moved to another thread either so please move it to the right place if it needs to be.
Thanks!
Click to expand...
Click to collapse
Well now, I found this http://forum.xda-developers.com/showthread.php?t=761045 but is it cool to do this while running Froyo? And another question, since I bought this phone from a friend can I still have it replaced/fixed (if needed) if the warranty is still active on it?
Thanks!
Back to original ROM by Odin, T959UVJFD.tar and s1_odin_20100512.pit
in dounload mode (down + power)
Related
Dear All
I'm a new android user, I just get a new A50 from Australia and try to root it. It's successful with z4root and I try to install Thai font to system. Unfortuantely I did wrong by deleting font folder in the system, therefore I can't run the system again. When I power on, it still have only garmin asus android logo and can't use it again. Does anyone please let me know how to restore or resolve this problem, or I have to throw it away? Thank you in advance.
Cheers!
Winext
Android 1.6 or the new 2.1 Eclair update?
It's a new Eclair 2.1 update, is there any solution?
Connect it to your computer via USB cable.
Using ADB, try this:
ADB REBOOT RECOVERY.
If it works, a yellow triangle appears with the green android guy.
Hit the HOME button. A menu appears. Use volume up/down to move through the options. Tap power to select it I beleive.
Reset/wipe to factory is one of the options.
If you need it, ADB is found in the Android SDK.
If that doesn't work, try calling in to Garmin for support.
Sent from my Garminfone using XDA App
Dear Spazmogen
Thank you for your suggestion, but I'm really new with ANDROID.
I downloaded ANDROID SDK and try to install but it dodn't work.
I use Win 7 64bit, do I need another software to run this command.
If possible, please let me know some previous post that already teach for beginner.
Thank you in advance.
Cheers!
Winext
ADB is a command line tool. But you will have to get Android SDK installed on the computer 1st.
Read the instructions for installing the SDK here: http://developer.android.com/sdk/index.html
ADB commands: HERE.
Interesting. I got into the recovery screen using the Quick Boot app,used the home button to show the menu. The arrows and volume buttons move, but can't actually do anything. Probably related to missing files that are reported in the data/cache/recovery folder.
https://www.garminasus.com/en_US/support/eclair/006-B1130-00.update
official 2.1 update came out today for USA GARMINFONES. Not the A50 Nuvifones elsewhere in the world...
Is the update different from the leaked one?
Sent from my Garminfone using XDA App
I am waiting for an answer to that question myself. I have no plans to change from the leaked version Garmin posted in mid-November.
Sent from my Garminfone using XDA App
Apparently someone did a bit comparison and said they matched. Plus, I tried and it told me it was the same version. On the plus side, I messed up my recovery partition and recovered it using the backups I made of each partition after I loaded 2.1 (dump_image). I made img backups and tar backups of all the files in 1.6 (I am anal about backing up). Good thing because 2.1 doesn't come with flash_image.
I can get into fastboot and the driver loads and stuff, but I get no devices listed when I do fastboot devices command. Next stop is Ubuntu
I know it works,just need to know how to get to it. Btw,I tried both the Garmin fastboot and adb drivers as well as adding the device hardware id's into the android drivers and neither worked.
I also need to find out if there is a similar enough kernel that I can use to get a fully functional recovery mode. I did find out that you can use adb just fine in the stock one and it loads a serial driver as well.
any possible way I could get that backup you made? I apparently didnt save my backup to the pc. And currrently I messed up permissions on my Garmin trying to get recovery working. I cant run the update or anything.
I've just stumbled across this forum post from google, I too am need of fixing my phone. All that is faulty is that the recovery mode has been overwritten with an incorrect one. Is it possible to extract the recovery image and reflash it from the optus supplied Android 2.1 006-B1130-00.update file?
Or is there a way of just getting say Rom Manager to work some magic for me?
Yes, it is possible... would be easier if someone could just use dump_image on a phone that has a working recovery mode and root access. I can provide the dump app and instructions.
Where can I get the Optus update, and are you positive recovery works on it? Does it also have working fastboot?
And to the other poster, which partition do you need? Btw, Rom manager has a permission fix mode. I can get you a tar file if it is the system partition or your choice of img or tar for the others.
And to everyone, after updating to 2.1, do a master clear because a lot of 1.6 apps are left over... duplicates.
Also, odexing all apps speeds it up a lot, with the caveat that you have to re-run the odex.sh file (found somewhere here and modified by me to be more thorough) after every app update or you will get force closes.
Oh I just reflashed the update again, and I got my recover menu back!
I'm not sure if i need any help anymore, but thanks for your offer of help merwin.
By working, do you mean that you can get to it with a hardware key combination and can actually select items?
first of all ,i 'm sorry for my english .my a50 is dead too.i also delet font folder and i use the adb command 'adb reboot recovery'.but the error is device not found. and my pohone can not boot .it stop at the android guy . how can i setup the device..Q.......Q......help me ..pls
garmin-asus a50
i have this garmin asus a50 was running 2.1 after installing a few apps.
tried to reboot and now is stuck on android screen.
tried hard reset stuck on android screen with wipe userdata on top
please help!
garmin-asus a50 dead
yoyoset
i think i have the same problem please let me know of any progress
thank you
I have an LG Enlighten (Verizon Wireless), not an LG Optimus Slider (Virgin Mobile), running Android 2.3.4 (Gingerbread). I am in desperate need of a root solution. I have searched the online forums to no avail. I have put the phone up for sale for fear that this device may never be rooted. I am calling on XDA Developers to produce a working root before I ultimately rid myself of this thing. To add, I tried running Android SDK (adb). No go. The instructions threw me even after trying them repeatedly on several different occasions. It could be that my laptop
has no internet access, but I'm not entirely sure.
I really enjoy this phone and have customized it to the point of
exhaustion. All I'm waiting for now is ROOT! Please help ASAP...
Have you attempted to root it? Have you tried Superoneclick, z4root, and/or Gingerbreak?
Re: Have you tried to root it?
Yes, I have. Unfortunately, with no success. Results are as follows:
Z4Root - The end result is my phone takes me back to the previous screen (internet, home, games, music, etc.). It begins the rooting process... acquiring shell root. Then it just sticks for approximately 30 seconds and then closes. I have repeated the process on several occasions in the event that something unusual happened the first time around. But the result is always the same.
Gingerbreak - This app just ultimately hangs, endlessly. Approximately two hours worth before I just quit in frustration. But all online forums claim it should take no more than 15 minutes tops. I should also note that I read Z4Root and Gingerbreak will not work on rooting Android 2.3.4 due to the patching of an exploit. However, I did not update my phone to this firmware. It came preinstalled. And I have not found a procedure for downgrading (sbf'ing) an LG Enlighten.
SuperOneClick - This is the one I'm currently trying still. I can't recall the website, but in addition to SOC, it also requires the use of adb from Android SDK. The problem I'm coming across is the laptop I'm using to perform this action is without internet access (which I've tried feverishly to restore to no avail). And I'm thinking this is what the issue may be, but I'm not entirely sure. The only access I have to the internet currently is on my phone. However, I make a weekly trip to the college library (no restrictions on installing, downloading, etc.). So maybe I can try something there.
For the past month, I've been doing extensive research online trying to find any and all information in regards to resolving this matter. A few sites have blamed Verizon for crippling their Android devices from performing certain functions. For instance, this particular device has no "boot into recovery mode" (which I confirmed with a Verizon tech support person). Had it, I easily could've updated with the .zip file from my SD card (which I've now deleted since it's rendered useless).
I did read today that the next version of SuperOneClick v2.3 (to come out at a later date) will include the option for the forced inclusion of adb debugging/android files which could be the solution to my problems. Possibly.
I apologize if this reply post seems a little long-winded. But I wanted to provide you with all the information I have available in order to better recieve instruction as how to proceed forward. I will continue to try the SuperOneClick in hopes that I will acquire root. But if not, I will rely on the expertise of those in the XDA community.
Thanks,
Centim6
Rooting LG Enlighten
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Hi, I too have an LG Enlighten from Verizon wireless. I was just wondering how your root process went? Did the phone work well afterwards? Also do you by any chance have a link to or at least remember the name of the video you watched which helped you to get your phone rooted.
thanks in advance, Angel
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Can you link to the video?
Sparky42 said:
Can you link to the video?
Click to expand...
Click to collapse
seeing as there is no link, I would say no.
secondly, the video posted and my own research indicates that root was possible only if it was v. 2.3.3. There isn't anything available for 2.3.4.
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
fsdfgasgfisd said:
I have rooted my LG Enlighten which was on Gingerbread 2.3.4. I made a tutorial over at phandroids forums since xda does not let me post links to outside sources. Just google Lg Enlighten root and you will find it in the first or second link. Enjoy.
PS: If you do not believe me I made a video of my phone rooted on youtube. My user name there is the same as xda and I posted pictures at the end of my tutorial. Gingerbread 2.3.4 is fully exploitable on the LG Enlighten.
Click to expand...
Click to collapse
I think it would a great idea to include which firmware you used this on. I kbow for a fact that it fails on v4 and v5.
And its not that I don't believe you (I do btw) its just the lack of specifics are going to excite someone and they'll leave you a nasty message cause they thought it would work. So, just a heads up:
Android version:
Firmware version:
Sent from my LG-VS700 using xda premium
I can confirm that the new VS700ZV5 update crippled the ability of this phone to root. I just tried the gingebreak and it didnt work. Any way around this?
Same here, android 2.3.4; firmware VS700ZV5.
I haven't been able to get root to work with SoC....
Any chance someone will figure a way around this update?
please reply to root on you tube PLEASE!
centim said:
Ok. I found the solution. There is a video on youtube which shows you how to do it. And it works. I now have a rooted device! Finally. Thank you for your assistance.
Click to expand...
Click to collapse
Extremely frustrated and hoping you will share this link. I to have tried everything to root my Enlighten to no avail and would appreciate your help more than I can explain! Please! Thank you and congats!
I had my phone rooted, then verizon put out an update, and now I can't root it. I think we're screwed until sombody figures out a new method.
Model: LGVS700
Firmware: VS700ZV5
im not sure if this will help but here, i found this claiming to be able to root the phone.
First, you need the file hboot_2.xx_soff-V8.9.zip, download it.
Unzip it into c:evoroot on your pc.
Second, put your LG Enlighten into development mode by
going to Settings->Applications->Development and turn USB
debugging on.
Third, connect your LG Enlighten to your computer and set
your USB to Just charge.
Fourth, if you get errors with drivers, install their HTC drivers.
(You can also install HTC Sync, but it is bulky!)
Fifth, open up a command prompt by typing cmd.
Sixth, type the following commands: (Or copy and paste,
easier!)
Code:
cd evoroot
adb push root/unrevoked-forever.zip /sdcard/
adb push root/mtd-eng.img /sdcard/
adb push pc36img/PC36IMG-ENG.zip /sdcard/PC36IMG.zip
adb push pc36img/PC36IMG-MR.zip /sdcard/PC36IMG-MR.zip
adb push root/flash_image /data/local/
adb -d install -r root/z4root.apk
Seventh, go to your phone and launch Z4Root app. Then select
temp root and wait until its done.
Eighth,go back to command prompt and type:
Code:
adb shell
su
If you get a pound(#) sign, that means you have temp root,
which just gives you temporary root so we can now install
permanent root.
ninth, go back to command prompt and type the following:
Code:
chmod 0755 /data/local/flash_image
./data/local/flash_image misc /sdcard/mtd-eng.img
sync
And reboot to bootloader mode by typing:
Code:
reboot bootloader
When bootloader mode starts up, it will look for PC36IMG.zip
and after about 3 minutes ask you if you want to install
PC36IMG.zip.
Say Yes by hitting the volume up button, it should now install
the new zip file, should take about 10 minutes. Go grabs some
coffee and come back.
Eleventh, reboot when its done by hitting the volume up
button.
It will reboot into the OS and we dont want that so takes the
battery out and puts it back in it. Then go back to the
bootloader by hitting the power button while holding down
the volume down button.
Choose Bootloader and wait until you get the triangle sign and
type:
Code:
adb push recovery /
adb shell busybox Cinstall /sbin
adb shell nohup /sbin/recovery
&
Go back to your LG Enlighten and you should see green
menus.
Choose install zip from sd card and choose unrevoked-
forever.zip
After that installs, Choose MS-USB
Go to your computer and delete PC36IMG.zip, then rename
PC36IMG-MR.zip to PC36IMG.zip.
Then power off your LG Enlighten, power back on by pressing
Power Button while holding down the Volume Down button,
this should get you back into bootloader mode.
Simply wait and when it asks to install the update, hit the
Volume Up button.
then reboot your LG Enlighten, your device should now be
rooted with Recovery menu then you can flash new ROMs for
LG Enlighten.
LG Enlighten root
I have lg enlighten running 2.3.4 and it is rooted with super user and rom toolbox working. I used POOT.APK which can be found on google. It worked well and everything went smooth. It is a simple and easy to use application. (You can use either SU or SSU)
any way to update it to ics? i have one
Hi all.
I just bought my (Verizon) Samsung Galaxy S4 Mini, so of COURSE I'm going to root the daylights out of it. That part is done. Not only that, it's setup and running as I wanted with one exception: no CWM recovery.
This is the part where now my phone won't even power on. Here's what I did:
(1) I thought "I reeeally want CWM recovery".
(2) I went here and downloaded the touch version of CWM recovery ... labled Samsung Galaxy S4 (Verizon) ...
http://www.clockworkmod.com/rommanager
(3) Not knowing how to install the .img file, I made an attempt to learn how via the following page:
http://answers.yahoo.com/question/index?qid=20130925031702AAqdm7f
after renaming the .img file to simply "recovery.img" and putting in the SD card root, I read on ...
The page reads
Answerer #1 answered 3 months ago
You need to use Terminal emulator.
Instructions:
1. Put it on the root of the internal sdcard
2. Open Terminal App
3. Run :
Code:
su
Then
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p6 bs=4096
4. Reboot and now it would work !
Source(s):
Knowledge
... and now I'm stuck.
My phone refuses to power on. Am I legitimately bricked? Is it over? Is it dead?
I sure hope there's a way to fix this. Can someone please help? I'm good with instructions and willing to Odin if need be.
Model = SCH-l435
I'm 99% sure u just nuked a partition on your phone. While on s4 verizon, that mmcblk0p6 is really a correct recovery partition, on your s4 mini it might just be other partition, system, data or kernel partition. Dd is really a dangerous command to be use, moreover when u don't know what you're doing.
Since u mentioning Odin, did u already tried to flash stock rom with Odin?
And what does "and now i'm stuck" means? Not turning on? Stucked at kernel logo? Stucked at bootanimation?
Softbrick usually easy to recover, just flash stock rom with Odin and phone should be booting again afterward.
Sent from your phone
By "stuck", I mean it's behaving like a hard brick. Nothing happens when I attempt to boot it. There's no logo ... nothing. The phone simply doesn't respond to power buttons at all. Now, I'm on a Mac - and - maaaybe the phone can be accessed via usb? When I plugged it into my wife's PC, the pc did respond with the installation of *some sort of* driver.
Is that a good sign?
I've got both a Mac and a PC at my disposal. Would you be game to throw me links/processes so that I might attempt to see if repair is even possible?
Otherwise, I'll be going into a repair shop as I paid for this phone in full not a week ago.
I really, REALLY both appreciate and need help in diagnosing what must happen to get 'er back up and running.
Fixed!
My S4 Mini was the first that they've worked on. All is well. She was hard bricked, for sure.
Go here. They were well worth it: http://mobiletechvideos.mybigcommerce.com/
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi
1) First root your device using MTK Chopper (from PC) or framaroot (from android app) . Both work fine for MTK phones
2) Then using MTK droid tools backup your ROM. Here is the guide for that
http://forum.xda-developers.com/showthread.php?t=2730031
3)Then using MTK droid tools , make CWM recovery for your phone and install it . Here is guide for that
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Hit THANKS if it works
4shreyas said:
Hi
1) First root your device using MTK Chopper (from PC) or framaroot (from android app) . Both work fine for MTK phones
2) Then using MTK droid tools backup your ROM. Here is the guide for that
http://forum.xda-developers.com/showthread.php?t=2730031
3)Then using MTK droid tools , make CWM recovery for your phone and install it . Here is guide for that
http://forum.xda-developers.com/showpost.php?p=44660171&postcount=417
Hit THANKS if it works
Click to expand...
Click to collapse
I think you mean MOTO Chopper? It doesn't work, same as framaroot. They are old tools, they don't work anymore on the ROMs released after June 2014.
ODIN could work but I have not the sure/right file to download.
Generally speaking, the first thing to do is that of getting a backup of the ROM from the un-rooted phone
The guides that have been reported to work in these cases are:
From XDA:
http://forum.xda-developers.com/showpost.php?p=38337401&postcount=5
From China Devices:
http://www.china-devices.com/Thread-ROOT-CWM-Readback-your-ROM-with-SP-Flash-Tools#
Hereunder is the link to a success case story:
http://www.china-devices.com/Thread-Rooting-new-octacore-S5
There is no way I know to get the root with one-click-tools, there is no case I could find of anybody being able to root these phones by following other procedures.
If anybody knows better, please send me a link (MTK phones with ROM s released after june 2014 only!!!)
My only problem now is that I cannot get the read back with Flash Tools. I have tried uncountable button-pressing combinations, I have put the phone in recovery, download, fastboot mode, I have tried with and without battery, phone switched off or on - no error, but the read-back doesn't start (however my phone doesn't have the USB connection working when it's off or without battery).
The only way to skip this step is, if I had already a copy of the firmware available, a sure one.
Kindly help me if you can
Hi
Odin doesn't work for MTK mate
Try this latest app . It worked for some latest MTK KK phones
http://www.kingoapp.com/index.htm
Some other KK phones got rooted using vroot and rootgenius
Try your luck
Final option is to read back from SPFT which has 90+ success rate
Link to your stock firmaware: ( Official ROM Kingelon G9000 Version: 20140710_e2706v92_jbla_fhd -> This model number matches with model no in your image)
http://www.needrom.com/download/alps-star-kingelon-g9000-style-s5-touchwiz/
As bizarre as this sounds, I managed to get root on a similar phone (another MTK6592 S5 knockoff) with MTK tools. After exhausting my options, I clicked the ADB button and tried to get root shell regardless (via 'adb root shell', which probably isn't the proper command but it works regardless), which caused some sort of hang. After a minute or so I unplugged my phone, which caused things to start responding again; plugging it back in showed me as having temporary root, and the get root button actually worked the next time I tried it. I have no idea how or why it worked, or if it was a once in a lifetime occurrence, but it can't hurt to try.
Also, if your phone is anything like mine (and is actually running some form of KitKat), good luck getting write support for external SD cards. I couldn't get the system partition to mount (to write changes to the necessary file) via anything but ADB shell.
Problem solved
Good to know, thank ypu.
However in the meantime I solved my problem.
My phone works this way: I have to remove the battery and connect it to the USB cable. Then it goes in "preloader mode" and tries to install a driver called "MT65XX preloader driver". This driver actually emulates a COM port. If data transfer doesn't start, then, after a few seconds, the device goes down and disappear from Windows list. So it is easy to miss it when we install all drivers. I had to dowload it (from Google cloud service in my case), install and ... the Read Back started !!! Now I have completed the procedure and my phone is rooted with the CWD recovery installed.
ALPS S5 phone, real FLASHROM total size, 64GB ext SDcard not working
FEGuy said:
As bizarre as this sounds, I managed to get root on a similar phone (another MTK6592 S5 knockoff) with MTK tools. After exhausting my options, I clicked the ADB button and tried to get root shell regardless (via 'adb root shell', which probably isn't the proper command but it works regardless), which caused some sort of hang. After a minute or so I unplugged my phone, which caused things to start responding again; plugging it back in showed me as having temporary root, and the get root button actually worked the next time I tried it. I have no idea how or why it worked, or if it was a once in a lifetime occurrence, but it can't hurt to try.
Also, if your phone is anything like mine (and is actually running some form of KitKat), good luck getting write support for external SD cards. I couldn't get the system partition to mount (to write changes to the necessary file) via anything but ADB shell.
Click to expand...
Click to collapse
Maybe your phone was using firmware dated before june 2014? These was a bug that was exploited by Framaroot, but now they fixed it.
Is your phone also from ALPS? They sold it to me as capable of installing an external 64GB SDHC card, but I cannot have it working. Did you face any similar issue?
Otherwise 32GB cards work fine. Have you tried Aparted app? I use it for formatting/maintenace. This app makes partitioning, I guess it should work.
Also, if your phone is from ALPS, does it really have the ROM memory that is advertised?
I am facing some interesting issues with my phone on this respect. It was sold as having 16GB internal ROM, of which about 12GB avalible for users. In fact, the settings menu shows 10GB ,( 8GB available) of internal memory, and about 4GB of phone memory. Well, if I am correct, this so called internal memory maps to the directory /data (the one highest level in the root), who corresponds to partirtion mmcblk0p7. This partition actually has a size of 2.3GB instead of 10 !!!. f I install and try to run online Nandroid backup, I cannot have it working on paths directed towards the SDcards, but it works on the path data/media. Well, a backup of about 1.2GB is shown in the setting menu of the phone as a memory consumption of about 5 GB !!!
Then I had also hard time in copying this file from the /data directory to one of the SD cards. Root Browser and Root Explorer didn't work, only ES Manager with root rights worked.
Maybe you can give me some advice in finding some tool or SDK procedure to assess what the real total size of the memory is? Or some suggestion on how to fix the ext 64GB card? I got bad feelings with the guys who sold this phone to me, so I would like to collect some more evidence if possible.
I downloaded some applications for making device inspection. They read the manufacturers' data, so they get cheated - even if, in some cases, they can show the right amount of unused memory still available (quite lower than declared by the phone) . Also I cannot see the real size of the RAM memory used by the CPU .
Need stock ROM for Teca g89 mobile.
Hi experts,
I need stock ROM of TECA G89W ANDROID 4.4 2.4GHz 4GB-RAM +32GB 18MP 5.5-inch GPS SMARTPHONE. I brought this phone 6 months back and unfortunately the software corrupted. I tried with other ROMs and currently bricked my phone. If anyone who might have this phone by fortunate can help me to post the stock rom by read back or any process whatever you wish as you know much than me.
Desperately need the ROM file as I want to have my phone back to working.... Thank you....
need that rom
hello. can you ... or someone else, upload that rom again?
the link is no longer online at needrom, and that was the best rom for my kingelon g9000.
i had made a flash to try another rom, but is wasn't better. when i wanted to download again that ALPS rom it was no longer online!
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi see if the link helps you to find the mach of your phone model file:///data/data/com.android.browser/files/kingelon_g9000.mht
---------- Post added at 04:58 PM ---------- Previous post was at 04:53 PM ----------
gt56 said:
Hi, I just bought this phone from TECA Mobility, it turns out to be an Alps S5. See attachement for a detailed description.
I tried to ge the root. I tried some different tools, without success.
MTK Droid Tools ROOT button doesn't work but gives a link to xda's MKT forum, so I started with the recommended procedure. I tried to read back the ROM with SP-FlashTools but no way, it doesn't start. I also made some attempts with the Android SDK but adb backup of course doesn't work for the System partition without root.
When I send the adb reboot recovery command the phone goes in download mode, with the adb reboot bootloader command it goes in fastboot mode, while to have it in the factory recovery mode I have to manually hold down the start and vol down buttons. However, it doesn't matter, the readback does not start.
Should I try to install the CWD recovery without having a backup of the ROM? I think it's too risky. I looked at NEEDROM to see if I can find my ROM, but didn't find. I found these, "S5 SM-G900 MT6592", but I cannot be sure it's the right one.
Somebody can help me? I want to root the device.
Click to expand...
Click to collapse
Hi see if the link helps you to find the mach of your phone model file:///data/data/com.android.browser/files/kingelon_g9000.mht , you can root it using v root you will need a pc to root your phone.
Hi, I am trying to unlock a Galaxy J1 Ace SM-J111F/DS for my colleague. The phone belonged to his younger brother who had passed away in an accident, now that he's gone, we have no information as to now to unlock his phone.
I have tried researching and searching around for methods but to no avail. I was hoping maybe someone here could provide some assistance
A factory reset is out of the question as he needed to access information stored inside the phone
Some device details:
Device is locked by a pattern lock
Unable to unlock via Google account(No one in his family knows his account name/password)
Phone is not Rooted
Phone is FRP Locked
Things I have wanted to try and done so far:
Intended to flash a bypass to unlock the lock screen
Attempted to flash a custom recovery in order to flash the bypass, however FRP is locked and it does not allow a custom recovery to be flashed
Attempted various methods of "security exploits" to unlock, but appears to be patched on current firmware
Tried to search methods of unlocking FRP, however all the methods I've seen so far requires access to developers option, or requires a flash of stock firmware.
Tried accessing device via ADB, however it does not work as USB debugging is not enabled
I'm currently out of options trying to do this by myself, we would really appreciate it if someone could help us out in this
If powered on, and plugged in to PC, is it 'seen' at all?
robneymcplum said:
If powered on, and plugged in to PC, is it 'seen' at all?
Click to expand...
Click to collapse
Yes, it is "seen", but I can't do anything else to it
If it is seen, there is a chance you can get data off it.
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Chilli71 said:
You can install' minimal ADB and fastboot' and the USB drivers for the phone on your PC. If the phone is not encrypted you should be able to browse the phone storage in an adb shell and to copy files or directories with adb pull.
gl
Chilli
Click to expand...
Click to collapse
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
XenoJin said:
I have tried that as well, the only way I can get the phone to appear under "adb devices" is to select "apply update from adb" via recovery, even then it's only via sideloads, running shell returns an error
Click to expand...
Click to collapse
Ill jump in this one to. im in a similar situation. I have a lg g vista that no conventional method is working to bypass frp. Device is not encrypted. My prob is. I believe if i can downgrade back to stock kk which the phone was released with it didnt hve frp then so bam im in. But lgflash tool wont downgrade. Always errors. Loads of diffrent settings have been made. Also followed guides to a t.
But in ure case to if it is possible to dlmode and odin back to kk or earlier u should the be able to skil the google login totally. I dont know if ure device came with kk from factory or lolipop. Frp was implemented in loli so kk should be good. Maybe
Two comments:
1) I have a Huawei G8 in front of me. I worked all weekend with it with bootloader/fastboot. I wanted to test the lock screen/adb behavior, But to my surprise ADB does not find it w/ and w/o lockscreen. --> There are different possibilities why the phone does not show up (it worked in the past with this phone/notebook, but quit working). Before you flash make sure that your setup is working (best with an identical mobile). It seems that USB connection can behave different in Bootloader/Recover/Android OS mode.
2) I made a dirty flash (w/o erasing flash) of Lollipop over Marschmallow last weekend. The result was that many directories including SDCard0 where not accessible. Also user data was not accessible. And you have always the chance that you mess something up when flashing and you loose the content.
If the data is really important your friend could pay a data rescue company (if you don't loose your face). I'm pretty sure that programs exist that can be loaded into RAM with bootloader (fastboot boot) that provide an interface to the PC (in the easiest case, adb again).
Chilli