Guys I can confirm the twrp klte recovery .tar file available on twrp's website works for the Verizon GS5 development edition phone. I am rooted as well
**This thread is aimed at folks who have already acquired the developer phone and need a little guidance and/or concrete evidence that is easy to find regarding how they should proceed with recovery and root. The other threads were geared towards linking folks to a .com site for purchase and the pros and cons of the dev edition.
Follow me @Bash_array
das7982 said:
Guys I can confirm the twrp klte recovery .tar file available on twrp's website works for the Verizon GS5 development edition phone. I am rooted as well
Follow me @Bash_array
Click to expand...
Click to collapse
Did you flash TWRP then install the Superuser zip in order to gain root?
Skeetch79 said:
Did you flash TWRP then install the Superuser zip in order to gain root?
Click to expand...
Click to collapse
Download the superuser.zip file of your choice (I used SuperSu). Flash TWRP Klte recovery image using ODIN.... Bootloader is unlocked out of the box. Then flash superuser zip via TWRP :good:
das7982 said:
Download the superuser.zip file of your choice (I used SuperSu). Flash TWRP Klte recovery image using ODIN.... Bootloader is unlocked out of the box. Then flash superuser zip via TWRP :good:
Click to expand...
Click to collapse
I have the DevS4... so identical process. But DevS4 can also use saferoot and preserve stock recovery
Sent from my SCH-I545 using Tapatalk
Moderator Comment: There is a reason for the report button; please make your comments germane to the thread topic, avoid arguing with anyone in the open forum, and be respectful at all times. We have a threadbare thread due to not following the aforementioned basic standards of decency.
das7982 said:
Guys I can confirm the twrp klte recovery .tar file available on twrp's website works for the Verizon GS5 development edition phone. I am rooted as well
**This thread is aimed at folks who have already acquired the developer phone and need a little guidance and/or concrete evidence that is easy to find regarding how they should proceed with recovery and root. The other threads were geared towards linking folks to a .com site for purchase and the pros and cons of the dev edition.
Follow me @Bash_array
Click to expand...
Click to collapse
Awesome, my DE SG5 is waiting for me at home, will try soon and confirm. Thanks!
How did you guys activate the phone on your verizon account? Did you take it to them or do you just swap sim card?
razzrmaxx said:
How did you guys activate the phone on your verizon account? Did you take it to them or do you just swap sim card?
Click to expand...
Click to collapse
Swap sim cards.
razzrmaxx said:
How did you guys activate the phone on your verizon account? Did you take it to them or do you just swap sim card?
Click to expand...
Click to collapse
I activated online and typed in the IMEI and the serial# of the SIM card that was in the phone.
BTW: it's working fine, here are the files I used:
1. Drivers: http://forum.xda-developers.com/showthread.php?t=2038555
2. Odin: http://samsung-updates.com/Odin307.zip
3. TWRP: http://techerrata.com/browse/twrp2/klte
4. Root: http://download.chainfire.eu/396/SuperSU/
Hey I'm very happy that you posted this thread up. I got my s5 Developer Edition a couple of days ago and it been sitting until someone could confirm this. With that being said.
What should us owners of the S5 Developer Edition do next? How could we retain a factory img of our current firmware (without losing unlocked bootlaoder status) since there is no factory image available directly from Samsung or verizon. Also, could we flash roms from other devices such as 900f, 900t, etc.... ?
sinfulmatik said:
Hey I'm very happy that you posted this thread up. I got my s5 Developer Edition a couple of days ago and it been sitting until someone could confirm this. With that being said.
What should us owners of the S5 Developer Edition do next? How could we retain a factory img of our current firmware (without losing unlocked bootlaoder status) since there is no factory image available directly from Samsung or verizon. Also, could we flash roms from other devices such as 900f, 900t, etc.... ?
Click to expand...
Click to collapse
Once you accomplish root, the next step you should immediately take is dd all partitions!!! I mean all!! Make a back up of all partitions!!! There are no official ODIN images available for the DevS4 or DevS5 - all images have come from the community. We have rooted our devices and backed up the partitions in case something goes wrong and we need to recover. Again, back up system, cache, radio, modem, aboot, recovery, etc etc etc....all!
You can run the following command from either the Android Terminal Emulator app on your phone (as "su") or (assuming the Samsung drivers and ADB are set up properly on your computer) plug your phone into your PC, open up a command prompt as administrator, type, without quotes, "adb shell", then type "su", grant superuser access. Type "ls -l /dev/block/platform/msm_sdcc.1/by-name/" (those are lower case "L"'s BTW). This will print out a list of all your partitions, then proceed to back them up.
You can back them up from either your Terminal app on the phone as "su" or PC again in a command prompt and ADB Shell as "su".
For example, to back up your system partition, you can try: dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/mnt/extSdCard/system.img.ext4
This will back up the partition (which is 2+GB) to your external card on your phone. You can change the directory (destination path if you want). Then after you are complete with all the partition backups, adb pull them or transfer them to your PC.
Some of the partition files names should be saved as:
aboot.mbn (ABOOT partition)
boot.img (boot partition)
NON-HLOS.bin (radio partition)
recovery.img (recovery partition)
modem.bin (modem partition)
and so on and so forth
For my Galaxy S4 Dev here are all the commands which I ran after getting my partition list while on I545OYUEMK2:
adb shell "su -c mkdir /mnt/extSdCard/MK2dump"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/mnt/extSdCard/MK2dump/aboot.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/apnhlos of=/mnt/extSdCard/MK2dump/NON-HLOS.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/backup of=/mnt/extSdCard/MK2dump/backup.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/mnt/extSdCard/MK2dump/boot.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/mnt/extSdCard/MK2dump/cache.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/carrier of=/mnt/extSdCard/MK2dump/carrier.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/mnt/extSdCard/MK2dump/efs.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/mnt/extSdCard/MK2dump/fota.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/mnt/extSdCard/MK2dump/fsg.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/hidden of=/mnt/extSdCard/MK2dump/hidden.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs1 of=/mnt/extSdCard/MK2dump/m9kefs1.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs2 of=/mnt/extSdCard/MK2dump/m9kefs2.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/m9kefs3 of=/mnt/extSdCard/MK2dump/m9kefs3.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/mdm of=/mnt/extSdCard/MK2dump/modem.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/mnt/extSdCard/MK2dump/modemst1.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/mnt/extSdCard/MK2dump/modemst2.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/mnt/extSdCard/MK2dump/pad.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/param of=/mnt/extSdCard/MK2dump/param.lfs'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persdata of=/mnt/extSdCard/MK2dump/persdata.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/mnt/extSdCard/MK2dump/persist.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/mnt/extSdCard/MK2dump/recovery.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/mnt/extSdCard/MK2dump/rpm.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/mnt/extSdCard/MK2dump/sbl1.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl2 of=/mnt/extSdCard/MK2dump/sbl2.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl3 of=/mnt/extSdCard/MK2dump/sbl3.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/mnt/extSdCard/MK2dump/ssd.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/mnt/extSdCard/MK2dump/system.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/mnt/extSdCard/MK2dump/tz.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/mnt/extSdCard/MK2dump/userdata.img.ext4'"
So grateful you guys took the time to share this. I've been holding off on purchasing the DevEd. I have the S4 DeveloperEdition, because I had to get my consumer edition replaced after the MDk bootloader was no more. I love the freedom of an unlocked bootloader, but I've been a little afraid that if they never crack the consumer edition we will never see custom roms for this device.
Do you guys think that if they never unlock the consumer vzw s5 bootloader we will see CM, or other varients make their way to the Developer edition? I know it's just speculation at this point, but If I have to run touchwiz, I may just want to stick with my s4 and return the new one.
Skeetch79 said:
Once you accomplish root, the next step you should immediately take is dd all partitions!!! I mean all!! Make a back up of all partitions!!! (...)
Click to expand...
Click to collapse
Thanks, here is the bat file for the Verizon SG5: (You'll need around 8+GB on your external SD card and around 10 minutes to complete)
Code:
adb shell "su -c mkdir /mnt/extSdCard/ANCGdump"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/aboot of=/mnt/extSdCard/ANCGdump/aboot.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/apnhlos of=/mnt/extSdCard/ANCGdump/NON-HLOS.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/backup of=/mnt/extSdCard/ANCGdump/backup.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/mnt/extSdCard/ANCGdump/boot.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/cache of=/mnt/extSdCard/ANCGdump/cache.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/carrier of=/mnt/extSdCard/ANCGdump/carrier.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/dbi of=/mnt/extSdCard/ANCGdump/dbi.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/ddr of=/mnt/extSdCard/ANCGdump/ddr.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=/mnt/extSdCard/ANCGdump/efs.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fota of=/mnt/extSdCard/ANCGdump/fota.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fsc of=/mnt/extSdCard/ANCGdump/fsc.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/fsg of=/mnt/extSdCard/ANCGdump/fsg.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/mnt/extSdCard/ANCGdump/modem.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst1 of=/mnt/extSdCard/ANCGdump/modemst1.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/modemst2 of=/mnt/extSdCard/ANCGdump/modemst2.bin'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/pad of=/mnt/extSdCard/ANCGdump/pad.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/param of=/mnt/extSdCard/ANCGdump/param.lfs'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persdata of=/mnt/extSdCard/ANCGdump/persdata.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/mnt/extSdCard/ANCGdump/persist.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/recovery of=/mnt/extSdCard/ANCGdump/recovery.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/rpm of=/mnt/extSdCard/ANCGdump/rpm.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/sbl1 of=/mnt/extSdCard/ANCGdump/sbl1.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/ssd of=/mnt/extSdCard/ANCGdump/ssd.img'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/system of=/mnt/extSdCard/ANCGdump/system.img.ext4'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/tz of=/mnt/extSdCard/ANCGdump/tz.mbn'"
adb shell "su -c 'dd if=/dev/block/platform/msm_sdcc.1/by-name/userdata of=/mnt/extSdCard/ANCGdump/userdata.img.ext4'"
sinfulmatik said:
Hey I'm very happy that you posted this thread up. I got my s5 Developer Edition a couple of days ago and it been sitting until someone could confirm this. With that being said.
What should us owners of the S5 Developer Edition do next? How could we retain a factory img of our current firmware (without losing unlocked bootlaoder status) since there is no factory image available directly from Samsung or verizon. Also, could we flash roms from other devices such as 900f, 900t, etc.... ?
Click to expand...
Click to collapse
I'm going to provide a dd of all partitions. However, you'll need to dd your own aboot partition as these are individually unlocked and have unique bootloader keys.
Sent from my SM-G900V using XDA Premium 4 mobile app
razzrmaxx said:
How did you guys activate the phone on your verizon account? Did you take it to them or do you just swap sim card?
Click to expand...
Click to collapse
Just put your Sim in the new phone.
Sent from my SM-G900V using XDA Premium 4 mobile app
Hey thanks guys so much for your help. I will do a soon a I get home. dd all partitions using the bat file got it. Also what about flashing roms for other carrier versions? Other should I wait for a verizon specific rom created by a dev? IIf I were to root wouldn't trip the Knox counter ?
sinfulmatik said:
Hey thanks guys so much for your help. I will do a soon a I get home. dd all partitions using the bat file got it. Also what about flashing roms for other carrier versions? Other should I wait for a verizon specific rom created by a dev? IIf I were to root wouldn't trip the Knox counter ?
Click to expand...
Click to collapse
Not sure about ROMs for other carriers. Stick to either ROMs for Verizon or "universal" ROMs. Who cares about tripping Knox if it does. ... You have a Developer Edition!
Sent from my SCH-I545 using Tapatalk
Skeetch79 said:
Once you accomplish root, the next step you should immediately take is dd all partitions!!! I mean all!! Make a back up of all partitions!!!
Click to expand...
Click to collapse
is there any way to do this complete partition backup prior to voiding the warranty from altering the software?
i am coming from a gnex and rooting is huge deal for me to replace my aging phone. custom roms, not as much, but i need it to be high end, i need it to be rootable, and i need it to be on verizon. (and i KNOW that verizon wont be getting a nexus again after they botched the gnex, which is the vanilla android OS that I want EXACTLY). but this is as close as I can get considering the circumstances and factors at play.
once i saw it was successfully rooted, i went and bought the s5 developer edition an hour ago (and extra battery/battery charger at 50% off with coupon) as i need to stay with Verizon as i am grandfathered unlimited data and have to pay full price for a new phone to keep that. as much a sI dont want to to business with verizon, the unlimited data/coverage/vs speed makes it a no brainer (especially when merely tethering)
this unlocked and rootable s5 (great hardware) seems like the best choice considering all of my personal factors, what has come, and what looks to be on the horizon (replacable battery is a MAJOR issue for me, and an extra battery with build in charger was PERFECT as I now carry 2 spare batteries without a dedicated charger).
i can add a large sd and freeze the bloatware or just deal with it, and can be ok staying with no OTA updates, but I might explore other roms as well if and when they become available if they upgrade android versions successfully and the s5 retail gets rooted eventually
so, to sum up and form a question out of my rambling, is there a way to back up EVERYTHING prior to altering the software or is the only way to do this with root?
I am going to use the s5 developer without rooting for 2 to 3 weeks to make sure the hardware is solid and i wont get hosed by the 30 day hardware warranty (you better believe i am dunking that SOB in water and making sure that it is indeed as claimed, more or less short term, shallow depth, water proof), and i want to do this PRIOR to altering the software/firmware to make sure all the hardware works as claimed, and I would MUCH rather backup every partition immediately after activating, before testing for a couple weeks and dunking it and eventually rooting it
is this possible?
after I am sure the hardware has no issues with warranty, i will be happy to factory reset, then root, then backup.
but can i backup the pre root stock image without, i think it is called triggering the knox by altering the soft/firm ware?
i know i cant reset once i have triggered it, but can i back up all partitions PRIOR to triggering it?
thanks, and this is a general question, not just to you, skeetch. but you certainly bring up a good point
Have any of you tried running a unified build of any AOSP ROMs yet? If there are any out yet... I'm not sure I'm still on an MDK S4 but I'm watching here closely to see how you guys make out. I'd possibly grab a Dev S5 if we could run any unified builds since that opens up many options. Great work by the way!
Sent from my SCH-I545 using Tapatalk
mulch maker said:
is there any way to do this complete partition backup prior to voiding the warranty from altering the software?
Click to expand...
Click to collapse
mulch maker said:
so, to sum up and form a question out of my rambling, is there a way to back up EVERYTHING prior to altering the software or is the only way to do this with root?
Click to expand...
Click to collapse
Umm, ok, in order to back up the partitions you have to root the device. Therefore, you will need to alter the software in order to back up the partitions. But if you are worried about ever having to warranty your device what, about uninstalling root through the superuser app? Another thing, once rooted, you phone may show a boot screen with the word "custom" on it and an open padlock. Unrooting, may remedy this and reset it back to the "official" boot screen. Anyone know if triangleaway could work on the GS5? I know root really hasn't been worked out yet, though.
Can someone chime in?
Related
Okay, So I have a Samsung Admire running 2.3.4 and has a kernel of 2.6.35.7. Purchased 3 weeks ago. I rooted the phone and within a day I had lost the ability to make or receive calls. the phone app crashes every time.and I thought that I had deleted some vital file and thus ruined the phone. After a couple days and nights reading and experimenting I believe that that changing the screen density with Rom Toolbox from 160 to 167 is causing the app to fail. Now the problem is my inability to get rooted again, after resetting back to factory. Nothing I have tried will work and what may, seems baffling. I tried multiply times the original method that was successful, Admire_Root_Windows, Super one click, I tried running both from the SD card, I even downloaded a handful of Android Development programs because I read somewhere that I had to, I'm desperate here. I even came across this :
This was successful with: (I bought the phone 3 days ago)
Android: 2.3.4
Kernel: 2.6.35.7
You need a copy of su, and superuser. (If you have superone click, its all there, just run it adb from that directory)
adb shell "rm /data/log/dumpState_app_native.log 2>/dev/null"
adb shell "ln -s /data/local.prop /data/log/dumpState_app_native.log 2>/dev/null"
adb shell "app_process /dev/null"
REM This command may take a while.
adb shell "echo "ro.kernel.qemu=1" > /data/local.prop 2>/dev/null"
adb reboot
REM Device vibrates (kinda pulses) This is good.
adb wait-for-device
adb shell "rm /data/local.prop 2>/dev/null"
adb shell "rm /data/log/dumpState_app_native.log 2>/dev/null"
adb remount
Thats it, your device is rooted. Now to install the goodies...
adb push su /system/xbin/su
adb shell "chmod 4755 /system/xbin/su"
adb shell "ln -s /system/xbin/su /system/bin/su"
adb install Superuser.apk
Now, before anything else happens, I was having issues with full root. (Root checker claimed everything was fine.. titanium backup worked, but could not remove some crapware..) so at this point, you can go into /system/app and remove the Metro apks. I'd recommend clearing Dalvik cache after you're done as well.
adb reboot
That looks great but there are no instructions and in where does that get typed?
I will have to go buy another at some point tomorrow if I dont get this phone fixed. All I need to do is change the screen res back to 160 and I "think" it will be fine. Everything else runs like a champ. BTW, I do have a LG Optimus T / LG P509 running 2.2. maybe I can use it to fix the other. It's inactive and I have no plans to call tmobile and have it turned on. Please make your answers as though you are dealing with someone who's had a lobotomy, seriously.
How can I reroot?
Thanks,
Zeke
Well...Never mind, I managed to get it figured out...
Thanks,
Zeke
I been looking for an ATT Avail root guide since january, I found this page today and I am wondering if anyone has done this successfully?
if you google "root att avail" it is the top search result link right now and it is at a site called android police.
here is a copy/paste of the article:
New root methods show up all the time, so it's not a huge deal that a rather unknown phone on AT&T is now rooted. So why are we posting about it? Because the root method used is, well... interesting.
It was uncovered by our own Justin Case from TeamAndIRC, and while a big part of the process will look very familiar to some of you, there is one step that induces a wait, what? moment.
Before you get started throwing commands at the little guy, though, you need to grab this file. After that, commence command throwing.
adb shell rm -r /data/local/logs (if this command gives you an error, do not worry, it is precautionary)
adb shell mkdir /data/local/logs
adb shell ln -s /data/local.prop /data/local/logs/loglast1.tar.gz
Dial *983*7668# on your phone. This does a few things, it mounts /system as writable on boot, and creates the loglast1.tar.gz.
Wait about 10 seconds, then continue.
adb shell echo 'ro.kernel.qemu=1' > /data/local.prop (Nod to Rosenberg here)
adb reboot
Once the phone reboots, continue
adb push su /system/xbin/su
adb shell chown 0.0 /system/xbin/su
adb shell chmod 06755 /system/xbin/su
adb shell rm -r /data/local/logs
adb shell rm /data/local.prop
adb shell rm /data/property/persist.sys.ztelog.enable
adb shell rm -r /data/local/rwsystag
Head into the Market and grab the Superuser app.
Done.
Catch that bold part? Looks like someone at ZTE dropped the ball and left seventy-nine developer codes in the retail version of the device. Oops.
Of course, their mistake is your gain. Hell, there's even a code to disable Carrier IQ: *983*24737#. Enter the code, ???, profit.
While this is definitely an unusual and unique find, it's also quite dangerous. This means that any app can mount the system as writable and, from there, basically control everything. As a result, JCase contacted ZTE to let them know of their oversight.
Click to expand...
Click to collapse
if someone could let me know if this is legit, that would be a fantasticism.
yes that is legit.
see my thread:
http://forum.xda-developers.com/showthread.php?t=1437032
Jcase broke it, the loon created a batch file to make it easier
http://forum.xda-developers.com/showpost.php?p=21627136&postcount=37
thats the last version of the batch file
Cool, thanks, for some reason I cannot connect to my avail via usb, I have it in developer mode and unknown sources checked, I ran adb devices command and it does not find my phone and when I try to run or debug in eclipse it does not find my phone there either.
I used it, and now have root. I wish all phones were this easy to root.
I recently received my Transformer back after RMA-ing it for a non functioning screen. Of course, even though the problem lied with the hardware, they still unrooted and reinstalled stock firmware on it. Everything on it works, except for the USB cable that seems to be either not working, or because they installed all my apps and settings back on the tablet, something's wrong. This is a problem when it comes to rooting it again. What I'm trying to do is run the commands through the Terminal Emulator, but here is what happens:
Code:
[email protected]: /sdcard $ adb start-server
* Daemon not running, starting it on port 5038 *
* Daemon started successfully *
[email protected]: /sdcard $ adb connect localhost:5038
connected to localhost:5038
[email protected]: /sdcard $ adb push su /data/local/tmp
error: device not found
So my question is, is it even possible to do this? If not, is there another way to do it?
Thanks in advanced for any help!
adb is the android debugging bridge what it does is changes your shell from your computer to your device so you do not need to run anything that refers to adb from your device
Hmm, run Wolf's exploit but remove 'adb' from all the commands, pretend you're already in the shell. (Because you are)
Thing O Doom said:
Hmm, run Wolf's exploit but remove 'adb' from all the commands, pretend you're already in the shell. (Because you are)
Click to expand...
Click to collapse
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
aldude999 said:
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
Click to expand...
Click to collapse
push is an adb command not a terminal command
mrevankyle said:
push is an adb command not a terminal command
Click to expand...
Click to collapse
I understand that.
I've been trying mv with no luck:
Code:
mv /sdcard/su /data/local/tmp
failed on '/sdcard/su' - Cross-device link
Download a Recovery.zip you want, and then extract the file called 'recoveryblob' out of it. (I highly recommend Rouge XM touch)
Place it on the root of your internal storage /sdcard/.
Run this:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
reboot the tab, get back in, run this:
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot again, then you see a blue bar if it worked.
Then you can access CWM recovery that you just flashed with dd, and use that to install the Superuser or SuperSU .zip
Thing O Doom said:
Download a Recovery.zip you want, and then extract the file called 'recoveryblob' out of it. (I highly recommend Rouge XM touch)
Place it on the root of your internal storage /sdcard/.
Run this:
Code:
mv /data/local/tmp /data/local/tmp.bak
ln -s /dev/block/mmcblk0p4 /data/local/tmp
exit
reboot the tab, get back in, run this:
Code:
dd if=/sdcard/recoveryblob of=/dev/block/mmcblk0p4
reboot again, then you see a blue bar if it worked.
Then you can access CWM recovery that you just flashed with dd, and use that to install the Superuser or SuperSU .zip
Click to expand...
Click to collapse
Code:
mv /data/local/tmp /data/local/tmp.bak
failed on '/data/local/tmp' - Permission denied
EDIT: Also, I've tried chmod, and I get an Operation not permitted error.
This is a TF101 correct? What stock firmware is it running?
You need to get USB working again.
Thing O Doom said:
This is a TF101 correct? What stock firmware is it running?
You need to get USB working again.
Click to expand...
Click to collapse
Yes It's running completely up to date (unfortunately) 9.2.1.24.
aldude999 said:
Yeah, I've tried that too.
Code:
/system/bin/sh: push: not found
Click to expand...
Click to collapse
It might help to understand what is going on. In this case, adb push su /data/tmp becomes "cp su /data/tmp/" if you are running from the terminal. You'll need stronger linux-fu.
You might also need a few extra /'s at the end of *some* of your commands.
sent from my transformer
gee one said:
It might help to understand what is going on. In this case, adb push su /data/tmp becomes "cp su /data/tmp/" if you are running from the terminal. You'll need stronger linux-fu.
You might also need a few extra /'s at the end of *some* of your commands.
sent from my transformer
Click to expand...
Click to collapse
Yeah, I gotcha, but the only command I have that comes close to cp is mv, and all the commands are very strictly limited.
Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me
sunny342 said:
Hello I have a HOX from att with the 1.85 software number.
I attempted to use this method to root my phone. http://forum.xda-developers.com/showthread.php?t=1709296
I proceeded with the instructions as followed and was sucessfully able to run these commands:
adb shell rm /data/data/com.redbend.vdmc/lib/libvd*
adb reboot
adb shell ln -s /data/local.prop /data/data/com.redbend.vdmc/lib/libvdmscomo.so
adb shell ls -l /data/local.prop
adb shell "echo 'ro.kernel.qemu=1' > /data/local.prop"
Now it's time to reboot
adb reboot
After phones reboots
adb remount
The command prompt indicated a successful remount. (At this point on the phone only the notification bar was working and nothing else was on the screen and right now that is where my phone is stuck, but i proceeded on)
I entered this command adb push su /system/xbin/su
and recieved a error
failed to copy 'su' to '/system/xbin/su': Read-only file system
At this point I did not know what to do I proceeded to reboot and then remount again.
Now I am stuck with just the notification bar responding and the settings not opening.
I am hoping anyone can help me also please PM me. I would appreciate any help with my situation.
If possible could someone g chat with me as typing and waiting for replies is taking to long.
Sorry if I come off as needy but the possiblity of losing the phone I recently bought is scaring me
Click to expand...
Click to collapse
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone
sunny342 said:
I ended up just turning off the phone and then opening hboot and doing a factory reset. It got me back to stock so at least I can use my phone
Click to expand...
Click to collapse
When you try and mount your phone, since you factory reset through Hboot, you'll need to reformat your SD card because you corrupted it. Just some information for you.
Factory reset in bootloader, plug it in to comp, bring up "my computer" on your computer. Right click removable storage and choose "format"
Sent from my One X using Tapatalk 2
MODIFIED LG AS730 Root for Revol Wireless Android Version 4.0.4 Kernel 3.0.8 Build IMM76L SW Version AS73012a
March 22, 2013
By: Ruckman
---------------------------------------------------------------
##ENABLE USB DEBUGGING UNDER SETTINGS > DEVELOPMENT > USB Debugging
##PLUG IN USB CORD TO COMPUTER
##PLACE PHONE INTO LG software mode
######(Download lg-as730-4.0.4-root.zip)
######Extract ZIP, and run adb from that folder.
adb shell
######(while in adb shell)
rm /data/local/tmp/profile_calib_m
ln -s /data/local.prop /data/local/tmp/profile_calib_m
exit
adb reboot
######(Wait for FULL phone reboot)
adb shell
######(once in the adb shell again)
echo 'ro.kernel.qemu=1' > /data/local.prop
rm /data/local/tmp/profile_calib_m
exit
adb reboot
######(Wait for FULL phone reboot)
adb remount
adb push su /system/bin/su
adb shell "chmod 6755 /system/bin/su"
adb shell "ln -s /system/bin/su /system/xbin/su 2>/dev/null"
adb push busybox /system/xbin/busybox
adb shell "chmod 755 /system/xbin/busybox"
adb shell "/system/xbin/busybox --install /system/xbin"
adb push Superuser.apk /system/app/Superuser.apk
adb shell rm /data/local.prop
adb reboot
######(You are now ROOTED!)
Sweet. Before this I was just using that scrappy unlock root program.
Sent from my LG-AS730 using xda premium
NomadCF said:
Sweet. Before this I was just using that scrappy unlock root program.
Sent from my LG-AS730 using xda premium
Click to expand...
Click to collapse
I saw that program but it seemed a little spyware laden. So I decided to try and find another way, and after about 6 hours of messing around succeeded. Glad someone else benefited from it as well.
RuckmanXDA said:
I saw that program but it seemed a little spyware laden. So I decided to try and find another way, and after about 6 hours of messing around succeeded. Glad someone else benefited from it as well.
Click to expand...
Click to collapse
Oh it is a POS program with ALLOT of spyware. But since i was using on my virtual PC I didn't really care
But yea thanks again !
PS. What have you really done to yours since you rooted it ? I've been slowly removing the bloat-ware.
NomadCF said:
Oh it is a POS program with ALLOT of spyware. But since i was using on my virtual PC I didn't really care
But yea thanks again !
PS. What have you really done to yours since you rooted it ? I've been slowly removing the bloat-ware.
Click to expand...
Click to collapse
I want to compile clockwork recovery but that is a lot more work and i risk perma-bricking my phone, but I have been using titanium backup and root explorer. Be careful of what programs you remove, the phone may have root but it still has a locked bootloader that freaks if you remove the wrong app.
So what apps have you removed safely. I've gone and removed the normal ones (Facebook, exchange, etc).
Sent from my LG-AS730 using xda premium