Database Users

Who has the most problems??

Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.

The key piece of information to remember is that rooting does't cause the issues we experience. It's the custom ROMs and hacks we install that cause problems
I think most everyone here remembers that we're doing these things at our own risk.
As for the OP, if you don't feel a desire for the features available after rooting or flashing a custom ROM, that's cool. It's not for everyone.
Rooting, flashing, hacking... it's for tinkerers. People who like to find out why something does or doesn't work and then find a fix for it.

I would place a bet on this:
The people who don't have root or don't want to root, and they rarely post their issues in comparision with those who have rooted.
Yes, Most of the issues you see here are self inflicted, but it's what we do. We like a challenge/problem, it gives us something to do. Another reason to stay up till 3 in the morning to find out WHY it's jacked up.
If your issues are so bad, RUU and stick with stock (A whole new set of issues).

We mention our problems so that developers can try and fix them for the next release. In all honesty, Ive had one 1 problem, that was when I installed AOSP 1.6, which btw is/will not supported by our phone officially, I got the dreaded SMS issue that SOME people are experiencing.

Well yea many people post about issues who are rooted, but it is caused by other things they are doing that require it. Simply rooting your device shouldn't cause anything to go wrong.
Roms and other things that require root access tend to be beta, and even if they are not beta they are created by people, and not everything will be perfect.
It is pretty hard to permakill your hero compared to other devices. The only way I know of using the software is through flashing the radio, or messing with ESID and stuff like that.
Which you aren't supposed to do .

Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.

rdisanza said:
Pardon my boldness but I have been on this forum now for awhile and been reading and getting alot of very good information on ROOTING.
I have yet to ROOT my Hero and I am really in a struggle to do so because it seems to me that those of you, for the most part, who have ROOTED your phones are the same people who are having all the problems with this and that appearently because of the ROOT. I mean that folks with stock Hero's very rarely say that something isn't working as it should. App's withstanding. I refer to stock features only.
Reading the problems is the Who's Who of why I think it not a wise choice for me to ROOT at this time.
Anyway, I had my say and my stock Hero works just fine with its 1800 from Mugen. Remember, its a phone, not a pc even tho it share's some pc features.
Thanks for listening...and for a great place to learn.
Click to expand...
Click to collapse
There's not an issue with rooting in and of itself. Take me for instance. I've had some problems with my phone:
1. Apps2SD didn't work...but that was part of a ROM that was being beta tested.
2. Kernel locked up...that was due to an invalid setting I put into the kernel I was building.
3. Lost CPU kernel control...this is something I'm doing wrong in the kernel I am building. I simply restore a control file from a previous build and recompile.
These are things that were expected in testing and needed to be fixed or that I inflicted on my own.
I have a friend who has rooted his Hero, but hasn't applied any of the custom ROMs to his phone (although he has installed applications that require root). He's never had an issue with the phone.
It really depends on what you use it for.

rdisanza said:
Yo Is_907
Not quite the 1st reply I was expecting but a very nice understanding instead. You SIR are a gentlemen and I thank you.
Yes, at the ripe old age of 62 I do believe ROOTing and all that goes with it are for you younger folks who have grown up with computers and like devices. I do tinker somewhat and in fact, my wife and I host a private FREE World of Warcraft ( WOW )server. Been hosting online game servers for about 9 years now and we love it.
Once again, thanks and as you said, I probably need alot more schooling before I would attempt a ROOT. My only problem is AWAKE time, its really high even tho I have removed those apps I can remove to help that situation. Hopefully, 2.1 will help us Non Roots somewhat but if not, then I will strongly consider ROOTing. As long as I know there are people like yourself to help us old dudes.
Thanks again Is_907, and to the rest of you who voiced your opinions, Thanks. All good points and even more reason to consider ROOTing.
Click to expand...
Click to collapse
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.

watzone69 said:
Rooting really isn't too difficult. Just look at the intelligence level of some of the people who have managed to root (before anyone flames me, I'm mainly talking about myself)!
I believe it's entirely possible to root your phone, install a custom ROM that is close to stock, and then live a happy life without ever messing with it again.... Sorry, I couldn't keep a straight face!
Kidding aside, did you update your phone with the Sprint Maintenance Release? You mentioned "awake time" which this patch will fix without the need to root.
Honestly, I mess around with my Hero so much that I am often startled when it rings and I'm reminded that it's a phone.
Click to expand...
Click to collapse
lol I second this my wife hates the fact the I have tis really nice phone and when ever I am at home she can never get ahold of because I am always doing something to it.
to the OP rooting really is not hard I mean if you are hosting a MMORPG server you could surely do it, but if your happy with your phone as is then that is really awesome. I myself when I first got my phone knew ABSOLUTLY NOTHING about android or linux or what in the work a kernel or apk was but with the help of the great community here I have learned so much. Dont get me wrong I am no where near where a lot of the guys on here are but I am learning and helping as much as I can just as those that helped me (i mean I am just happy that I think I could go through and make a theme now lol). if you are happy with the phone as is the only benifit of rooting I would bring up is being able to make backups of everything that way if anything does happen to the phone then you dont have to go trough and redownload apps and set everyhting back up again.
if you do decide to make the leap there are many people here more than willing to help.

Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,

