Related
Hey ive been trying to root my evo all day it is on version 2.1-update1. I was able to root my brothers perfectly fine using the downloads and tutorial from the idiot-proof guide to rooting by thebiles. But on mine I get stuck right at the beginning, when i try to flash the PC36IMG my bootloader says main version older. I feel like ive tried everything if anyone can help I'd reallly appreciate it thanks.
Try simple root, and keep trying. I got that same error even with simple root on my buddies 3 times before it worked. Don't know why. Maybe try copying the pc36img to the sd card instead of letting simple root push it...gl!
I agree with the simple root approach. Not trying to highjack your post but I have a question back at you if I may. You say you have one root EVO and one not root? If so the the root has PRI 1.34 and the nonroot 1.40? Could you perhaps do a data speed comparison on these and post the results? I am real curious...
sorry man i saw your post like 2 minutes too late the simpleroot worked right before i refreshed this page thanks for the help though guys appreciate it
one more quick question while PC36IMG was flashing the 2nd "tp" file said bypassed next to it rather than OK like all the others and the first tp had a blank next to it...is this a problem i should look into before unlocking the nand and all that other good stuff?
No problem glad you got it working. This was kinda like going to the casino...getting up to go to the bathroom...coming back to see someone hit the jackpot on your machine....hahaha!!!
That is normal....mine did that.
thanks man appreciate it...one more question for anyone that can help, im using the idiot proof guide and im on step 56 but when i try to enter the adb shell i get an error from command prompt saying "error: more than one device and emulator" i entered the shell perfectly fine like 2 steps before that and used it to flash the new pc36img rom but now i get this error to enter shell again how do i fix this error?
Okay I came here thinking this might finally be it... but nope I tried all the solutions mentioned here but to no avail. I am frustrated and still getting the main version is older. Does anyone know what is causing this error. Please I'm using usb debugging I wiped and backed my SD and have ota that came out in June. I installed Microsoft net frame and htc drivers. I updated simple root and the update log said this was to fix the error but still getting the same error. Any suggestions
I have the same issue, pretty much have tried everything with no luck, kind bummed at the moment, hope someone can help
Thanks
I got to work FINALLY!!!!!
So finally i got the main version error older NO MORE. So i decided to share what i did in hopes that it will work for all of you frustrated out there.
1) Download simple root from xda forum, dont download it anywhere else. The first time i tried i downloaded it at another android forum and even though it may seem the same, this version for some reason was not pushing the files as it suppose to. So again download from forum. Search for it on XDA.
2) Be patient and prepare yourself.
3) Make sure you on the 147 ota version. Not froyo. or before any version before ota because you can use old simple root.
4) After you download it extract it to a folder. Choose whatever location suits you i like desktop so i can delete file after i use it and keep zip. Be sure to update the program. Open it and let it search for downlaod or go to root folder and search for the updater.
5) Before running the program check the obvious. Is usb debugging enable, Do i have microsoft netframe, Are my phone drivers correct. Is the usb cable correctly connected to my computer and phone. Did i choose charge only when connected to the computer.
6) Now on your phone, and this step did it for me, go to Settings>SDandPhoneStorage>FactoryDataReset. Brace yourself this will wipe data it will not change your version. But if you want do a backup the folder of your contacts and whatever you have in your SD card, this is the time to do so. Mount as disk drive, and remember to change back to CHARGE ONLY. I skipped this because rooting was more important than my girlfriends phone number.
7) Now youre noobiness is ready connect phone double check Step 5. In case you missed something.
8) Run the simple root downloaded from XDA forum. Wait for it to push files is wont take long but me patient. Think of it passing 180mb to sd card so it takes some time.
9) Phone will reboot in a screen with skating androids Push power button and WAIT. It will find file and you shouldnt be getting "main version older" reboot error you where getting if you paid close attention to detail. Now update push volume up.
10) Why so impatient wait for it to update files. Once its down just push volume up for reboot. First time it reboots after root or when u flash a rom it usually takes longer, enough to get u nervous but dont be WAIT.
11) Easy sailing now but youre not done yet. Hit recovery once your phone reboot. Choose the method you want i chose Clockwork it works just fine for flashing roms.
12) Congrats your fully root and can flash that cool rom youve been reading about. Suggestions: DamageControl or Cyanogen but go ahead and try whichever you like.
13) YOURE DONE WOOF
If for some reason, it happened to me with AvaFroyo, when you flash your rom it goes on a loop and keeps rebooting dont panic that is what the recovery is for just put your microSD on a card reader delete the rom that is giving you problem and place another one and Reflash. Read how to flash rom you have to wipe on Recovery menu everytime you flash a different rom.
I hope this helps...Its in plain english not Dev English so...
Is anyone working in any of these for the Samsung Admire?
I have used every method possible and I'm still unable to obtain root... Will admit that this is a quick phone and a definite step-up from the Optimus V...
VanillaTbone said:
I have used every method possible and I'm still unable to obtain root... Will admit that this is a quick phone and a definite step-up from the Optimus V...
Click to expand...
Click to collapse
Here, try this method. It has worked for other users as well as myself.
Note: I am not responsible for what happens to your phone.
Make sure that you have USB Debugging Enabled.
Bump
Same question, anyone working on the capability of flashing cwm or custom roms to the admire?
Is someone working on this by any chance? A few of us are looking to expand the Admire community.
DEVS PPPLLEEEEAAASSSEEEEEEEE!!!!!
yeah but the same dev that achieved root is trying to port it i would post the link but im still new
mpdasher said:
yeah but the same dev that achieved root is trying to port it i would post the link but im still new
Click to expand...
Click to collapse
PM me with the link. Or maybe the name of the site.
Thanks in advance.
on the admire-root-windows.zip i viewed the run.bat file in notepad. there's a line that needs to be changed.
open in notepad and change the line:
adb wait-for-defice
to
adb wait-for-device
the f should be a v lol. then file and save. it works.
actually just checked and even though the thing ran i haven't yet got it to work. i got a segmentation fault of the
adb shell "app_process /dev/null"
line and i dont this the superuser.apk installed right. when it loaded up the phone it asked me what to run it with. i had the option of: go launcher ex and launcher. neither worked. i read online just go to the market and find the app superuser. am trying that now.
---------- Post added at 03:14 AM ---------- Previous post was at 03:10 AM ----------
success!
help please
Somebody out there help us
Hi guys!
I'm interested in helping you guys with this device. I'm purchasing one soon.
Anyways:
has anyone tried unlocking the bootloader.
Download Fastboot and run.
fastboot oem unlock
any one?
so it looks like metropcs wont accept payments with credit cards outside the country. so i cant get the phone. sorry guys!
This would be awesome
rooting samsung admire/Vitality
youtube: watch?v=EEpU8-RBVHo
watch this video too root,,,very self explanatory
and to install clockworkmod:
How to put phone into download mode:
1) Unplug USB, remove battery
2) Re-insert battery
3) Hold down CAMERA button
4) Plug in USB
5) After 4 seconds you will see a screen with a warning about installing a custom OS, with an option to continue (VOL+) or cancel (VOL-).
__________________________________________________
__________________________________________________
Installing ClockworkMod:
Basic ODIN instructions:
1) open odin
2) put your phone into download mode and press Volume Up to continue.
3) connect the phone
4) ensure that you have a yellow com# box (see attached picture)
5) Select the ops file in the ops box (SCHR720.ops is in the zip with odin)
6) in the check boxes in the top left make sure one package and auto reboot are selected
7) in the bottom one package box select the desired tar (admire-cwm.tar that you downloaded)
8 ) click start! Your phone will reboot when finished and you can close out Odin.
Recovery mode for the Admire:
1) Turn phone off.
2) Press and hold Back, Volume Down, and Power keys.
3) Continue holding all three keys until device powers on and recovery menu appears.
Navigate using volume up/down keys, and Home key for enter.
Downloads:add the www before each link
unleashedprepaids.com/media/phones/Admire/admire-cwm.tar[/url]
unleashedprepaids.com/media/phones/Admire/Odin+OPS.zip[/url]
Admiral Beast in the ACSyndicate has delivered a ROM for the Samsung Admire (or Samsung Vitality if your a Cricket carrier) that works successfully for me.
forums[dot]acsyndicate[dot]net/showthread.php?5066-ROM-Admiral-Beast-CWM
Sorry for the above linklessness, forum won't let me post links just yet.
Thanks for the help with this phone... I did have a helluva time trying to find the proper driver for this phone.. I can't even imagine how many Samsung drivers are installed on my PC now with all these samsung phones I have rooted and ROM'ed.
Hopefully we will see someone port the Cynogenmod to this phone or finish what the one guy may or may not have started...
Thanks again!
Yes Please Help US
root of samsung admire.
marcos.lennis said:
Here, try this method. It has worked for other users as well as myself.
Note: I am not responsible for what happens to your phone.
Make sure that you have USB Debugging Enabled.
Click to expand...
Click to collapse
sometimes you might have to run the program 3x or more so just be patient.
you will also have to install the superuser.apk & the busybox.apk
before you will be able to verify you are rooted with root checker.
I am also looking at getting one of these phones in the near future (Vitality through Cricket).
I'll be sure to update this thread with any customizations/themes/ROMs I make in the coming months.
Cheers.
Just picked up this phone today.
Flashed my own root to it -- OK
flashed CWM -- OK
Packaged up system image and xferred to PC for decompile -- OK
I'll be working on a custom ROM for this phone soon enough.
I hear theres a beta CM7 floating around the net somwhere, but its spotty at best.
I'll be making a ROM similar to my OpenPDP/Zio flavors located in my sig.
Look for it.
~Cheers.
Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Probably drivers. Just manually boot into bootloader.. And then flash the factory image.
Sent from my Galaxy Nexus using xda app-developers app
Fastboot reboot-bootloader command will only work if you are already in the bootloader mode anyways...
As @mrgnex said, just do it manually, or use adb commands to boot into bootloader where THEN you use fastboot command.
To manually get into bootloader/fastboot mode; power down, then hold power button and volume up AND down all at same time for few seconds, it'll vibrate and you'll be in the bootloader mode where u can issue the fastboot commands.
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
You don't actually move the factory images onto your phone.
One of the sticky threads here is called "return to stock". That should guide you in the right direction.
Sent from my Galaxy Nexus using xda app-developers app
huzzug said:
Ok. I tried to put the .tgz file onto the cell and tried to install the file from there which is ~250mb. But when i try to select installing from s/d card, it does not show up the file there. I am most cretain i'm doing something wrong, and so would like to know what it is ? Any other guide that could be a little easy to follow ??
Click to expand...
Click to collapse
it's great that you're learning to do this Droid life has a good howto, just google "droidlife how to root galaxy nexus"
if worse comes to worse you can use this toolkit that does it for you, it's called wugfresh google "wugfresh nexus toolkit"
If you want to install ROMs you download the zip right on your device (make sure you get a ROM zip file AND a gapps zip file. They are linked in pretty much every OP for ROMs)
Downloading a ROM zip directly from/on device is easiest because then you do not have to transfer the file(s) over to your device in order to "flash"(aka install). Then all you do is go into recovery mode. Then go to install, then choose your ROM zip file. After that installs, then install gapps file the same way, always install gapps zip AFTER the rom zip.
If you use TWRP as your custom recovery you can "queue" your zip installs(choose rom zip and then you can choose to add another zip file and it will flash them both for ya)
And usually it is recommend to do a factory reset from recovery before you reboot into system. (Make sure to not wipe ALL /data...choose factory reset...wiping ALL /data will wipe /sdcard contents as well)
This all might seem foreign and difficult at first, but once you've done it once or twice(or more... you might become what we call a "crack flasher"-one who is constant changing ROM and kernel and setups lol, that's when it gets REALLY fun) so do not get discouraged. Especially if you don't understand the terminology we all use, you will become familiar with it quickly. And remember, Google is your best friend, almost any questions you might have will yield MANY helpful results when you put in a Google search, highly recommend that if using Google for trying to get useful info to put things like "how to install custom recovery "Galaxy Nexus" xda" to get the best info possible )
And do not be afraid to ask us either if you feel lost. It's easier to prevent an issue than to fix it(though fixing a borled Gnex is fairly easy with all the tools available here and elsewhere)
As for going back completely to stock, as mentioned above, to do that you aren't putting any files onto your device itself. You download them to PC(I use my laptop) and install from there using fastboot. When you download the factory img that is for your specific device and unzip it (I believe they still come compressed... If not ignore that part sorry!) You will see inside there is a script called "flash-all.sh" OR if using windows use the "flash-all.exe" that will automate the fastboot commands needed for a full factory stock restore of the device.
I could link you to posts containing useful how-tos and info and such, but right now I'm viewing forum via Tapatalk app on my device and really gonna be lazy and just say look at the "Sticky posts" in General, Q&A, and Development sections, those are most likely what I would link to you here.
After reading through some of those, if you need clarification of steps taken or something, come on back and let us know.
huzzug said:
Hi,
I require advice as to how i should proceed with my recent purchase blunder.
Background: I required a cell since my current one started acting up with frequent call drops and shut downs. I scoured my local craiglist and got a used Galaxy Nexus for ~$ 100. The guy said it wasn't rooted, and so i proceeded to purchase, but only realised now that the cell is infact rooted, with ClockworkMod (not well versed with droid) and some functions / options do not work as intended. I want to unroot it and i tried to follow this guide, but it gets stuck at
Code:
fastboot reboot-bootloader
saying waiting for device.
Not sure what to do as i'm fine even if i have to stay rooted, but i want the damn thing to work properly.
Also, if anyone can recommend how i go about installing ROM's
Regards,
Click to expand...
Click to collapse
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
SolGoodGuy said:
Not sure getting the GN was a good idea even for $100, surely there must have been better options.
Click to expand...
Click to collapse
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
ashclepdia said:
Maybe on contract for that price yes.
But for $100 no contract, that's not bad for a Gnex.. considering I paid ~400 just over 1.5yrs ago lol. And a highly developed device at that.
MAYBE could have found another device for a little bit more in the 150-200 range that was newer. But 100aint bad for a gnex
Click to expand...
Click to collapse
I see an optimus G on swappa for $115. Much better phone.
Actually, I ain't in US guys. And whatever I found was a personal preference as I wanted this model and not any other.
Bumpity bump
huzzug said:
Bumpity bump
Click to expand...
Click to collapse
Bump?
Did you ever try what I said?
You need to download the factory img needed and run the flash all script...
Edit::
HERE go to this thread.
http://forum.xda-developers.com/showthread.php?t=2726518
Follow my advice there, except make sure to grab maguro img for your device. Be sure to grab the correct package for your device (takju yakju, etc...it will tell u in bootloader mode which one u have)
Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Davy49 said:
Hi,
I'm trying to get into the recovery mode on my LG G5 H830 (T-Mobile / Unlocked) phone. Unless I'm doing something wrong, I can't seem to get into the recovery mode so I can perform a wipe data cache function. I seem to remember reading somewhere else that the only way to get into recovery on this phone is to use a computer to do so. On my desktop computer I already have the android studio application installed, but to be honest I'm still trying to learn how to use it. I don't know why lg makes getting into the recovery mode so difficult. I guess I can try to use the buttons on the phone one more time and see if I have any luck. Also I've read possibly using TWRP will possibly let me perform a wipe data cache function. Thank you for any valid suggestions.
David
Click to expand...
Click to collapse
Hi David!
Holy cow, you've installed the entire studio? That's way more than you need. Just get the Platform Tools here: https://developer.android.com/studio/releases/platform-tools
At a user level, all you'll ever need are ADB and fastboot. Then enable developer settings, enable USB debugging and use the command 'adb reboot recovery'. You sure power + volume down don't work? Or power + volume up for fastboot (to get custom recovery installed)? Note that I have made zero research on this device so it may deviate (I'm on mobile right now). If any of those steps seem difficult or you're unsure how to proceed, just let me know where exactly you're stuck.
Oh and when you send an adb command to your device for the first time (like 'adb devices') it will likely show a trust notification on your screen, asking you to allow this computer to send adb commands. Make sure the remember checkbox is on.
Good luck!
Wrapped with delicious Fajita [emoji896]
Hi Timmy,
Thanks for being nice and explaining the process to me, that sounds pretty easy. Today my biggest problem is getting vanced to install on my amazon fire 7 tablet (2019 Edition). I've had it running normally on there previously, but a couple of day's ago I started the vanced app and noticed that I wasn't signed into my google account anymore. And when I attempted to sign in I received the now famous notice that said google server's were busy, please try again later. But knowing I had it running before, motivates me to get it running again. In the interim, I'm using the Web Tube app.
David
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Timmmmaaahh said:
That's usually a matter of uninstalling both, installing MicroG first, then Vanced.
Wrapped with delicious Fajita [emoji896]
Click to expand...
Click to collapse
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Davy49 said:
Hi Timmy,
Unfortunately I've already tried that, now I'm wondering if it's possibly due to me installing google web view on my tablet. All I can do is just keep trying to figure it out.
Thanks, David
Click to expand...
Click to collapse
Proper reboots in between? I don't see how web view would be related but it's always a good exercise to remove recent installations one by one, retrying Vanced in between. Be sure to share your findings if you encounter a potential culprit. It's important for the community to learn from that.
Hi Timmy (I guess it's okay to use this name),
I think before I do anything else, I'll go back and re-read the instructions on how to properly install it. Unless google has done something on their end, I should be able to get it functioning properly. It was installed previously, that's why I don't know what happened.
Thanks,
David
Hi guys n Gals How you all doing? Staying safe i hope!! Im posting this incase it is of any use to anyone who happens to stumble upon an old tablet as i did, But is absolutely bamboozled with what to do next.
Well then i had been looking for help on this issue with regard to Kindle Jem and done my fair share of reading before signing up here.
I am right out of the wrapper and wet behind the ears with Kindles and the like(1st time rooting anything at all) however i managed to install TWRP 2.8.6.0 on su rooted kindle using the bin4ry method.
I followed step by step a tutorial on Youtube named " KindleFireHD89 to pure android"
1. At first i was getting read/load errors:
when attempting to flash cm10.1 cm11/12 through adb sideload i was getting the error message "unable to read cm 11/12" or "unable to load cm11/12" each time i try to flash the rom.
So I done some research on XDA and found a thread to do with the \LARGEADDRESS issue , so downloaded the program to use more than 2GB ram for the flash process, all to no avail. (THIS WAS ABSOLUTELY NO USE AT ALL)
I soon figured i was copying and pasting the commands for flash/fastboot wrong ( i was forgetting to add .img to the name of the image files i was pasting into the command prompt to flash lol)
2. I done a bit of reading around and saw that most , if not all the files were severely obsolete (like the Jem) so i searched around and first upgraded to TWRP 3.0.0.2 from 2.8.6.0 which i feel made a big difference if not just for a smoother gui alone.
3. As my determination and curiosity got the better of me i began replacing the roms also , flashing newer ones each time in this order:
cm 10.1 (success)
cm 11(success)
cm 12.1 (success)
And finally onto Lineage OS 14.1 along with GApps 7.1 Pico where i remain , however i am unable to fix the bluetooth issue as i dont know the commands/ paths or method to alter the LTE file replacement. (any help with this would be great guys or girls (i know Ladye made a fix i think) i just dont know how to go about editing these files.
I got into the menu brand new , though weirdly it wasnt by the volume up button, it was by turning on/off about 5 times and then holding the POWER button in and finally the TWRP Recovery screen would popup.
### edited### i know this is an old kiindle hence why there is no replies .....
####23rd May 2020 EDITED YET AGAIN ##### So i wondered whether there was a recent newish kinda Rom for the JEM after managing to flash (with great difficulty and beginners syndrome) custom rom in TWRP 3.0.0.2.
As i said earlier this was a kindle that was found and when i got it in out the rain and dried off with the hairdrier treatment , was amazed it still worked. So i figured it was a tough mofo and deserved to live outwith the bin since he made it this far.
Anyway when i checked it out the firehd 8.9 was blacklisted ((((Which i am assuming will mean i at least dont need to worry about disabling OTA updates??????))))
So bottom line and after all the fuss above trying to root etc i got 14.1 lineage os without the bluetooth but ill figure that out soon.
For anyone out there this post may help if you can be bothered to read through it haha.
###Last but not least I would like to thank all the guys n gals who make these mods possible and xda themselves for not binning these old posts for noobs like myself . Respect people . thanks again man ###