Hi Guy's
I keep seeing everyone talking about using ADB etc to do various things from pushing apk's into system or deleting from System etc however, I have been struggling with the various ways people have briefly said how to do things as in, in a way that everyone already knows exactly what they are doing with the various codes / inputs etc.
Therefore I would be grateful if someone could do a quick step by step guide for me from beginning so I know I'm getting it right.
I'm using R8 Modaco rom with Clockwork and I have noticed already people saying go into recovery and do this and that and I can't even see those options in there.
Thanks for help in advance.
choccy31 said:
Hi Guy's
I keep seeing everyone talking about using ADB etc to do various things from pushing apk's into system or deleting from System etc however, I have been struggling with the various ways people have briefly said how to do things as in, in a way that everyone already knows exactly what they are doing with the various codes / inputs etc.
Therefore I would be grateful if someone could do a quick step by step guide for me from beginning so I know I'm getting it right.
I'm using R8 Modaco rom with Clockwork and I have noticed already people saying go into recovery and do this and that and I can't even see those options in there.
Thanks for help in advance.
Click to expand...
Click to collapse
you will find everything you ever needed to know about using adb here
http://developer.android.com/guide/developing/tools/adb.html
Related
I would like to get everyone's opinion, I'm looking at a couple options of how to get rid of Sprint / HTC Junk that runs at startup and continues to startup - Sprint Nav, Sprint Zone, Nascar, all those things. I'd love to hear alternate suggestions as well.
1. Startup Auditor - Seems to do a decent job of keeping things from starting, definitely reduced boot time, but I'm unsure of how it actually operates - is it just another task killer? Or does it actually take things out of a startup list without running in the background? I've been playing with it for close to a day and am still undecided, at times it seems to help, but other times I don't think it really did anything. It seems like having root would make it completely pointless, since you could edit things yourself.
2. Wait for Root - I already did the OTA update so root is not possible, from what I understand. With root access, I'm sure it would be much easier to remove the actual applications, and furthermore install custom roms without the bloat.
3. ?? You tell me please
Thanks guys!
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
gx1400 said:
If you're comfortable using adb, you can root here: http://forum.xda-developers.com/showthread.php?t=718889
I rooted my yesterday after the OTA and flashed Fresh 0.5.3. It doesn't have most of the crapware.
Click to expand...
Click to collapse
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
berardi said:
Funny I was just reading that. I have zero experience with ADB, but perhaps that is the best route. Can't be too hard to learn, right?
Thanks for posting that. If you have root, it mostly eliminates the need for a program like startup auditor, right?
Click to expand...
Click to collapse
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
okolowicz said:
Correct. Most ROMs already have the crapware removed, however, once rooted you'll also have the ability to remove and do anything else you want.
If you are uncomfortable with adb, don't be. There are enough tutorials and videos around to walk you through the process. Not only was I a complete noob when I moved to Andriod from the iPhone but I am also using a Mac which means the commands are slightly different. However, with a little trial and error I was able to root via adb the very weekend the phone was released when only adb instructions existed.
And, going forward you'll never have to wait for "Idiot Guides" again. Whenever something new and great comes along you'll have the skills to implement it right away.
Click to expand...
Click to collapse
I'm trying to setup ADB right now but I'm stuck here:
http://forum.xda-developers.com/showthread.php?t=694250
3. Enabling ADB support on EVO
If using completely stock EVO, adb will be disabled in recovery and can't be enabled.
Click to expand...
Click to collapse
So if you can't enable ADB on stock EVO, but you need ADB to root - what to do?
EDIT : Nm I think I got it
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
elegantai said:
I want to say that if you plug your phone into your computer and select sync option, that it will install the necessary drivers. Just make sure to turn on usb debugging in your settings menu: menu,settings, applications, development, usb debugging- check the box.
Click to expand...
Click to collapse
Thanks got it..
I'm following these instructions, they seem the most complete. I followed every step successfully and refreshed the pages, and it told me to reboot and run part2. However when I hit
adb reboot
it returns
adb: permission denied
What did I do wrong here?
EDIT: Missed hitting exit. That step wasn't there in original, it is in the recompiled though.
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
elegantai said:
go read up on that thread, do a search for 'permission denied' or the like and I am sure something will come.I saw it a few times while reading that thread
err... Are you sure it didnt just mean reboot your phone?
Click to expand...
Click to collapse
haha thanks I was messed up because the original instructions didn't say to exit the adb shell (I probably should have known though) but now I'm past that, now to reboot and hit adb shell /data/local/part2 in time lol this is fun :-D
All done!!! :-D now to flash rom... good times!
Thanks all
Still kind of a noob to all of this...
I've read multiple threads on how to get these functions working correctly. Most of these either don't make much sense to me, even after hours of trying to research them. Beyond that, after hours of trying and looking through multiple sources, threads, and forums, cannot get ADB working, nor can I get the proper drivers to install (yes I booted in recovery mode, still, no luck, even after manually downloading the drivers.). I have been trying to use ES File Explorer to place files in my /system dir manually.
I have found one thread about how to get MMS and GPS working with CM7, which is what I'm running, but it involves using ADB, as well as updating a PRL (which I have no idea how to do). The following link is where i found this info:
http://forum.xda-developers.com/showthread.php?t=793588&page=4
In addition, I tried flashing Jiminy mod, but I guess I didnt do it right, cuz I noticed to differences or changes. Sorry if it seems like I haven't done my research, because I have. Its just hard to start learning this stuff if there is no clear starting point for learning it all.
I've been trying for about 2 months to get my GPS and MMS working, but to no avail. Please, if anyone has some helpful insight to offer, I would greatly appreciate your time and effort in this. Thanks a lot, guys!
Hey.
Ive done some searching but i just dont know the answer to the question so wanted to check first - Im a new user so couldnt post in the actual ROM thread.
Question. In the install instructions for the HellFire kindle Sandwich 4.04 ROM is says to fix permissions. What is this?
Like i say i have searched that thread and others but just see it referenced as fix permissions. Sorry if im being really dim (its always quite likely!!!)
Look under other in recovery mode it should say fix permissions(at least that's where it is on my rezound)
sent from senseless ics rezound using tapatalk 2
Dammit, I knew it would be simple! Never come across it before!
Thanks for your reply
Can someone explain please what fixing permission does and when it should be done please?
bbc0
Permissions
Hi. This is a bit late, but in case you never figured this out. Fixing permissions just basically makes sure that programs are connected to their separate parts correctly (that's completely in lay terms, not technical). If there are name changes or lost files (like dll's on a computer), then they are cleaned up using the applications' lists of files that it should be associated with. It also makes sure that your access to specific programs is intact. I use it quite frequently as a tune-up - incorrect permissions are often the cause of force-closes, because the device is unable to find a specific file, or it can't gain access to it because the system isn't recognizing the file or the admin privileges correctly.
Hope that helps.
Hey guys,
First off, I don't have any idea where to post this as the phone I'm working with isn't on the forums, so I thought it would be more appropriate here. Please move it into the correct place if there is one. Thank you.
So I'm a new comer of course and I was browsing the internet for solutions to my friends phone issue and I came across this forum. From what I can tell this is a really intellectual environment and therefore was inclined to make an account to see if anyone can help me out with my issue.
The problem(s):
Currently my friend's HTC Wildfire S (T-Mobile) is locked out.
He had tried too many times to unlock it via the pattern and now has to enter in his google email credentials to unlock his phone.
Right now the wifi or data is not on for the phone
Failed solution 1: I tried to call him and have him answer the phone. I then tried to pull the notification tab down in order to enable data or something but that didn't work. I had read on another website that it could work.
Failed solution 2: I downloaded ADB and tried to access the settings.db file in order to edit it via an add on on mozilla firefox. After going to the path where ADB was located i typed in "dir", where settings.db usually is it wasn't there. I then concluded that he probably didn't have USB debugging enabled as that is a strange setting to turn on for no reason.
And now here I am...
He doesn't want a factory reset because he wants his texts, I can only guess that he has important nudes he wishes to save, haha.
Anyway, I'm not too educated in computer or coding language, so if you have any ideas please provide me with some extra details for my noobie status.
As a result of this tinkering, I'm kind of interested in learning how to code and messing around with my Samsung Galaxy S2, so if you also have any pointers for that I'd really appreciate it.
Thanks for your help in advance,
I look forward to engaging in the community and trying to contribute
There is a forum for the Wildfire S. Search at "Type Your Device..." and you'll find it.
Sent From My GT-I9000 Running Mackay ROM KK4.4
86356522
vhngu930 said:
There is a forum for the Wildfire S. Search at "Type Your Device..." and you'll find it.
Sent From My GT-I9000 Running Mackay ROM KK4.4
Click to expand...
Click to collapse
Thank you very much!
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
I am really surprised no one has replied yet, but again I am facing the same problem and I've been searching the Internet for one month now and I found absolutely nothing for this phone (specifically for version A010U).
So I am going to post a different question in the hopes that someone will read it and help us out:
I have two Blu Advance 4.0 L A010U phones, which are identical except for the color (white and green). They were manufactured a month apart one in 10/2015 and one in 9/2015.
Unfortunately after only a couple of months of light use and for no apparent reason (did not drop it, or wet it, etc) it started going through a boot loop. It will start, show the "bold like us" logo then restart again without making it to the operating system at all. Like I said I've been looking for over a month to find a ROM (stock or modded) to reflash but with no luck. Then I had an idea. Since I have the other identical phone that's working fine, is there a trick I can do using the working phone to create a ROM that I can use in my broken one. By the way, the non working phone will allow me to get into the recovery menu, but unfortunately nothing happens if I wipe the cache or even if I reset to factory defaults.
Anyone knows what's causing that "boot loop", how to fix it and where to find a ROM or even "extract" or "create" one using a working Advance 4.0 L ???
Thank you very much!
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Deuler93 said:
Hey guys,
I really need to find at least the stock ROM for the new-ish Blu Advance 4.0L (model A010U), because the most recent OTA update unforgivingly bricked mine. Now I want to try to re-flash the stock ROM, but I am also open to custom ROMs, if there are any available. Please help me out! Thanks in advance
Click to expand...
Click to collapse
I just got ahold of a couple of these devices myself and am in the process of going through all the in's and out's of them....I'm a Samsung nerd so I haven't messed with something like these in a while but I got one (that was supposedly dead bricked per the lady friend of mine I got them from) at least able to boot into factory mode and recovery via ADB and just as I'm posting this I'm in adb shell going through the device's internal memory.....so we'll see what all I find and can pull out of this one and possibly know enough to post an intelligible reply with solutions next time
The boot looping sounds like a common problem with these and when I get to that point I'm going to get rid of the stock bootanimation.zip ASAP and try something else. I get the idea that these things aren't exactly power houses built for much so the littlest thing or small bug in their coding could lead to this kind of crap happening.
Hopefully you figure yours out before I toss these out the window! lol
Cheers y salud!
---------- Post added at 02:27 AM ---------- Previous post was at 02:20 AM ----------
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
Forgot to add a couple things about your post, sorry! I beleive (and I just started digging into this phone) that the no command part is the locked bootloader these phones appear to have. I think it was a combo of holding both volume buttons down from a powered off state then pressing power button on that came up with the option for factory mode or recovery (which led to the sad 'no command' droid), i went into factory mode and theres an option for Tp Upgrade which Im assuming is F/W or something similar but I just hooked up to the PC and in that mode it's reading the internal and external memory of the phone and that's about where I'm at so far.
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
I can't wait to try it, thank you! And btw, were you able to get root successfully and if so, how?
Deuler93 said:
Wow! I'm surprised this thread is still going.
Anywho, I found a repository that is storing the default ROM for the 4.0L. The files were just added recently. I would have liked to have seen a custom Lollipop ROM made by now, but this device is far too irrelevant to get any attention, unfortunately. Just root and forget, I guess.
Click to expand...
Click to collapse
Hey Deuler93 -
You have my respect for digging out that BLU ROMs link and sharing with the rest of us. I downloaded the one for my Advance and used SP flash tool to flash the phone that was stuck on a boot-loop. Of course first I had to download and install the MediaTeK drivers for USB connectivity with my PC. Everything worked flawlessly, no glitches what so ever. All these links are easily found and widely available online if anyone is interested I can share here too. I just hope that this boot-loop was due to some software glitch and not hardware failure. Everything seems to work fine for now, keepint my fingers crossed it will NOT happen again.
Well, one less headache to worry about. By the way we're not that far, if you're ever in the Chicago area, I owe you a beer or something. Thank you!
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
I got temporary root using the kingroot apk. But it messed things up and I don't trust it anymore. None of the other mentioned methods worked for me either, maybe try the PC kingroot method
well this helps one thing
good.m. said:
Man I wish I knew. I'm kinda a novice. I have the same phone with a similar problem... I downloaded the recent ota update and the first time it said it couldn't unzip it. I tried again and it seemed to work but when it rebooted into recovery it said there was an error... So it won't boot up, it just goes to the screen that says "no command". I'm pretty sure the there's a way to make a copy of the working ROM but since I don't use a PC for anything I've never taken the time to learn the method.
Click to expand...
Click to collapse
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
What might happen if a ROM is used for another blu phone. ??
A similar phone as well.
Plz advise.
Damn! This thread just keeps going!
I haven't even looked here in a while, so I will bunch my commentary here. I'm also salaried now, so I bought into a OnePlus X (onyx), a more expensive cheapo device, so I do not use the 4.0L anymore.
As for rooting tools, I used the Kingroot APK successfully in the stock environment. I never tried flashing something SuperSU myself, but it could work. Is flashing a SU app possible from the fastboot interface?
And to Steve's question - it is technically possible to flash a ROM for a different device onto your own device, but is considered a bad idea due to the possibility of introducing incompatibilities and missing proprietary requirements. I feel like this would hold especially true to stock ROMs because the manufacturer probably has no interest in supporting anything more than the device that they are manufacturing for. Doing so removes many possible "compatibility" issues from even having to be considered, but I digress. In short, try to find a ROM made for your device and your device only.
Did you find the zip file for the recovery
Marya Wynter said:
umm. . . when the no command option comes up just press the power button and the rest of options will appear. doesnt exactly solve your problem however unless you have the ZIP file to install, which is what I'm looking for.
Click to expand...
Click to collapse
i root my blu advance 4.0l a010u with the kingoroot PC apk, but i got some issues with the lock screen and some apps, so, i need some advice..
i was looking for a zip to use it via recovery but i can't find any..
Recover IMEI
srspinho said:
Hi guys !
Thank you very much for the Advance 4.0L Roms.
I have successfuly recovered my phone, but the IMEI got lost.
So, I need to root it in order to recover the IMEI, but I just can´t get success on any method :
Kingroot
Framaroot
Towelroot
is there another way to root it ?
Thank you very much.
Click to expand...
Click to collapse
You dont need root to recover imei all you have to do is type *#*#84666364#*#* in your dialer and you will be entered in EngineerMode then go into connectivity ,CDS information and radio information phone 1 or 2 then you will see AT+ type something eg.A then backspace and select the first thing you see. Put a space after AT+ and then put you imei code here "IMEI" between these "" You can find your imei by removing your battery it willl be there. After sending command reboot and imei is back.
links are down....check this instead
Hey guys, links here seems to be down .
Maybe this link would be useful for you all... stock firmware can be downloaded and useful help on videos is available too... Enjoy