rdisanza said:
Its not the Intelligence thing, I know I can ROOT if I wish either with PreKitchen or the cmd prompt. And YES, I do host a game server and can write script so its not that I don't have the know-how. Its just me, I really don't need to be ROOT'd but the thought of having full control is the thing. Guess you could say I am a Control Freak. If you have ever played online and been part of the game Administration, you know what I mean.
Thanks, I haven't said NO, still just wondering is all.
Regards,
Click to expand...
Click to collapse
oh please understand I wasnt trying to insult you at all, and yes I understand the control thing. thats why I rooted originally but then I flashed my first rom and got addicted. Now if im not changing my phone in some way on a pretty much daily basis I start to get the DT's lol.

No insult taken my friend. The DT's, lol WORD!

Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.

HeroMeng said:
Rooting is actually deceptively easy. All you have to do is download fresh pre-kitchen and hit root. Even from the command prompt (which i used because i don't have access to a windows machine) is still easy. This is literally ALL you have to do: (These are instructions for macs, basically same on windows)
Step 1. Download Android SDK from android.com
Step 2. Download Amon Ra's Sprint Hero Recovery Image
Step 3. Copy the recovery image to root of phone's SD card (name it recovery.img)
Step 4. Open command prompt and navigate to tools folder of the SDK \AndroidSDK\Tools
Step 5. Type the following code with phone plugged in via USB:
Code:
adb shell
#cd /sdcard
#flash_image recovery recovery.img
#reboot recovery
Your phone should then boot into a screen with green text on a black background. Success! You have rooted. (Note: you will need to get the version of Stock ROM with SU for root access.)
Before you reboot the phone go into Backup/Restore>Nandroid Backup Then hit Home to confirm. This will say Performing backup...... and then say Backup complete! You may now hit Reboot System Now and it will start up like normal. Then, mount the SD card, and copy the Nandroid folder to your computer. This is your stock ROM, if anything goes wrong copy this back to the phone and restore it. You may boot into recovery by starting up the phone while holding the home button. Hope this helped.
Click to expand...
Click to collapse
You don't have to push the asroot2 exploit!?!?!!?

Kcarpenter said:
You don't have to push the asroot2 exploit!?!?!!?
Click to expand...
Click to collapse
Not if you're flashing a custom rom that already has it.

You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.

gu1dry said:
You have to have root access to initially install the custom recovery image. So you DO need to push the asroot2 exploit & run it on the phone.
Click to expand...
Click to collapse
I never had to do that when I rooted. Flashed MCR right after I rooted using above method and it worked fine.

Yes the asroot2 exploit is was allows to root the phone, so therefore you had run the exploit initially.

[Beta] Custom ROM (system.img) without unlocked bootloader!!!

FIRST TRY... Edited system.img (KERNEL 2.6.36.3 only!!!)
WARNING: ONLY USE THIS IF YOU HAVE A BACKUP OF YOUR /DEV/BLOCK/MMCBLK0P3 IF YOU DONT HAVE ONE YET, MAKE ONE BY USING THIS:​
IF FROM ADB:
ADB SHELL
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
IF FROM TERMINAL EMULATOR:
SU
IF=/DEV/BLOCK/MMCBLK0P3 OF=/SDCARD/SYSTEM.IMG
THIS IS A FUNCTIONAL FILE SYSTEM, I AM WORKING ON A CUSTOM ROM WITHOUT HAVING TO HAVE THE BOOTLOADER UNLOCKED.
THE ONLY THING THAT HAS CHANGED ON THIS SYSTEM.IMG IS THE BOOT ANIMATION (INSTEAD OF "ANDROID" IT HAS THE HONEYCOMB BEE) AND THE FONT HAS CHANGED ALSO...
AGAIN, THIS IS JUST A TEST, IT IS THE FULL FILE SYSTEM TO BE USED ON A DAILY BASIS BUT DOES NOT HAVE ANY OPTIMIZED FILES AT THIS TIME.
Alright, now that you have read the warning... download this file here:
LINK = http://www.megaupload.com/?d=1YZSDVZI = LINK
You can then push the file through ADB by typing:
dd if=/sdcard/blk0p3_sys.img of=/dev/block/mmcblk0p3
Post if it worked for you or if it did not, this will help me troubleshoot...
PLEASE MAKE SURE THAT YOU MAKE A BACKUP OF YOUR FILES FIRST!!! THIS FILE IS BASED ON USA MODEL 1.104.05_GEN1 ACER A500. I RECOMMEND TO TRY ONLY IF YOU HAVE HAD TO UNBRICK YOUR TABLET BEFORE. I DONT WANT TO MESS UP YOUR TABLET!!! YOU HAVE BEEN WARNED!!! JEJEJE
Please post if it has worked for you or if it glitched, I am currently in trial and error so... my tablet gets bricked 1-3 times a day because I am testing different things on the system images... hopefully, I can find a way to have root on the image or at least include:
1. File manager
2. ROOT or at least the Gingerbreak.apk already installed.
3. Terminal emulator
4. Custom background upon boot
As stated, it works for me but I have only 1 tablet so if you are daring enough, please dont hessitate to help me in getting this up and running...
I AM NOT A DEVELOPER SO PLEASE BARE WITH ME AS I AM TRYING TO LEARN AS I GO... JEJEJE

props to you!
u crazy.

I don't see any attachment or link...

Euclid's Brother said:
I don't see any attachment or link...
Click to expand...
Click to collapse
Sorry about that, i've updated the post... jejeje

Beta Rom
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.

tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
THANKS!!! this is what I am needing... at this time, there is NOTHING ELSE that has been changed on the file system... I am just testing making sure that my changes stick... I am hoping to be able to change some more things... As long as its working... I will continue changing things ... Until I can get an image that is worthy of "Custom ROM" status... jejeje

tomlogan1 said:
Applied your image & got the honeybee and very small print. no other changes notes, moving back to previous system image. still can not get updates due to Chinese ROM unbricking, but that will come in time.
Click to expand...
Click to collapse
Did you fix your issue if you haven't I'm on gtalk if you want help I pulled my hair out for 2.5 days before I fixed it
Sent from my A500 using XDA Premium App

cant figure out how to multiquote as clicking the buttons dont do anything.
but just look at "Crsdr37"'s post in general with the imgs and update zip to get back to stock and updates!!!
and to the person who made the IMG keep up the good work. im not gonna flash it and im happy with being stock and getting updates now ;D

Have you figured out how to apply the incremental updates to the img?
I suspect it's just replacing files, I'll look at it when I get to a PC.

Ive been away from my tablet today. I put the post up and went out tonight... jejeje
Thank you guys that tested my image... if it worked for you, THANKS!!! if ou didnt, then let me know what did not work...
THIS IS NOT NOT NOT AN UPDATED IMAGE, IF YOU CHECK THE DESCRIPTION, THIS IS A TEST IMAGE TO GET A CUSTOM ROM OVER TO THE ACER A500... I AM TESTING SO I WILL NOT ANSWER QUESTIONS ABOUT UPDATES... THAT IS FOR MY OTHER POST... SORRY PEOPLE.

Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.

i am going to try it as well nice thing you guys do

Great
Cheers man, !

So, pulling your system image from /DEV/BLOCK/MMCBLK0P3, then modifying it, then pushing it back works?
Let me try and understand here:
I thought the whole locked bootloader thing checked signatures on the images that are about to be loaded into memory, such as the image in /system.
According to this:
http://www.reddit.com/r/Android/comments/hkbf3/so_you_want_to_know_about_bootloaders_heres_the/
It says:
What does a bootloader do with digital signatures?
It uses them to check any update that passes through it.
So: dd any partition we want to modify, back it up in a safe place, mount the img we get from that, make changes within the img, and dd it back, = all good?
ie: signed bootloaders only have to do with installing update.zips on the sdcard?
Can someone clear this up for me?
Thanks!

Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express

If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.

netham45 said:
If you'd read my question before making an all-caps rude response you'd see that I was asking if you've made any headway into applying the updates, not if you had already done them.
Click to expand...
Click to collapse
Dude, chill man... You are right, your question does ask about headway for the updates but here are the facts:
You are asking about updates on a BETA Rom that is just in testing...
I took your question to be if the ROM file had the updates (My fault for sure). I was not yelling per say nor trying to be rude but rather making sure that people are aware this is in no way an updated image and should not be treated as such... THIS IS A TEST ROM and since your question was posted within its thread, I took it as if it was directed to the image itself and not toward me and my development...
Look, as stated, im not a developer man, this stuff is a little hard for me to do. I do apologize because I did not answer your question correctly/completely but as far as the comment... Its what I meant. jejeje

tomlogan1 said:
Never did. Am back now on the EMEA version and going to wait until someone cracks the code. I have reflashed so much I can do it with my eyes closed.
Click to expand...
Click to collapse
Have restored to complete US stock. Had a lot of problems related to SD cards, had to swap them out to avoid errors on the actual update.zip file, but am back to normal. Now if I can just keep my hands off until the 3.1 update comes out, or there is custom ROM...

mapaz04 said:
Unfortunately, I don't know how to answer that... I have to make my changes through the tab and then pull the system.img. Everytime I make edits externally, my tablet crashes... That's why I'm in testing right now.
sorry guys, I'm not a developer so there are going to be some things I can't answer but if someone is willing to explain it, please do as it is a learning experience for us all... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express
Click to expand...
Click to collapse
That's what I've doing for a while now....I guess I should have shared xD
been installing custom fonts and trying to change some of the system settings from other customized roms directly from the tablet.
Instead of reflashing wouldn't it be easier to just provide the files to push into the tablet? just my 0.02

Yeah, I can provide files for you guys to install but what I was going for was an image that contained everything already setup so you can just flash it over ur old one allowing the "customization" to appear upon install/pushin the file... jejeje
Sent from my WP7 []D[][]V[][]D ARRIVE using Board Express

[HOW-TO] Fix 5 vibrate and black screen

Here was my situation: when trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so I decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way I think makes the most sense, but read all of what I wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what I needed to do and bringing all of their minds together in one place.
The Process
First thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
UPDATE: To clarify: fastboot is a completely separate (although closely related) piece of software from adb. If you do not have "fastboot.exe", download it from http://dottech.org/tipsntricks/2153...ows-computer-for-use-with-your-android-phone/ and follow the instructions there. Or, you can just download the full sdk from google which should include adb and fastboot. I recommend the second option, but my hard drive can take the hit. (thanks BonzTM)
UPDATE: If you get an error saying "The Program can't start because AdbWinApi.dll is missing from your computer" you need to copy that file from platform-tools to tools, then it should work (thanks Jester1614).
If you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
Disclaimer
Note: This is what I experienced with my amoled incredible; in no way do I take responsibility for anything you do. If you try to blame me for bricking your phone I will enjoy a hearty laugh while salting my soup with your tears.

Worked great for me and saved me from the hassle of needing a new phone.
THANK YOU!

goblue13579 said:
here was my situation: When trying to boot the phone, it would go to the splash screen for a few seconds, then go to a black screen and vibrate 5 times. Had to pull the battery to escape. However, when booting after a battery pull with the charger in it booted just fine, but with no sd card recognition or usb/adb functionality. A factory reset and both htc's and verizon's tech support didn't fix it at all. I had this problem and there seemed to be no good guide on how to fix it so i decided to gather all the right sources in one place.
The reason it's messed up comes from the usb problem, which is why plugging it in lets it boot sometimes. So, contrary to all of tech support, fixing the usb is all you need to do to get it working same as usual again. I've outlined the steps below in the way i think makes the most sense, but read all of what i wrote to understand what you're doing before you start. The links are the specific instructions for each piece written by people smarter than me. I only take credit for figuring out what i needed to do and bringing all of their minds together in one place.
the process
first thing is to see if you can get it booted. Best bet is to take out the battery and charger, hold down the power button for 10 seconds, then connect the charger and battery and boot. If you can't do that then your only option would be to try some fastboot adb trickery (which is over my head) or flash the stock rom in hboot from http://www.droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html. Note which radio you have (listed in settings -> about phone somewhere or on top of hboot) to get the right file. If you can get it booted then move to the next step.
To fix the sd card and usb go to http://forum.xda-developers.com/showthread.php?t=695243.
Fastboot is in the tools folder of the android sdk, not platform-tools like adb. To get the drivers working go to http://www.flexjunk.com/2010/05/01/installing-htc-incredible-android-sd-drivers/
if you had to reflash and lost root download z4root from http://forum.xda-developers.com/showthread.php?t=833953 and do a temporary root to be able to run the commands to fix the usb.
Once the sd card and usb are fixed then it should reboot with or without the charger plugged in. Now your phone is stable and will work with unrevoked again and you should be good to go!
disclaimer
note: This is what i experienced with my amoled incredible; in no way do i take responsibility for anything you do. If you try to blame me for bricking your phone i will enjoy a hearty laugh while salting my soup with your tears.
Click to expand...
Click to collapse
u saved my life/phone i love u son

Perfect Solution!
Thanks Thanks Thanks +1

So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb

sofocused715 said:
So...question: Does this mean if you had to reflash and are currently unrooted, that you have to wait for z4root to show up in the market. Because it seems there is no way to root aside from that, and without root no usb, and no usb no adb
Click to expand...
Click to collapse
Actually you can download it from the link I provided in my post to the xda page for it (http://forum.xda-developers.com/showthread.php?t=833953). Scroll to the bottom of the first post and in the attached files there is a version that works. That's what I did, and then you can run the usb fixing commands. Then it's just reboot, re-root, and restore.
Hope this helps.

This thread needs more attention.

This needs to be stickied(sp?) and maybe added to the Development section where it would most likely be looked for first.
If I've helped you, hit the thanks button!

As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.

goblue13579 said:
As you can see by my post count I can't put anything anywhere, so if someone wants to move it feel free.
Click to expand...
Click to collapse
I re-worded your OP and posted it on another forum. I did credit you though. You are now famous.

Cool, thanks!

I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.

brando56894 said:
I wish I would have known this back in March when this happened to me! But then again my phone was S-ON and to get the USB fix to work you said you need root so I might have still been SOL.
Click to expand...
Click to collapse
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.

doug piston said:
That is what the z4 root is for. You dont need s-off, just root. The things are going to s-on by themselves when something is trying to write to the misc, thus the misc brick. PITA brick if ya ask me.
Click to expand...
Click to collapse
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol

wildstang83 said:
Glad yall were able to make something of this. This is gonna save some people since warranties are finally running out. Hey Doug, I seen your thread over on AF. You did a very good job of writing that up.
Oh and thanks for the tiny little peace of credit, heh. Glad I could help 'point' the late and great dougpiston in the right direction on something, lol
Click to expand...
Click to collapse
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.

Thank you goblue13579, wildstang83 and Doug Piston! My phone is totally functional once again.
Odd timing how the problem happened only 2 days ago on my phone, and coincidentally, a fix was hashed out in the same time period after all this time of it being unfixable.
I owe you all a beer! Thanks again!

doug piston said:
Late and great is an over statement. I am just a user like most here. I appreciate you taking the time to reply to my PM. I have been out of the Inc game for some time now so a little direction was very helpful.
Like I said I knew what had to be done but ADB kept ****ting itself, as soon as I read the OP and to use a terminal emulator I slammed my head on my desk.
So simple, I was spending all my time trying to get ADB to run that the idea of the usb being borked hadn't even crossed my mine.
This thread really does deserve more credit and to OP good on ya son. Well done.
Click to expand...
Click to collapse
Yea bud, even I use adb so much that I keep forgetting that there's emulators to use. Its just one of those things we never think about.

Even though it was really more dumb luck and excessive googling that got me to this solution, thanks! I'm glad my compilation has helped so many people. And honestly, it's the least I can do for all the help and goodies I've gotten from these forums and developers.
Happy modding!

What if the devise isn't rooted?

Let the phone sit for an hour with the battery out. Put the battery in after that, should be good
Sent from my 2.3.5 Incredible Obsession

Can you ADB push build.prop from a stock recovery? If not I'm in trouble.

Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.

taboo_ said:
Hey all,
Long story short. I made a backup copy of my build.prop to my internal SD. I edited one line in the /system/build.prop. I rebooted. It was fine. I decided the change I made to build.prop was not necessary so I copied the backup I had on my SDCard of the original file back to /system/. My phone hangs on the "Samsung GALAXY S5 powered by Android" screen during boot.
I'm not experienced with ADB but I am technically inclined so please point out if I'm doing something wrong. I have installed the universal ADB drivers on my computer. I have installed the "Samsung USB drivers". I boot into recovery. I go to "apply update from ADB" (not sure if that is correct). I then run the command "adb devices" in Windows and it lists my device with "sideload" next to it.
I then run "adb pull /system/build.prop" and I get "error: closed". That is as far as I can get.
Any help is greatly appreciated.
Click to expand...
Click to collapse
I would flash a stock rom to get the phone running again, and next time make a nandroid backup that you can restore with a custom recovery before you mess with system files.

I'm currently downloading a stock rom from a very slow source. In the 3hrs or so it's going to take to download I thought I would absolutely confirm I was buggered as it would be nice if a few ADB commands could save me.
gee2012 said:
next time make a nandroid backup with a custom recovery before you mess with system files.
Click to expand...
Click to collapse
I do certainly know better. But Samsung in their power have decided to Knox flag your device if you install a custom recovery. As such creating a nandroid backup was not an option for as long as I want my warranty. I do have Titanium backups, and I thought I was doing the right thing by making a copy of build.prop before doing anything... turns out I was wrong. But really, thanks for your concern and advice.

..

fffft said:
Three hours huh? You should talk to Santa about a faster net connection.
Click to expand...
Click to collapse
I live in Australia. We asked our government and they said yes.... then we got a new government. But in this case it's the speed of the host that was hindering. It's all elementary now anyway as the download finished. No one had replied. I flashed it. It failed. And the long and short of it is adb is now useless to me.
fffft said:
You should know this already though as a five minute search on how to use ADB would have pulled up numerous tutorials.
Click to expand...
Click to collapse
I appreciate the help. But I'd spent all day reading tutorials. Trying commands. Failing. Googling the error. Trying new commands. Failing. Googling those errors. After doing that for some time I thought it would just be more sensible to ask people that have actually had experience.
fffft said:
You're also on the wrong site if you are obsessing over the Knox flag. Yeah, it might affect your warranty. Probably not, but I'll grant that it could. So simply decide up front it you want to modify your phone or wait out your risk free warranty period.
Click to expand...
Click to collapse
So here's the thing. I don't want my cake and eat it. I will absolutely be blowing away knox. I just didn't see a point in doing it preemptively. The phone is only a couple weeks old so I decide it would be wise to at least keep my warranty until I'm happy it's rock solid and I have a good reason to lose it - nice stable Cyanogenmod I'm looking at you. Plus anything I wanted to do up to now I was able to with Towelroot and xposed. I just couldn't Nandroid.
Really. Thanks for listing the commands. As of this morning I hadn't needed to use ADB at all. I appreciate you spelling it out. I just wish I had of seen it mere minutes earlier as I would have been able to let you know if it worked. Unfortunately I didn't. But I appreciate the effort.

..

fffft said:
And you say that your firmware download speed was host limited. I just did a search for half a dozen S5 firmware builds. Found all of them widely disseminated. And as one might expect, not all of the hosts were slow..
Click to expand...
Click to collapse
I was using sammobile.com on a free account. I'm sure I could have found a faster host but I've used sammobile.com many times in the past and they've always been reliable. I'd rather wait longer and get something I trust when I'm not in a hurry than download a file that has the right name but is just from a random "megaupload" link or something.
Now regarding adb I got a lot of the information I needed through google searches. I also watched a number of videos. But here's the thing. If I were just taking the opportunity to learn about adb google-ing around would have been fine. But as the circumstances were a little dire in this situation and I've expressed that I've never used adb before and was not confident. I didn't know what I was doing or have the experience to know the implications of what I was doing. As such 1) I didn't want to take the chances of getting it wrong and screwing myself over further and 2) I seemed to have a fairly unique issue (can't boot, stock recovery, "error: close" issue).
It wasn't just about knowing the commands to use, it was about finding out whether I was even able to do what I was hoping to do from a stock recovery on an S5 (hence the title of the thread).
You're getting a little judgey, which is fine you're entitled to your opinions. But I'd ask you read my title and first post again. It wasn't about just getting the commands outright coz I was too lazy to look, it was about getting a number of questions that I didn't know the answer to due to lack of experience, and that I hadn't had directly answered through google searches. Also I never implied an urgency, it was simply a case of "I had a contingency plan in place (downloading a stock rom) but I thought I may as well ask for some advice in the time I had while waiting for it to download".
It's not as though my case was a dime-a-dozen, "answered directly a million times". It was a little more unique and I had answered many of the general questions myself and decided that my remaining hesitations are best answered by those with experience. I'm sorry that bothers you.

