Related
Hi! I'm a total cell newbie, so pardon.
I want to root my phone just so I can actually put apps on my SD card. There's a few bits I want to understand first:
I've read that I am not going to want to accept OTAs. I've also read that some phones automatically accept OTAs. Since I don't plan to change my ROM (and I am not entirely sure what ROM refers to... is my "TouchWiz" a ROM?), how can I be sure that my default software isn't going to go trying to install OTAs without asking me?
Is a bricked device actually completely worthless? There's no way to get it back into a working state at ALL, or just no way to get it working without help from your carrier? And what is a "soft brick"?
If I manage to root my phone with the CASUAL one-touch program, how do I unroot if I were interested in doing so?
Please either avoid or explain any jargon you may use in your reply. For instance, if you refer to opening an app.... please just do the courtesy of saying it's an app rather than just assuming I know. If you use an acronym, assume I have no idea what it stands for. It took me forever to figure out what an OTA was, and I still don't quite understand what a ROM is... and that's the extent of my acronyms.
Thanks.
Wow, a lot of demands. Why not start here, as it should answer many of your questions. Threads are stickied for a reason.
http://forum.xda-developers.com/showthread.php?t=2024207
Mandolin Bee said:
Hi! I'm a total cell newbie, so pardon.
I want to root my phone just so I can actually put apps on my SD card. There's a few bits I want to understand first:
I've read that I am not going to want to accept OTAs. I've also read that some phones automatically accept OTAs. Since I don't plan to change my ROM (and I am not entirely sure what ROM refers to... is my "TouchWiz" a ROM?), how can I be sure that my default software isn't going to go trying to install OTAs without asking me?
Is a bricked device actually completely worthless? There's no way to get it back into a working state at ALL, or just no way to get it working without help from your carrier? And what is a "soft brick"?
If I manage to root my phone with the CASUAL one-touch program, how do I unroot if I were interested in doing so?
Please either avoid or explain any jargon you may use in your reply. For instance, if you refer to opening an app.... please just do the courtesy of saying it's an app rather than just assuming I know. If you use an acronym, assume I have no idea what it stands for. It took me forever to figure out what an OTA was, and I still don't quite understand what a ROM is... and that's the extent of my acronyms.
Thanks.
Click to expand...
Click to collapse
Touch wiz is a style of ROM if you will.
Touch wiz roms for Samsung.
Motor blur roms for Motorola.
Sense roms for HTC
Aosp roms for nexus phones.
When you have a "touch wiz ROM"
It builds from the stock base code basically. They add freatures and themes and basically ROMs are endless to what they can do.
My phone never tells me about OTAs.
I believe the only time they do this is when on a stock rooted ROM is when something bad could go wrong
Never had any problems on custom ROMs however.
Next,
Bricked devices are very rare and only happen out of stupidity or carelessness in most cases.
Google will tell you how to fix. But I wouldn't worry about it.
As a very frequent flasher of ROMs I have experienced many of times a soft brick. Or a phone in boot loop.
This is when the device powers on but will not boot up. ( stuck on boot animation or splash screen are most common.)
ALL OF THESE ARE FIXABLE.
You can always wipe in a recovery and normally that fixes it.
Soft bricks normally happen from not wiping or bad download.
Also remember you have Odin as a last resort.
Also you can read the sticky threads in android development to figure out how to unroot
They will give you a better explanation on how to do so.
All this is answered by xda and Google.
They are what taught me what I know
They will teach you as well over time.
PM me if you have any other questions
Hit the thanks button so I feel important!
Haha
God bless the American people.
Ok, you know, today I got my phone, I had been waiting forever, I got it and within 2 hours I screwed it up. I have followed and followed many forums and posts on how to fix this, and I am just.. lost. So please i need your help, I am seriously stressing out, and I know I shouldnt, but this is my first android phone. I am shot right now.
I had unlocked the bootloader, and then I tried to root it, then it rebooted and went into bootloop mode or whatever it is.
I still cannot figure out how to use this Hasoons2000's OX+ AIO kit. So I am just leaving it alone.
Ok the PC doesn't recognize it as a storage device, but the fastboot does recognize it, as I have executed a few commands, like reboot or something, just to test that it works.
My phone is ATT but I am in Russia so there is no sending this anywheres. All I want to do is reboot the OS and have it work again, I dont care what mod or stock rom it is, I just really need some direction here.
I know something about RUU, ATT RUU, Fastboot, some other stuff, I have like 5 pages on XDA pulled up and I cant figure this out.
What is the CMW or TWRP or whatever it is called? How do I flash a zip or an img to the phone? I really just want my phone on again.
Yes Ive done stupid noob stuff, but you learn. So please I am kindly asking for any assistance,
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
somemadcaaant said:
No need to stress. Its fairly hard to brick your phone, good way to learn quick also is to screw with it.
Just need the right guide and I think this will help you since u have fastboot access hopefully. Its a pain rebuiling so read everything so u only have to do it once.
Remember these guides are for different phones so don't use the ruu or recovery links, user my links below.
Your phone is:
AT&T(Evitare)
This guide:
http://forum.xda-developers.com/showthread.php?p=30863908
Or this guide:
http://forum.xda-developers.com/showthread.php?p=27301573
This is for another phone so you need to choose an ATT ruu from here for step 1:
Your phone is a HTC One X+ for AT&T(Evitare)*
http://www.androidfiles.org/ruu/?developer=EvitaRE
More info here for custom recoveries etc which is cwm and twrp for deploying roms, backing up your current installed Rom and general tools for fixing or enhancing your phone, displayed prior to your phone booting into android:
http://forum.xda-developers.com/showthread.php?p=37778531
Sent from my HTC One X+ using xda premium
Click to expand...
Click to collapse
thank you very much I really appreciate your help. I finally figured out the ruu.exe thing, I didnt know they had to be the same numbers, ex 1.15.xxx.xx or whatever.
You see what happened originally was that I unlocked the bootloader, easy pie, but I tried to root it and that is when it started looping. Maybe I didnt understand something, but I seemed to have messed up right there.
Is there really any reason to root? I mean yeah there is super user, but doesnt bootloader help with that a bit? I know BL is for flashing custom roms and all.
May I ask how to flash a custom rom? I really want all of this ATT stuff off of my phone, I really dislike it.
Yes I know I can search, here, google etc. And maybe I should, but I end up getting so many different results, and here and there, and this and that. It really is just easier to talk to one single person who knows what they are doing. So if you could help me, I would again extend my appreciation.
Also I have the android revolution for ox+, and I dont know if it is.. you know.. THE BEST or not. Dont know what to do.
And yes, you live and learn, took me forever with iphones, then I realized hacking and roms and stuff were completely different from iphone. So new game new story.
i have been seeing a lot of threads about rooting this phone, but, they all have windows scripts, even the thread that is said to have a runme.sh does not have it in any of the links that i unzipped - only a runme.bat, but yet, people keep mentioning a runme.sh in it... also, i really don't see any one lying out the steps for doing this with linux.
i'm a noob, and dont really know much about this stuff, but i've done this ONCE before with a galxy exhibit, but it was very easy, i just copied a file to the phone (stock rom?), rebooted into recovery, told it to recover from that file, and i was done.
i have no idea how to do it with my new phone, and so i'm wondering:
1: where can i find the files i need to do this with linux - i just want root, nothing special
2: where can i find the steps necessary to do it - in the easiest manner possible?
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
any help is appreciated.
sentientsystem said:
3: it says i have droid 4.0.4, ICS, but every one who talks about lg l9 p769 says its JB, so, thats a bit odd...
Click to expand...
Click to collapse
Your phone is running ICS 4.0, that is the version which it shipped with. Pretty much everyone on here has upgraded to JB either with software update on the phone or they have manually updated with the offline KDZ flash method.
I dont have any experience in linux so I cant help. I hope you can get your phone rooted!
Sent from my LG-P768 using xda app-developers app
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
sentientsystem said:
i just started to restart my phone into recovery mode to see if i could put cyenogenmod on it without having to root it first, and it's saying "software upgrade ... please wait while upgrading...", so, i guess it's upgrading to JB right now... i'll see shortly.
but even if it does upgrade to JB, i still wouldn't know how to do it on linux. i figured there would just be some files to download, and a sequence of adb commands that i could type into bash, but, i'm kinda lost. i guess i'll wait and see if it upgrades to JB before asking more questions.
thanks.
Click to expand...
Click to collapse
You would need wine and then set it up...
Sent From My Xperia Themed P769
well, i tried that "LGpwn" and it didn't work, as well as a fake lg-recovery app. i figured out that i've got a "10g" phone (P769 V10G ICS). i'm not sure what the next step is. some one mentioned downgrading to JB... is there some where you can point me to for that???
i've GOT to get this t-mobile junk off my damned phone... i've even TRIED to install cyenogenmod, but i can't figure out how to get my phone to go into recovery mode (NOT factory rest) - i've tried volup+power+home and volup+power, and neither seem to be working.
Setup a sandbox, windows xp. LG uses windows, no other way to root as of right now for the t-mobile version.
Sent from my LGMS769 using xda app-developers app
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrade to a samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
sentientsystem said:
yeah, it's starting to look like i'm gonna have to try this with a virtual machine, or, pay some one else to do it, or, go get my money back and downgrad to an samsung galaxy exihibit (not sure if the new model of that phone is just as easy as the exhibit 4g, but, it's screen is about an inch smaller than the lg, and they're all 3 the same price, so i'd rather keep the lg).
just out of curiosity, how do you get this phone to boot into recovery mode? you don't have to root it for that, or have windows, right? you just hit the right keys on the phone, right? i couldn't get it to work, but, maybe i was doing it wrong. and, if you can go into recovery, does it have to be rooted to use a cyenogenmod image, or will it not really know the difference?
thanks again. i'm sure this thread may help other noobs as well.
Click to expand...
Click to collapse
Option #1
If you are rooted on stock T-Mobile 10e or 10g ROM and have the CWM installed from this thread:http://forum.xda-developers.com/showthread.php?t=2095825 follow my instructions.
Place one of these CWM ROM images on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2136204
Place this JB radio firmware from T-Mobile 20d ROM on your SD-Card:
http://forum.xda-developers.com/showthread.php?t=2256350
Power off the device.
After power on the back/menu capacitive buttons will flash repetedly. Press Volume down while the lights are flashing and the phone should go into recovery.
Flash the ROM first.
Flash the radio second.
Reboot.
***Notes***
1.) 20d is the latest T-Mobile, 21b is the latest Wind Mobile. Both work.
2.) 21b is lighter/faster but has no wifi-calling.
3.) 21b will require you to manually enter your APN settings for cellular data and MMS. Be sure to write down your APN settings before flashing this ROM.
4.) Some users say battery life sucks on JB. I notice that 21b is better on battery life than 20d.
Option #2.
In Linux install a Windows VM and follow the standard instructions here:
http://forum.xda-developers.com/showthread.php?t=2173465
Use KVM with a GUI or even easier use VirtualBox.
I'm a die hard linux geek too. I even run linux at work while all of our msp software was written for windows. You are better off just running an old copy of xp inside virtualbox trust me its just easier that way. You can use adb if you like (its the same thing the windows users use in their batch files and just rewrite the bash script, but you will save yourself lots of headaches just using virtualbox. -- my .02
Sent from my LG-P769 using xda premium
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
# what's the difference between unlocked boot loaders and being rooted?
# do you have to unlock the bootloader to get root access?
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
My bad. I should have read through your original question all the way before posting. I see that you are not rooted.
If you are on 10e ROM you can root in Linux:
http://forum.xda-developers.com/showthread.php?t=1990705
It will require rewriting the batch script as a Linux shell script. It is possible but nobody has done it yet.
If you are on 10g you will need Windows. I have also answered your questions below.
sentientsystem said:
i'm not exactly sure what the end result of your instructions are, as i assumed it was to BE rooted, but the first line of your post says "if you are rooted ...", so, i'm guessing you're telling us how to ... unlock the boot loader?
by the way, that reminds me, i still haven't come across any posts on this site that tell noobs:
# what's the unlocked boot loader FOR - why do you need this - what does it do?
It allows you to boot an un-signed kernel. You can boot custom ROMs basically.
# what's the difference between unlocked boot loaders and being rooted?
Root allows you to `su -` to the root user and own the whole system.
# do you have to unlock the bootloader to get root access?
No.
all some one like ME needs, is root access, so that i can edit the /etc/hosts file and test mobile compatibility of web apps on the development server before making them live - and to remove t-mobile damned bloat-ware. i hope this helps others who are trying to understand the basic concepts of getting control over the phone they paid money for.
thanks again. now to find a winxp image to load into a virtual machine...
Click to expand...
Click to collapse
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
sentientsystem said:
yeah, the one t-mobile is selling now is a v10g - so, it's time to play with virtual machine, and hope that usb-access is passed through from ubuntu to the VM.
thanks for answering the other questions. i think this essentially sets things straight.
peace! \m/ (>_<) \m/
Click to expand...
Click to collapse
Welcome!
I know that a long time ago when I ran VirtualBox in Ubuntu there was something I had to do to allow USB access to the VM.
Here are the current instructions directly from Ubuntu:
https://help.ubuntu.com/community/VirtualBox/USB
Good luck.
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
sentientsystem said:
hey, i've got 1 more quick question: is there a way to simply load a pre-rooted ROM onto it, like i did with my samsung? where you put it onto the device, the go into recovery mode and choose the pre-rooted ROM? i haven't seen any mention of that, so i'm not sure if that's an option...
also, how the hell do you make this boot into recovery mode? i still haven't been able to get it to do that?
thanks \m/ (>_<) \m/
Click to expand...
Click to collapse
Yes you can flash a pre-rooted image. They are available. Use the search?
I posted instructions on the first page showing how to boot recovery.
that's great news - that's all i really needed - i didn't see them before, at least, not conspicuously, but i'll search around again.
and, i must have some how missed your instructions, i'll look again.
thanks!
kevev said:
I posted instructions on the first page showing how to boot recovery.
Click to expand...
Click to collapse
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @everyone for your help.
sentientsystem said:
those steps assume i have CWM installed, and i don't. i looked at installing CWM, and it doesn't have an official recovery app for the p769, and when i went to look at that thread you linked to, it says you must be rooted already. this is the aggravating part of us ignorant people dealing with people who know many things: it appears to us that you have to do some thing that requires that it is already done before you can do it. it doesn't make any sense - just a bunch of circualar requirements, with no beginning.
so, let me ask this a different way: how do i reboot into recovery mode, on a STOCK LG P769 v10g? the lights do not flash, and i'm assuming that is a CWM feature - but CWM is not installed - this is COMPLETELY STOCK - fresh out of the box. so, what do you press, when turning it on, to make it go into recovery mode, so that you can recover from a pre-rooted rom (which i am still looking for)?
i just want to "recover" to a pre-rooted rom, that's it, so that i can delete bloatware and edit the /etc/hosts file (for web app testing). this thread says you cant do this for LG phones http://forum.xda-developers.com/showthread.php?t=2174767 - i got the same result the last guy got . trying to borrow a windows computer now...
also, does any one know if it is safe to put a jelly bean rom onto a device that was using ice cream sandwich? is there a difference between the versions that would brick the device? is it not recommended, or is it highly recommended?
thanks again. sorry for all the confusion.
you know, as a side note: it may help more noobs understand this stuff if there was a sort of simplified glossary, perhaps as an official site thread, for the orientation of noobs, that would give an outline of the basic concepts, AND their order of operation. exmaple: "rooting is when you... bootloader unlocking is when you... CWM is for people who want to... you MUST do A before you can do B and then you can optionally do C if so desired...". that would help them understand where to START, then, where to GO next.
Click to expand...
Click to collapse
I've decided to help you out This page will give you some more info on the P769 and several kdz (roms) for the P769
The fastest way to root is to flash the V21B kdz (this is the Jelly Bean version for Canada) using this guide, http://forum.xda-developers.com/showthread.php?p=36351786
The reason why you want this rom is because it has a vulnerability that is easy to exploit with Jcase apk
Once your followed everything (and rooted), install Super Su and Busybox
Next install artas182x second init CWM (in case you can't find it on his page, the link is here )
Note: you will see blinking led lights when you see the LG logo (booting up) appear after a couple of seconds. To enter the CWM press the vol (-) when the lights start flashing.
After you installed Artas182x CWM you can recover from someones clockworkmod backup.
following info from Cmahendra's thread
Note: only restore CWM backups from P769 versions or MS769!!!!
Or check out the V10B (MetroPCS "JellyBean") CWM backup
Now the only 2 reasons to unlock the bootloader are:
1. Install a safer and better CWM
The reason why is because Artas182x CWM is a second init (bootstrap), so if you mess around with a busybox apk and something goes wrong or you remove a file that is required (for CWM), it will stop operating. You will have to reflash the kdz or fix what you changed to get it working again.) I've had this problem several times while messing around with different busybox apps and etc.
2. Custom roms
(which you stated you are not looking for) not worth talking about right now.
Answer to questions
The only pre rooted roms are clockworkmod backups, lol
The default recovery is useless to us (unless you feel like solving the problem)
Flashing back and forth (ice to jelly) comes with risk, the program used on Windows to flash is buggy at times. The best way (in my opinion) is to flash only when really required and mostly restore from clockwormod backups. The device is actually hard to hard brick, but it will require at lot more knowledge to get your device running again.
---------- Post added at 07:23 PM ---------- Previous post was at 07:16 PM ----------
sentientsystem said:
well, borrowed a windows computer and i got it rooted, but, i found out a few things about this exact model: it has no "boot to recovery" option, by default - it's locked down pretty good. you can not use any of the other root methods on this model, and you can not do it from linux (f*ck me).
so, that long-winded fake-software-update-while-switched-out-a-hex-edited-binary-file is the ONLY way for this exact model, it seems...
but, at least i can confirm that this exact model CAN be rooted at all
now to remove alllllllll the bloatware... and look into this CWM more and learn more about what is actually IS and WHY so many people install/use/flash it...
hey, does any one know if cyenogenmod ever got themselve's an "app/marketplace"??? that was one of the draw-backs to installing it, last i checked.
thanks @all for your help.
Click to expand...
Click to collapse
So what version are you on right now
Ice? Jelly?
i'm still on ICS for the moment. still trying to understand what i need to do next. re-reading your post for the 2nd time, and all the threads it references. making sure i don't screw any thing up. thinking about upgrading to JB, and trying this CWM. and looking into this "cyanogenmod" some more, to understand why i never see any one on this site mention it, and what all these "other roms" are about. lmao, like i said, i'm way new to this . it's a lot to take in, even for a web developer .
thanks \m/ (>_<) \m/
:cyclops:hi guys, first of all thank you because you have saved me many times in the past just by reading through the forums. but this time
nothing seems to help me, i have a htc one m8 from sprint, and i tried to root it and install a custom room. And i did rooted now my device
shows tempered and bootloader is unlocked. I used twrp for the custom recovery later i tried to install android revolution one 4.0
and did not work but not only that i erase the partition of the phone so i soft bricked and my phone end up stuck on the boot loader not even
twrp will work :crying:and i try to repair the partition by using some comands that i found, but my phone was not getting recognized by adb just fastboot.
After a day i try a different custom recovery philz. and that one worked so i was able to enter to recovery, and i don't know why but when im inside the recovery my phone gets recognize by adb. I try to repair the partition, but since i have to grant access on the phone is not able to finish. so i tried to install
different rooms such as viper, badseed and it goes through the set up, but when it finish it just gets stuck on the boot loader again. I been trying
to install the stock room but i haven't been able to find it, i found a link in many different forums but the links are broken i been dealing with this
issue for over 5 days and don't know what to do. i will really apreciate if someone cuold help me please forgive me if you don't understand me but
english is not my native lenguage, so i don't speak it very well. also i'm a noob on rooting so i may not know a lot by the way my phone is s-on. help will be
really appreciate.
If you are S-On, when flashing a rom, it will not be able to automatically flash the kernel (boot.img) unless it specifically states in the OP it does by the developers. Most of the time, you'll just need to extract the boot.img and place it in the folder you have fastboot, then when connected in bootloader / fastboot mode run this : fastboot flash boot boot.img
after you flash the rom. Just boot into it right after, flash, and the just type : fastboot reboot
Should be good to go. FYI : adb isn't intended to work in bootloader and fastboot doesn't work in recovery. Nothing wrong there.
Sent from over there...
es0tericcha0s said:
If you are S-On, when flashing a rom, it will not be able to automatically flash the kernel (boot.img) unless it specifically states in the OP it does by the developers. Most of the time, you'll just need to extract the boot.img and place it in the folder you have fastboot, then when connected in bootloader / fastboot mode run this : fastboot flash boot boot.img
after you flash the rom. Just boot into it right after, flash, and the just type : fastboot reboot
Should be good to go. FYI : adb isn't intended to work in bootloader and fastboot doesn't work in recovery. Nothing wrong there.
Sent from over there...
Click to expand...
Click to collapse
thank for the help and i did as you said i install viper it finish a soon as it finished the phone reboot and went to bootloader i extract the boot.img from the zip and put it on the fastboot folder flash it and it said okay then i reboot the device and again just got stock on the bootloader im going to try to install android revolution and do the same thing but i almost sure is going to do the same thing. any other advice that you can provide me i will really appreciate it
and thanks again for the help.
update
just and update i did try also with android revolution and still no luck :crying:any help will be really appreciated:cyclops:
Can you post the link to the roms you are trying to load? I'm wondering if you aren't try to flash ones not for the Sprint M8? I don't see the ARHD rom in the forum for your phone...
es0tericcha0s said:
Can you post the link to the roms you are trying to load? I'm wondering if you aren't try to flash ones not for the Sprint M8? I don't see the ARHD rom in the forum for your phone...
Click to expand...
Click to collapse
thanks for the help first of all i have try this ones
ViperOne_6.0.0
Bad_Boyz_Sprint_ONE_KitKat_v1.2
BadSeed_Sixth_Sense_RLS2.1
Sprint_M8_1.12.651.17_system_dump
SENSE_STOCK_ROOTED_VZW_M8
Android_Revolution_HD-One_M8_4.0_ART
this are the ones, thank for the help again and i soon as we go through this im going to give you a donation for the big help
homar_80 said:
thanks for the help first of all i have try this ones
ViperOne_6.0.0
Bad_Boyz_Sprint_ONE_KitKat_v1.2
BadSeed_Sixth_Sense_RLS2.1
Sprint_M8_1.12.651.17_system_dump
SENSE_STOCK_ROOTED_VZW_M8
Android_Revolution_HD-One_M8_4.0_ART
this are the ones, thank for the help again and i soon as we go through this im going to give you a donation for the big help
Click to expand...
Click to collapse
Well, I definitely see a couple issues with that list...
The Viper 6.0.0 should be this one: http://forum.xda-developers.com/showthread.php?t=2334294 Which is for the International M7.
The Bad Boyz rom you posted should be the one from here: http://forum.xda-developers.com/showthread.php?t=2635051 - This is for the M7 version.
The BadSeed rom should be the one posted here: http://forum.xda-developers.com/showthread.php?t=2694471 - Also for the M7 (hence the M8 *PORT* in the title thread.
Now, HTC was stupid for giving the new phone the same name, I'll give you that, and XDA doesn't have it set to really filter well between the 2 forums, BUT stuff like the date posted could have been a give-a-way as well. But honest mistakes for sure. So, how to fix from here since your partitions are probably thoroughly hosed...? Hmm. Since I don't think there is an official Sprint RUU, that will be tricky. You will most likely need to get a hold of a very experienced HTC dev like the one's whose roms you were trying to use. The Viper, Bad Boyz, and BadSeed dev teams are all very good at most everything HTC. Another option is the developer : Captain_Throwback. He is very knowledgeable about HTCs from top to bottom and seems to be pretty helpful. Your casual helper will most likely not be able to provide as detailed help as you would need in this situation.
The forums you want to hang out in for your phone are here: http://forum.xda-developers.com/sprint-htc-one-m8
es0tericcha0s said:
Well, I definitely see a couple issues with that list...
The Viper 6.0.0 should be this one: http://forum.xda-developers.com/showthread.php?t=2334294 Which is for the International M7.
The Bad Boyz rom you posted should be the one from here: http://forum.xda-developers.com/showthread.php?t=2635051 - This is for the M7 version.
The BadSeed rom should be the one posted here: http://forum.xda-developers.com/showthread.php?t=2694471 - Also for the M7 (hence the M8 *PORT* in the title thread.
Now, HTC was stupid for giving the new phone the same name, I'll give you that, and XDA doesn't have it set to really filter well between the 2 forums, BUT stuff like the date posted could have been a give-a-way as well. But honest mistakes for sure. So, how to fix from here since your partitions are probably thoroughly hosed...? Hmm. Since I don't think there is an official Sprint RUU, that will be tricky. You will most likely need to get a hold of a very experienced HTC dev like the one's whose roms you were trying to use. The Viper, Bad Boyz, and BadSeed dev teams are all very good at most everything HTC. Another option is the developer : Captain_Throwback. He is very knowledgeable about HTCs from top to bottom and seems to be pretty helpful. Your casual helper will most likely not be able to provide as detailed help as you would need in this situation.
The forums you want to hang out in for your phone are here: http://forum.xda-developers.com/sprint-htc-one-m8
Click to expand...
Click to collapse
thanks so much for the help im learning a lot like what is a RUU and as you said i try to look for one no luch anyhow i have a doom question how do i get a contact with them how can i get the help from the ones that you mention im sorry but so far i been using xda to read through the forums this is actually my first time posting a problem i will really appreciate the help thank you.
homar_80 said:
thanks so much for the help im learning a lot like what is a RUU and as you said i try to look for one no luch anyhow i have a doom question how do i get a contact with them how can i get the help from the ones that you mention im sorry but so far i been using xda to read through the forums this is actually my first time posting a problem i will really appreciate the help thank you.
Click to expand...
Click to collapse
1 of 2 ways : post on a thread they have up, or click on their name on the left pane of the forum thread and it should give you options to Private Message the member. Keep in mind, many developers are busy people and some of them just ignore their PMs because they get so many for simple questions. Yours is certainly not gonna be the easiest fix. I would suggest to maybe start here: http://forum.xda-developers.com/showthread.php?t=2696652
es0tericcha0s said:
1 of 2 ways : post on a thread they have up, or click on their name on the left pane of the forum thread and it should give you options to Private Message the member. Keep in mind, many developers are busy people and some of them just ignore their PMs because they get so many for simple questions. Yours is certainly not gonna be the easiest fix. I would suggest to maybe start here: http://forum.xda-developers.com/showthread.php?t=2696652
Click to expand...
Click to collapse
thank you so much i'll do that, i really appreciate your help and your time
homar_80 said:
thank you so much i'll do that, i really appreciate your help and your time
Click to expand...
Click to collapse
No problem! Don't let this scare you away from trying to mod your phone later on. Just use this as a learning experience about the importance of reading. Lots.
hay
+D
es0tericcha0s said:
No problem! Don't let this scare you away from trying to mod your phone later on. Just use this as a learning experience about the importance of reading. Lots.
Click to expand...
Click to collapse
thank you for everything and i will keep trying also i have another htc one but the first generations i will mod it as well as soon as im done with this one jejeje
and believe me that i been reading for day trying to find a solution to my problem but hopefully soon with some help can be able to do it and if you want i can post and update in here of how finally i was able to fix it... thanks
First off, this should be posted in the Sprint M8 Q&A forum.
Next, I assume you have a stock nandroid, as that's the first thing everyone should do after getting a custom recovery installed on the device. So start by restoring that. If for some reason you don't have that, I believe there's one floating around in the "Stock ROM or any" thread in Sprint M8 General or Q&A.
Once you can boot up the device, you should be good to proceed to S-OFF and flash only ROMs specified for the Sprint M8 variant.
My pleasure. It's how I like to give back to the community. I have a ridiculous amount of experience with everything root, recovery, rom, mods, themes, apps, etc related after modding 100s of phones and tablets, but these type of issues require the next tier of experience when you're getting into semi uncharted territory due to how new the device is and that HTC hasn't released the official update utility for it. But yea, you should post back, just in case another member runs into the same problem and you can help point them in the right direction.
Captain_Throwback said:
First off, this should be posted in the Sprint M8 Q&A forum.
Next, I assume you have a stock nandroid, as that's the first thing everyone should do after getting a custom recovery installed on the device. So start by restoring that. If for some reason you don't have that, I believe there's one floating around in the "Stock ROM or any" thread in Sprint M8 General or Q&A.
Once you can boot up the device, you should be good to proceed to S-OFF and flash only ROMs specified for the Sprint M8 variant.
Click to expand...
Click to collapse
thanks for the quick help and yes i did create a back up of the phone but when i was trying to install the first custom room Android_Revolution_HD-One_M8_4.0_ART it ask me if i want to delete all data and i said yes. So my partitions of the phone i believe are screw up. I did look for Stock room i found many that were linking to the same file both the oex and deodex links were bronken and i haven't been able to find the one that i need that is kitkat 4.4.2 sprint. and i don't know what's next from were i am now.
homar_80 said:
thanks for the quick help and yes i did create a back up of the phone but when i was trying to install the first custom room Android_Revolution_HD-One_M8_4.0_ART it ask me if i want to delete all data and i said yes. So my partitions of the phone i believe are screw up. I did look for Stock room i found many that were linking to the same file both the oex and deodex links were bronken and i haven't been able to find the one that i need that is kitkat 4.4.2 sprint. and i don't know what's next from were i am now.
Click to expand...
Click to collapse
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
EDIT: http://forum.xda-developers.com/showthread.php?p=51624633
Captain_Throwback said:
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
Click to expand...
Click to collapse
He flashed 3 or 4 different roms that were for the M7 or not for his version of the M8. Pretty sure that the partitions are borked at this stage as properly flashing the correct M8 rom and fastboot flashing the boot.img has not gotten him out of trouble.
es0tericcha0s said:
He flashed 3 or 4 different roms that were for the M7 or not for his version of the M8. Pretty sure that the partitions are borked at this stage as properly flashing the correct M8 rom and fastboot flashing the boot.img has not gotten him out of trouble.
Click to expand...
Click to collapse
thanks i was looking for the words to explain that my English is really bad i apologize for that.
homar_80 said:
thanks i was looking for the words to explain that my English is really bad i apologize for that.
Click to expand...
Click to collapse
Did you see my post?
---------- Post added at 05:15 PM ---------- Previous post was at 05:11 PM ----------
Captain_Throwback said:
I'm not sure I understand. What does deleting all data have to do with your backup? Are you saying your backup got deleted? In that case, do what I said and find the one I referred to and restore that.
EDIT: http://forum.xda-developers.com/showthread.php?p=51624633
Click to expand...
Click to collapse
If restoring the above doesn't work, you can try this:
- Relock bootloader (fastboot oem lock)
- Download signed firmware zip from here. Flash via fastboot (fastboot oem rebootRUU, fastboot flash zip firmware.zip, fastboot reboot-bootloader)
- Unlock bootloader via HTCDev.
- Download TWRP Recovery from here and fastboot flash (fastboot flash recovery openrecovery-twrp-2.7.0.2-m8_whl.img)
- Download Stock Rooted ROM from here and flash via TWRP.
Don't forget to hit the thanks button.
http://superstarmobility.weebly.com/
New thread: http://forum.xda-developers.com/android/development/twrp-m1-lg-k7-t3462130.
(Above TWRP can be flashed with Flashify from Playstore)
Instructions from video:
With phone powered off, hold POWER and VOLUME DOWN buttons until LG logo shows. Release POWER then quickly press and hold again until factory reset menu comes up. Select YES and you will be booted into recovery instead of a factory reset ; )
Thanks @czarsuperstar!
V2 with the proper cmd line from m1 aka LG K7
Reserved.
This the real deal?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
Of course. You looked at the video?
goitalone said:
This the real deal?
Click to expand...
Click to collapse
I've used it and can confirm, first tested it with fastboot without flashing of course(use adb to get to the bootloader: adb reboot bootloader , then fastboot:fastboot boot "twrp.img file, tested then rebooted into bootloader, then flashed via fastboot:fastboot flash "twrp.img file") instructions are for any random person that come by i know you know how to do all this
concerned xda citizen
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
The first twrp was from a htc phone. This is from lg leon lte. Same manufacturer. I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon twrp is missing the options seen on this one. Don't use it. But I'm working on cm_m1 so continue to use the old one and when your phone can't come on have fun getting in recovery. Make it better.
Recovery log
Make a log.
NASSTYROME said:
what are the boardconfig.mk file contents that you used to compile this recovery?
the fact youre using a ghetto hacked twrp that works is fine, but id prefer an actual device specific twrp version that will reliably work - theres no telling what this twrp can do to your device, and the fact youre using another devices ramdisk scares the hell out of me.
ramdisks arent something you play around with - you can seriously ruin someones device like that.
also requesting the twrp fstab file youve used.
youre literally just throwing files at users that have perviously bricked their devices and not explaining in detail what they consist of.
if you seriously damage any of these user's device partitions by overwriting the wrong partition, are you going to pay for the devices when theyre hardbricked and no longer responsive to the oem flashing?
not once have a even seen a warning on these files yet youre just posting forum to forum; not to mention youre inexperienced at rom/kernel/recovery compiling for the fact you think its okay to just throw a different devices ramdisk in there " because it just works." when we have readily available source for our device.
legally- youre held responsible for these files youre distributing.
and to those just flashing this twrp file to their device, yes its reversible - but would you want to find out it doesnt work when its too late? IE backing up partitions in the wrong order, and restoring them into the wrong partitions? the video shows it backs up and restores, but is it doing so in the right order? in the right places. i may be ranting but id rather be careful/safe then sorry.
not one detail of this compile/build has been released, just a link that is claimed to work.
"left sock fits on right, doesnt feel right - but my feet aren't cold!" is how this feels to me.
i was sketched to even test this twrp version considering you need to tell the factory reset "yes, i want to wipe" twice, in order to boot to twrp.
idk about you but ive never seen any recovery warrant those options. normally twrp would just boot upon button combo - which is why im sharing this post. recoveries arent supposed to be functioning that way.
Click to expand...
Click to collapse
Check out the LG L70 it's the same way to get in recovery. This must be your first LG phone.
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Go spam the other thread. Over 200 downloads and no problems but there was problems right away with the first version. For your info download Twrp c50 from the Twrp site examine it and ask why it's incomplete. That's why I linked the video of the Twrp from the site and same problems. Bye and leave me be. Hd2 check it out. Czarsuperstar's HTC HD2 android custom roms. Check it out and leave me alone. Thanks for your concern. Oh and for your info we have the same keyboard configuration as the LG Leon. There's a device tree. Google it. Google is your friend bro.
NASSTYROME said:
i dont care whether its the same way to enter recovery, my care is youre using another phone's ramdisk in this device.
"I used my boot.img dumped on my sdcard and used the ramdisk from Twrp Leon aka c50 the leon"
post twrp.fstab and boardconfig.mk youve used for this "twrp" build.
this must be your first posting for development on an unsupported device.
as for anyone using another device's files when we have access to source of our own device - i wouldnt trust them to build anything, let alone CM. thats just pure shortcutting and laziness .. and at what expense?
as for twrp making this official, they wont - as you cannot provide SOURCE.
So, now, hopefully you've compiled TWRP for your device and gotten it working. Now, you'd like to know how to get TWRP officially supported for your device so that it can be installed automatically with GooManager. In order for us to add "official support" for your device we'll need the following:
1) Device configuration files to compile TWRP from source for your device. This means that you cannot have repacked a recovery.img by hand to get it working. We need to be able to compile it from source so that we can easily release future updates.
2) A copy of a build prop for your device (it's in /system/build.prop) so that we can add the correct device information to GooManager
3) We'll build a copy of TWRP and send it to you for validation. Once you've validated that we can build a working image for your device, we'll add it to GooManager.
Click to expand...
Click to collapse
not saying a official twrp isn't preferable, but man you got to learn how to talk to people, you were just short of cursing the dude out, and as far as the recovery the thing is solid(tested backup, flash and restore/ anyhow we got LGUP if you **** up so its not a huge deal), but anyone on this site shouldn't take someones word for things like recovery's and you should always test boot before you flash, also you don't seem to understand the first rule of xda-whatever happens to your device is on you, been that way since the og day's- talking politely to others is the way to go about things, people wont listen if you combative.
Kernel
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Didn't work, after selecting yes twice, my phone just starts like normal, doesn't go to TWRP or factory restore, it is there though because I can boot to it from the flashify app, ah well.
wait...my bad, I was highlighting the wrong one, lol, works great, thanks
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
callihn said:
Assuming it ever worked right it should work better now because you can always get to it.
As for concerns about the ramdisk I don't see any issues with that, it's just being used to boot and run recovery on if I'm not mistaken and apparently where the buttons get enabled so a necessity.
Considering many phones have such hacked together recoverys and many more have no custom recovery I'm thankful to have it particularly since most of my work is done away from my pc.
Click to expand...
Click to collapse
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
[email protected] said:
Thanks for report. The other Twrp w/o the button combo was from a HTC phone lol and I am getting blasted. HTC or LG? LG K7. ... LG.
Click to expand...
Click to collapse
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
callihn said:
Right and that's why the buttons didn't work. Great job! Best discovery yet for this phone, so happy that we can restore now withoit adb and withoit having to worry about debugging getting turn off, very essential find. Don't let those that don't understand get you down.
Click to expand...
Click to collapse
I'm working on building it from source but keep getting errors and I'm trying it with another device that has Twrp (Moto E 2015) and followed the directions to the T and no luck. So I am trying......... Will let everyone know how it's going.
[email protected] said:
Im building the kernel from source right now check out the video on Twitter. Anyone that wants to join the development I am down with it.
Click to expand...
Click to collapse
kernel??????????????????????????
im down!