Plus the reason you were able to have so much success is because you have experience and knew what to look for and understood the compounding factors. I had figured your first and third command out for myself. I was missing your second and I don't know if that was my problem, but the error I was getting "error: closed" seems to have a massive lack of documentation on the internet. Not many people are talking about it and those that are pretty much just say "update abd" - I was running the latest version. That is where I was coming undone.
But if you're STILL feeling disconcerted at my efforts here is my session from yesterday right before I made this thread. This is literally only a few of the tabs I had gone through: http://i.imgur.com/WDB3qIg.png

..

I just can not understand why you're being like this man. I've been nothing but polite. But I came on here to learn. If I was doing something blatantly against the community I'd expect to hear about it, but I just wanted help. You gave me help which was awesome but every time I took it or added something to explain my reasoning for my actions you added a lecture with it.
All I was trying to put across to you was that you don't know what I did or my reasoning for asking questions. I was just hoping you could see that your initial assumption about my laziness may not have been correct. Again, I'm not trying to be a **** about this and I really was thankful for the help you gave. But it seems you're more than willing to dish out the criticism but as soon as I defend myself or talk back you in turn get your back up. But I just don't understand why you seemed so interested in making assumptions about my efforts, my internet speeds and then telling me how I should be doing everything differently.

SM-S727VL Root and Recovery

I cannot for the life of me get this phone rooted or a recovery installed. Odin always fails and ADB doesn't recognize the device. Does anyone have any info on rooting this device? I really just want to at least be able to update this thing to nougat.

Nobody knows much about this device since it's not that popular. Some team named TWRP builder built a twrp for the SM-S727VL but it cannot be flashed even when converting to .tar.md5 or .tar.
Also I believe the bootloader on this phone is locked and CROM service does not function (if I am correct) on this device. CROM service will show it being unlocked but it seems to be lying to you.

djared704 said:
Nobody knows much about this device since it's not that popular. Some team named TWRP builder built a twrp for the SM-S727VL but it cannot be flashed even when converting to .tar.md5 or .tar.
Also I believe the bootloader on this phone is locked and CROM service does not function (if I am correct) on this device. CROM service will show it being unlocked but it seems to be lying to you.
Click to expand...
Click to collapse
Well that figures, im willing to use my device to work at it if anyone knows where to start.

I have 3 of these... not a noob but not an expert...say Pre-elite lol. I'm wanting to learn how to go further than use everybody else's solutions to root my phone's if somebody can give me some advice as to where to start as in I know how to root put it that way I was one of the people back in the day with the Evo when it was actually difficult no worries most of them were fine but these files we keep flashing these ROMs these kernels these firmwares where does one start when a phone like this 727 VL is obscure supposedly and nobody is doing anything to be able to root them I have everything that I need I'm sure and if I don't get it. It's somebody point me to a person or in the right direction to get started on what I need to due to learn how to write for I mean what where's the first step on these I've always just use everybody else's files. If that even makes any sense to anybody and anybody can give me a hand or show me the right way I'd be willing to do the work from there on I just need somebody to stick up a finger and say go there.... I mean if we have a twrp written, and we have OEM unlock, then why can't one of us do this I've been around long enough I've read long enough I've never once posted in these forms but I've read them daily... I know I got the skills I just need to know which ones to use. Odin fails like he said, fastboot for some reason still won't recognize, I actually made it one step with one of mine but it has to be a little incorrect because the only thing noticeable is it pops up with vo LTE at the top instead of just regular LTE like this one I'm on now. I was able to flash it with Odin believe it or not with what seems to be possibly just stock S727VLUDU2AQG1_ENG_boot_boxwares.tar
BUT the point is I was able to flash it with Odin and also it did change something because my phone now says there's been unauthorized changes and it wants me to restart it all the time so it can correct itself however it does not, it stays whatever it is, yes I know this is pretty vague however I got to the point where I just started trying anything on one of these phones to see if I could get any kind of anything to work and it did.. kind of.
I will say the USB drivers that's you find every where now do not work you have to go back to looks like version 1.5.5 1.0 SAMSUNG-USB-Driver-for-Mobile-Phones-15510.
With these drivers fast boots if I remember correctly will recognize it when you do fastboot devices however it still hangs on waiting on device. I'm sure I got more information my brains just a little foggy at the moment it is like 3 in the morning and I hope I didn't break any rules posting.
I did try flashing from SD card with no success yet nothing at all just error after error. I have tried twrp however it's supposed to be for this 727 VL I'm sure it's the same one everybody's got because it's only in one place that I've found but it comes up twrp-3.2.1-j7popqltefnvzw-201 and it will not flash.
I realize I have been pretty obscure however there's no reason why if all 5 of us with this VL stick together we can't get it rooted because I'm not going to give up LOL

Keep up the good work
I to have a j7 sky Pro, we need to figure out how to get this bootloader unlocked I would love the links to any from builds or twerp builds you have for this j7POPQLTEFNVZW

twrp
[email protected] said:
I to have a j7 sky Pro, we need to figure out how to get this bootloader unlocked I would love the links to any from builds or twerp builds you have for this j7POPQLTEFNVZW
Click to expand...
Click to collapse
I have a twrp that I managed to find on the internet but i have heard that it was for an older version of the phone. meaning it has to be updated somehow. I do know that the phone had a security patch update on June 1, 2018. I am currently trying to figure out if how to update the twrp or something, but I think I might need a little assistance. Because I am no expert ROM developer or anything of the sort but I am trying to learn, so I can eventually build a custom ROM for this phone.

Masterx4020 said:
I have a twrp that I managed to find on the internet but i have heard that it was for an older version of the phone. meaning it has to be updated somehow. I do know that the phone had a security patch update on June 1, 2018. I am currently trying to figure out if how to update the twrp or something, but I think I might need a little assistance. Because I am no expert ROM developer or anything of the sort but I am trying to learn, so I can eventually build a custom ROM for this phone.
Click to expand...
Click to collapse
Like I said in another thread about this issue, We are not to that bridge yet. The bootloader is locked and we cannot flash it yet.

Justin1198 said:
Like I said in another thread about this issue, We are not to that bridge yet. The bootloader is locked and we cannot flash it yet.
Click to expand...
Click to collapse
Okay, have you tried anything to unlock it. If so can you tell me what you have tried so I can see what doesn't work.

Masterx4020 said:
Okay, have you tried anything to unlock it. If so can you tell me what you have tried so I can see what doesn't work.
Click to expand...
Click to collapse
See post #11 on thread https://forum.xda-developers.com/galaxy-j7/how-to/sm-s727vl-analysis-partition-table-t3858632

Justin1198 said:
See post #11 on thread https://forum.xda-developers.com/galaxy-j7/how-to/sm-s727vl-analysis-partition-table-t3858632
Click to expand...
Click to collapse
Is there a way to tell if the bootloader is locked? (Sorry if I am asking noobish questions. I am just trying to learn.)

You can tell the Bootloader is locked because you get “Secure Check Failed” if you try to flash anything that has been modified. For example; The TWRP recovery file. We need root to bypass the Bootloader.

Allow

allow what
I feel like you're telling me to do something that's way over my head cuz I do not understand what do you mean by allow

I have read write access to root files now !!
I can now access all files on my 2nd of 3 J7s. I am attaching pics. When I try to duplicate and copy on my other J7 ,the factory ones, I get check file permissions access denied. However I've passed it on this one particularly. It also now gives me a security notice on the lock screen of unauthorised actions have been detected please restart phone to correct them. However even when you restart the phone it stays so it isnt temporary. I have actually even going to factory reset to see believe it or not it stays. So the next step would be one in which I need some input to know which files I need to modify to be able to install BusyBox Superuser and from their custom recovery excetra and we're in I believe correct me if I'm wrong.
Can't post pics yet so someone get at me here and I will send them to you to post. Or on my FB at Mighty.Whity.Titan

You can send them to me if you like.

No problem how do I not familiar with these forms
josh0426 said:
You can send them to me if you like.
Click to expand...
Click to collapse
One b a d d a d d i e i o and that said the old Google Mail you know if you want to send me an email I can forward them all to you cuz I can't post them and that's about the best I can do

Pre-Elite said:
One b a d d a d d i e i o and that said the old Google Mail you know if you want to send me an email I can forward them all to you cuz I can't post them and that's about the best I can do
Click to expand...
Click to collapse
[email protected]

Pre-Elite said:
I can now access all files on my 2nd of 3 J7s. I am attaching pics. When I try to duplicate and copy on my other J7 ,the factory ones, I get check file permissions access denied. However I've passed it on this one particularly. It also now gives me a security notice on the lock screen of unauthorised actions have been detected please restart phone to correct them. However even when you restart the phone it stays so it isnt temporary. I have actually even going to factory reset to see believe it or not it stays. So the next step would be one in which I need some input to know which files I need to modify to be able to install BusyBox Superuser and from their custom recovery excetra and we're in I believe correct me if I'm wrong.
Can't post pics yet so someone get at me here and I will send them to you to post. Or on my FB at Mighty.Whity.Titan
Click to expand...
Click to collapse
Can you please share the method that you used to gain read/write access? If you indeed have temp access, I can make it permanent also what firmware build are you on?

Absolutely
I'm not home right now but I'm headed there I'll be there in a couple hours I can if somebody wants to give you their email or email me because I can't post links or anyting I have the file that I used the wrong and I have the driver for Samsung for Odin that I used which I think I've mentioned in my original or previous post and by the way it is not temporary. This is permanent. I did a factory reset and it stays. I just need to know which permissions which file to go to to get my Superuser installed because it's still will not let me install that. But email me or tell me how to send it on here or something that way I can let you guys know or give you guys what I got. I'll tell you this I did not flash it with a v l ROM. I flashed it using a Verizon ROM the only thing that didn't work was my wife I which I think I originally and said back when I made my first comment on this thread I haven't done anything else I set my phone down and it was done clear back there I just didn't realize it. But it is not a VL ROM it's a Verizon ROM a v not a straight talk and my wife I would not which turned out to be something unrelated. I'm in no way trying to keep this from anybody because I know just how much we all want these damn things. But I would sure love to finish the job that I started but I do not mind handing over what I've got.
---------- Post added at 02:53 AM ---------- Previous post was at 02:40 AM ----------
Josh I just emailed you six pictures I just now seen your email in your post and Justin as soon as I get home if you can shoot me an email or get in contact somehow or I can send you everything I got so far once I get there

Here are the pictures