Related
Dear People,
I am a noob. A really big noob but I really want to have all the cool things that you guys have on the HTC Legend with 16GB SD. In my opinion is the HTC Legend sometimes a bit slow.
I am running: Android 2.2 and everything is stock, I never changed a thing. I saw some cool stuff on Youtube and I read a lot of interesting information about 'Custom Roms'.
My question / problem:
I want a fast cool Legend Rom which one the GPS, WIFI and Camera all the otherthings are working with no problems. Which Custom Rom is the best ROM for me?
I hope to read answers. I am very sorry for my dumb question and my bad English.
Regards,
Eer
Dear Noobfromthelegends,
first of all, if you want to try out custom roms, you need to root your Legend.
The easiest and safest way to do so is to follow the HTC guide [1] (please note that your warranty will be affected even if it is an "official" process).
Steps to follow had been explained in many threads, please take time to read a couple of solved similar threads; it'll spare you some time.
As you must have seen, there are a lot of ROMs out there, though a lot of them shared common basis. I'm afraid I can't help you on the best and faster one, I have only tested stock ROM and CyanogenMod (CM) ones. CM 7.1 (the latest stable release AFAIK, based on Android 2.3.7) is great but my Legend is sometimes laggy (actually a bit too often compared to newer phones).
Some people are trying hard to port Android 4 (Ice Cream Sandwich, ICS) on our beloved Legend. One major feature of ICS is the hardware-acceleration, which means that not only the CPU is used to compute (effects and some stuff) but available DSPs too. These ROMs are currently in beta stages, but users seems to be really happy with them (major drawback is not fully working camera ATM and some minor bugs, but like I said it is beta software).
(I am of course thinking of zeubea and its CM9 adaptation [2])
PS: remember to make nandroid backups (that is, make a backup of the whole system in case you did something wrong) and keep them safe, at least one which is okay (ie. a working copy on your computer). You can go back in time with complete backups, quiet useful if you want to try some MODs.
1: http://www.htcdev.com/bootloader/
2: http://forum.xda-developers.com/showthread.php?t=1562595
edit: it seems that updating your hboot version (ie. following the HTC guide to root your phone by updating your hboot) may be problematic if you want S-OFF. Please look for it on the forum if you care about it.
Thank you very much for your reply.
If I want S-Off has that something to do with: 'Root your Legend'?
Thank you for your back-up tip. But how do I back up my Legend? Because I am afraid that I don't back-up correct.
Hope to hear from you or the other forum members soon.
PS: Tomorrow I am going to 'Root' my Legend and I let it you hear.
NoobfromtheLegends said:
Thank you very much for your reply.
If I want S-Off has that something to do with: 'Root your Legend'?
Thank you for your back-up tip. But how do I back up my Legend? Because I am afraid that I don't back-up correct.
Hope to hear from you or the other forum members soon.
PS: Tomorrow I am going to 'Root' my Legend and I let it you hear.
Click to expand...
Click to collapse
- You're welcome, that's the purpose of this forum
- it seems that S-Off give you full access to your NAND flash.
I don't know a lot of things about it, only read some posts. So far, I didn't feel the need to do it, I can use custom ROMs, custom splash screens, etc.
I repeat, I don't know **** about this. Just that I didn't need it for the past two years with my Legend (rooted for more than 18 months).
I read that it has something to do with your hboot, and as I told you to follow the HTC guide to root your legend, yes it has something to do with it because it seems that you can't S-Off easily with a hboot version > 1.00.
- you can backup your device when you are in recovery
Please read guides about rooting your Legend, you will learn about the ClockWorkMod, the recovery, fastboot and last but not least ROM Manager.
If you are not comfortable with all these terms, you may end up not understanding at all what you are doing or done and being stuck with a (semi-)bricked phone is probably not what you want. Just don't rush for it.
If you want to update your hboot to root your Legend, have a look at BlaY0's post [1] too.
Feel free to read other member's questions and problems, they certainly have been solved. Reading others' mistakes could make you avoid them.
PS: if you want to thank me, press the "Thanks" button below my post
1: http://forum.xda-developers.com/showpost.php?p=22613990&postcount=62
edit: didn't see that you used the button already
@bibzor great stuff!
My 2c, Rom to try? OK just thinking here, maybe as a beginner to custom roms start with blay0s froyo, it will be more familiar to you coming from stock froyo, but its also got all the bells n whistles that make rooting worth it ie. ext partition support for more app space, over/under clock and more I've forgotten about just now.
Go here.
http://forum.xda-developers.com/showthread.php?t=866849
Or if that's too boring for you and want excitement just start with zeubeas ics , that'll get your juices flowing, just remember its still a w.i.p. so theres still a few bugs and not everything is working 100% yet, but is still good enough for me to use as a "daily".
The other option I like personally is ogo2's gingerbread
http://forum.xda-developers.com/showthread.php?t=987251
Then there's the cyanogenmod & its variants like legendary legends fuse.
Their all good! :thumbup:
Its a good idea to try and read the whole thread of the custom rom you want to flash for hints tips and other stuff before flashing too.
Welcome to a new world of flashing
sent from my legend, currently using zeubea ics beta0
Thank you both very much for your reactions.
I Googled a lot of Nanobackup but I first want to root my systeem. I saw on the HTC DEV site the Unlock Bootloader but first I have to update the Rom / Ruu but there isnt a Dutch Carrier. I come from the Netherlands.
What do I have to do?
NoobfromtheLegends said:
Thank you both very much for your reactions.
I Googled a lot of Nanobackup but I first want to root my systeem. I saw on the HTC DEV site the Unlock Bootloader but first I have to update the Rom / Ruu but there isnt a Dutch Carrier. I come from the Netherlands.
What do I have to do?
Click to expand...
Click to collapse
Read BlaY0's post about rooting, I posted the link earlier. You don't need to update your ROM to follow the HTC dev guide.
NoobfromtheLegends said:
Dear People,
My question / problem:
I want a fast cool Legend Rom which one the GPS, WIFI and Camera all the otherthings are working with no problems. Which Custom Rom is the best ROM for me?
Regards,
Eer
Click to expand...
Click to collapse
For couple of days i tryed some ROMs :
Cyanogenmod 7.1 -faster and stable, the phone was running perfectly, except the weak WIFI connection (maybe the problem was in my router) .
ExtremeLegendFuse 2 (best choice for me)- the phone just was flying - much more faster than the Stock ROM , GPS and WIFI worked perfect.
Now i use Cuanogenmod 7.2 - and will stay with it for future, Like advantages I can notice - lower baterry consumation and a little bit more free available RAM, in comparison with, CM7.1 / ExtremeLegendFuse 2 , on CM7.2 i neved used GPS and have not impression about the GPS ( befor i tryed to drive with GPS and after that i hate it ), everything else works perfct, the ROM is much more faster than the stock 2.2 Froyo ,but this ROM feels a little bit slower in comparison with ExtremeLegendFuse 2 ;
If you want a "fast and cool ROM " I recommend ExtremeLegendFuse 2;
If you use your phone for work and your phone is always in your hands - use Cuanogenmod 7.2
bibzor said:
Read BlaY0's post about rooting, I posted the link earlier. You don't need to update your ROM to follow the HTC dev guide.
Click to expand...
Click to collapse
Thank you Bibzor but ....sorry for so much questions.
Today I wipeout everything on my phone due:
- Turn phone off, volume down 1 x On / Off Button and then Clear Storage.
- Then I did a format of my 16GB Micro SD.
So everything is clean now and I really want to do a full back up of my original Dutch ROM. If I understand it right I have to do a NANDROID for a complete back up of my orignal Dutch ROM so I can always go back to the orignal software?
BlaYo post about rooting starts with:
'' 1. Do a nandroid (at least data partition). ''
But how do I do a NANDROID with a Legend that isn't rooted? Can I start with point 2 from BlaYo post about rooting?
NoobfromtheLegends said:
Thank you Bibzor but ....sorry for so much questions.
Today I wipeout everything on my phone due:
- Turn phone off, volume down 1 x On / Off Button and then Clear Storage.
- Then I did a format of my 16GB Micro SD.
So everything is clean now and I really want to do a full back up of my original Dutch ROM. If I understand it right I have to do a NANDROID for a complete back up of my orignal Dutch ROM so I can always go back to the orignal software?
BlaYo post about rooting starts with:
'' 1. Do a nandroid (at least data partition). ''
But how do I do a NANDROID with a Legend that isn't rooted? Can I start with point 2 from BlaYo post about rooting?
Click to expand...
Click to collapse
Use titanium backup from Google play.
Sent from my Legend using xda premium
Here Am I again. Sorry for my questions I hope that I get one more reaction.
I have have successfully unlocked my bootloader with the HTC DEV method.
But I still don't have ROOT acces. I have installed ROM Manager to do a full back-up of my ROM but it says: 'You don't have ROOT acces'.
I tought that when I unlock the bootloader with the HTC DEV method that I have ROOT acces on my HTC Legend.
What am I doing wrong?
Please help!
NoobfromtheLegends said:
Here Am I again. Sorry for my questions I hope that I get one more reaction.
I have have successfully unlocked my bootloader with the HTC DEV method.
But I still don't have ROOT acces. I have installed ROM Manager to do a full back-up of my ROM but it says: 'You don't have ROOT acces'.
I tought that when I unlock the bootloader with the HTC DEV method that I have ROOT acces on my HTC Legend.
What am I doing wrong?
Please help!
Click to expand...
Click to collapse
After unlocking boot loader, use HTC supertools (which can be downloaded in this forum or just Google it) and it should be rooted.
Sent from my Legend using xda premium
Download supertools from link below
do it with htc supertool:
http://forum.xda-developers.com/showthread.php?t=1431398
it worked for me after i unlocked my legend via htc dev
Sent from my Legend using xda premium
YEAH BIG THANKS! YEEEEAAAAAH! HTCSupertools were very easy! Thank you soooooooooooo much! Really, really, really thanks!
But..I want to back up my original Dutch 2.2 ROM. When I touch in Rom Manager:
Back up ROM, my Legend restarts and I get a phone with a red triangle.
When I push: Volume UP and then the On/Off button I get:
E: Can't open /cache/recovery/command.
I tried everything: Formatting SD card and much more.
Why is a backing up of my original ROM so difficult?
P.s. I also installed: Clockwork Recovery.
Similar Problem.
Hi Folks,
The above is similar to my problem.... I am an absolute total NOOB!! Rooted my legend thanks to these forums just yesterday and have SuperUser, ROM Manager & ROM Toolbox installed and can see the root and access files so most things seem to work..... BUT.....
Every time I try to update the ROM or partition the SD card I get the dreaded red triangle/exclamation mark and have to remove the battery to allow the phone to reboot into the dreaded Vodafone ROM.
My startup shows "UNLOCKED" S-on but according to other threads here that is not a problem as unlocked automatically means S-off.
Any ideas or threads to read would be much appreciated thank you as I want to try Gingerbread before I risk ICS
Thank you
Hi guys,
if you're experiencing the red triangle horror, don't be afraid it's quite common.
This triangle shows up when you try to reboot in recovery mod but the recovery image couldn't be loaded.
The easiest way is to use ROM Manager to update your recovery to the latest available and then press "reboot in recovery".
Otherwise, you can try to flash recovery image by hand.
Download the latest recovery image [1] and follow the method listed there which is :
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
EDIT: of course these two commands are to be executed in a shell command when your Legend is connected to your computer and the image file is in the current directory, otherwise put its path.
1: from http://forum.xda-developers.com/showthread.php?t=1290841
bibzor said:
Hi guys,
if you're experiencing the red triangle horror, don't be afraid it's quite common.
This triangle shows up when you try to reboot in recovery mod but the recovery image couldn't be loaded.
The easiest way is to use ROM Manager to update your recovery to the latest available and then press "reboot in recovery".
Otherwise, you can try to flash recovery image by hand.
Download the latest recovery image [1] and follow the method listed there which is :
Code:
adb reboot bootloader
fastboot flash recovery recovery-clockwork-5.0.2.0-legend.img
EDIT: of course these two commands are to be executed in a shell command when your Legend is connected to your computer and the image file is in the current directory, otherwise put its path.
1: from http://forum.xda-developers.com/showthread.php?t=1290841
Click to expand...
Click to collapse
I LOVE YOU! I did it and I did a flash image recovery by hand. Now I am going to back up my ROM!
Rexjarvis, if you don't know what to do with the command you have to do:
when the device is switched off, hold the volume down & power button in order for the phone to boot into the bootloader & connect the phone to the pc. You see now: ''Fastboot usb''.
Download the recovery_legend_5.0.2.8.img file and put it in the same folder on your pc as fastboot.exe & adb. then open the commandline on the pc, navigate to the folder that contains the fastboot.exe. You know: CMD and then C:\Android for example. Then you have to do the two commands from Bibzor:
Code:
adb reboot bootloader
fastboot flash recovery recovery_legend_5.0.2.8.img
NoobfromtheLegends said:
I LOVE YOU!
[...]
Then you have to do the two commands from Bibzor:
Click to expand...
Click to collapse
well ..
By the way, I just copied the commands from the thread I linked
NoobfromtheLegends said:
YEAH BIG THANKS! YEEEEAAAAAH! HTCSupertools were very easy! Thank you soooooooooooo much! Really, really, really thanks!
But..I want to back up my original Dutch 2.2 ROM. When I touch in Rom Manager:
Back up ROM, my Legend restarts and I get a phone with a red triangle.
When I push: Volume UP and then the On/Off button I get:
E: Can't open /cache/recovery/command.
I tried everything: Formatting SD card and much more.
Why is a backing up of my original ROM so difficult?
P.s. I also installed: Clockwork Recovery.
Click to expand...
Click to collapse
No problems mate, glad to help
Sent from my Legend using xda premium
I have been trying to flash with ROM Manager but have permanent verification errors. Now I will try via adb as above. THANK YOU - Wish me luck
No joy... All I get is the same error E:Can't open.......... etc followed by E:Singanture verification error....
Can I not force an S-Off?
I went through the S-OFF, etc process from scratch last weekend (soup to nuts from stock GB), and decided to share my notes.
There is no original information posted here, just a re-organized walkthrough to reference & accommodate what's already out there.
Hopefully a few find it helpful (I know I woulda )
Disclaimer:
this is a Windows-centric walkthrough, that assumes (in parts) that this isn't your first day at the rodeo. Never be scared to use Google or the IRC chat (sorry dsb9938 for the newb flood :laugh
This walkthrough is just an end to a means. You'll find people mention different ways they've accomplish the full process - this post is just a historical document on how I accomplished the same goal.
My methods were definitely successful, though my technique was admittedly ghetto at times. If any uber-pro's notice areas where this is the case, feel free to chime in & i'll update that chunk with credit to you.
I take no responsibility for anything you were inspired to do as a result of reading this post... unless it made you happy, I will take credit for that
The full process in a chronological nutshell:
HTC Unlock
Flash recovery
Root
Juopunutbear S-OFF
Flash latest firmware
Re-flash recovery
Flash ROM
Things to do beforehand:
disable fast boot // settings > power > uncheck
-- this is a universal truth throughout this process, if you have problems booting into the bootloader, check into this.
enable USB debugging - settings > applications > development > check USB debugging
-- this is another universal truth, if something isn't able to communicate with your device, check into this
verify your bootloader / system status
-- power down
-- hold down power & vol- at the same time while booting up
-- it should say Locked & S-ON at the top
backup SD card
backup anything on the internal storage that you care about
*Optional - wipe SD card
*Optional - install an MD5 checker (if you don't already have one)
-- Windows: http://download.cnet.com/MD5-Checker/3000-2092_4-10410639.html?tag=mncol;1
-- Android (for later): https://play.google.com/store/apps/details?id=com.fab.md5
BE PATIENT. seriously. I know you want to get back to MW3, but this can take a while. Your device will go through several lengthy processes. If something looks unresponsive and it starts to scare you, just wait it out for a few minutes before going willy nilly with the power button. At times, you will end up having to manually power on again, but give it time before getting antsy. If your ADD is driving you crazy, just bite your lip and power through it.
Steps 1, 2, & 3)
Unlock, Recovery, & Root:
go to htc dev
sign up / confirm from email / log in
install the stuff they tell you to, listed on the right of the page
Install / use the Rezound All-In-One Toolkit on your PC to accomplish the rest
for recovery, I chose Amon RA
The more you know ✩....
-- a dude doing recovery the manual way - http://youtu.be/AvSeLmXSjVI
-- the recovery is accessed through the bootloader menu
Step 4)
S-OFF:
Charge battery full
Make sure fast boot is still off
Make sure USB debugging is enabled
Download the latest juopunutbear for rezound here (Windows, Latest ICS)
*Optional - Verify the MD5
Follow juopunutbear instructions - here, then here
*Optional - Do a backup via recovery
The more you know ✩....
-- controlbear was randomly having a hard time seeing my device, I solved this by:
---- closing controlbear command prompt
---- toggling on HTC Sync as the USB connection type (on the rezound)
---- this caused the device to be recognized differently in windows & installed a driver
---- I started controlbear again, but it hung at "Searching for device"
---- I closed it & ran it again
---- then it worked
-- for the rooting part of this, when it boots you into recovery, check both SD card locations for SuperSU.zip
-- this process froze on me many times, closing and restarting controlbear seemed to fix it
---- seriously did this at least 10 times - it happened randomly at seemingly scary places. (each time getting me further than the last)
-- juopunutbear hboot? - I said yes
-- SD card issues? do a factory reset.
-- Still have SD card issues? you just need to update the firmware, move along.
-- USB debugging path has changed in ICS, you can enable it here: settings > developer options > check USB debugging
-- ATTENTION: Not getting any reception/ signal? put the case back on, broseph
more info:
-- S-off is Official!!! With Instructions...
-- S-OFF FAQ
Step 5)
Latest firmware:
Download the latest RUU (3.14.605.10 as of July 16) to update the firmware to ICS - http://bit.ly/KlRfKZ
-- *Optional - Verify MD5
Rename the RUU to "PH98IMG.zip"
Copy the renamed update to the root of your external SD Card.
Power down / reboot into bootloader / wait 5-10 minutes for it to finish
Step 6)
Fastboot flash recovery:
After s-off and firmware update, you need to re-flash recovery via fastboot, this process is described here -- # < anybody have a link? #
-- *Optional - Do a backup via recovery
The more you know ✩....
-- flashing recovery via fastboot is only necessary if you want to keep the top of the bootloader reading as "Locked" (even though it's already S-OFF'd).
-- I did not want this, (mine reads "Unlocked") so if you don't want that, then just re-unlock using the same method as you did the first time, and then re-flash recovery the same way again.
REPEAT: Not getting a reception/ signal? put the case back on.
Step 7)
ROM
Download ROM of your choice (I used Nils' Business ICS, Sense 4.0, v1.2)
-- *Optional - Verify MD5
Copy the zip to the root of your external SD Card.
Follow the ROM installation instructions (Wipe, etc) & install via recovery
-- *Optional - Do a backup via recovery
Hooray!
-- credit where it's due & thanks to all who came before me.
i came here because the title said BOWELS! 0.o
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Wrote up a similar guide last week at TeamBAMF's site:
http://www.teambamf.net/topic/4122-generic-guide-to-root-and-install-roms-on-the-rezound/
AshtonTS said:
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Click to expand...
Click to collapse
ha, might have been the reason controlbear failed so many times (still ended up working though).
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
dustintheweb said:
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
Click to expand...
Click to collapse
Yeah makes sense.
dustintheweb said:
ha, might have been the reason controlbear failed so many times (still ended up working though).
As far as ADB, I hear ya, I just felt that most folk have little or no idea what they are doing and just want to get to the next step - so I tried to keep it simple where I could.
Click to expand...
Click to collapse
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Divine_Madcat said:
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Click to expand...
Click to collapse
Just to add on to that, a noob who can't use adb and fastboot fully probably has no need for s-off
So no fast boot Ehhh?
I just checked, mine is on, so is that why my 8 hours of s-off attempts failed?
Sent from my ADR6425LVW using Tapatalk 2
Divine_Madcat said:
Anyone doing s-off (the one operation that CAN brick our phones), should know EXACTLY what they are doing. If you are doing this, there is no reason not to have complete knowledge of the process..
Click to expand...
Click to collapse
meh, maybe i've just had good luck, but I've personally found over the years (and reiterated from others) that HTC phones are fairly hard to brick. I mean, yeah, people should read up on stuff and not be idiots when going down this road, but there's no reason to treat it as delicate of a process as some do.
I like to think of it more as training a dog, rather than walking on egg shells. Take your time, be patient, but don't forget to make it fun.
-- and if at any point you're unsure on how to do something, don't panic - just post your question in the forums or in the chat and be prepared to wait. Someone will help you eventually.
AshtonTS said:
^lol. Just one thing... You did the s-off from GB before you updated the firmware.... So you should have chosen the GB ControlBear. Also I would recommend that you not tell them to use a toolkit. Personally I think you should always fully set up adb and fastboot. That makes it easier if you have problems later. But that's just me
This is a great guide tho. Very informative
Click to expand...
Click to collapse
First, this is exactly what I was looking for so thank you. I've read just about every post for unlocking and s-off, but I'm glad you put it all together!
Second, so step #5 should really be #4?
Third, flame me if you want, but I don't have the developer tools menu to enable USB debugging. Does that show after using unlocking via HTC dev?
Thanks again!
dustintheweb said:
meh, maybe i've just had good luck, but I've personally found over the years (and reiterated from others) that HTC phones are fairly hard to brick. I mean, yeah, people should read up on stuff and not be idiots when going down this road, but there's no reason to treat it as delicate of a process as some do.
I like to think of it more as training a dog, rather than walking on egg shells. Take your time, be patient, but don't forget to make it fun.
-- and if at any point you're unsure on how to do something, don't panic - just post your question in the forums or in the chat and be prepared to wait. Someone will help you eventually.
Click to expand...
Click to collapse
This is how it should be but not all people think like that most just wanna put people on blast
Sent from my ADR6400L using xda app-developers app
BSquaredB2 said:
Second, so step #5 should really be #4?
Click to expand...
Click to collapse
It worked for me, but AshtonTS says there is a better way. Search through the S-OFF FAQ thread (or similar) and see if you can get a consensus of what other people did.
BSquaredB2 said:
Third, flame me if you want, but I don't have the developer tools menu to enable USB debugging. Does that show after using unlocking via HTC dev?
Click to expand...
Click to collapse
If you're on GB, go to settings > applications > development > check USB debugging
Sorry about that, I had the ICS path in the guide (now fixed).
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/
I have a stock rom evo 4g LTE, rooted, with Android 4.0.3 on it.
I forget the root app I used, some one click thingy, I guess my bootloader is unlocked
because I get a boot menu every time I reboot, on that screen that says **TAMPERED**.
Anyway, I ignored the notification icon in my taskbar for OTA updates, for a very long time.
Since the day I bought it over a year ago.
Finally I decided "eh, screw it, why not." ...I'm sure I'll regret that.
I told it to do the OTA update, and it downloaded (I think??) and rebooted.
The icon went away. Seemed to be a done deal.
But once per day since then, my phone rings, and I see a prompt saying
there's an OTA update, and would I like to install it now?
I think it's the same OTA update being prompted repeatdly,
because the filesize is always the same (~42 megs).
What should I do? I can choose install, reboot, and be fine for the rest of the day,
or choose cancel, reboot, and be fine for the rest of the day.
Doesn't seem to matter. But would be nice to fix it for good.
Well, considering that you are about 4-5 OTAs behind the rest of the community, I would say that the notification is probably correct. HOWEVER, of you are not using the stock recovery, then the OTA did not flash. Yes, the phone rebooted, but that's because it is installed entirely through recovery, and the phone has to reboot to get into recovery mode in the first place.
Now, for the more important question at hand....why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted? As far as I'm concerned, the OTAs are actually necessary updates for the phone. I'm sure that you will love Jelly Bean if you have never used it before.
And please, for the sake of us all who are cringing at the sight of the first sentence....PLEASE UPDATE your phone! If you have a good reason not to, please share.
Hi, thanks for the reply... Maybe they were all different updates after all.
I haven't been prompted to update again since my post.
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
HOWEVER, of you are not using the stock recovery, then the OTA did not flash.
Yes, the phone rebooted, but that's because it is installed entirely through recovery,
and the phone has to reboot to get into recovery mode in the first place.
Click to expand...
Click to collapse
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
why exactly are you still using ICS? Furthermore, if you are still using ICS, then why are you rooted?
Click to expand...
Click to collapse
Well, I had no compelling reason to upgrade. I still don't really, the phone does what I want,
I just saw some of the features in the next version and thought "huh, that sounds pretty cool".
I'm rooted for all the usual reasons... I want to be able to browse, copy, move, rename files (including system files)
without incident... use nandroid for backups... wifi tether (still can't get that to work actually)... install unapproved apps...
tweak the OS, and so on.
Ok, my friend...let me educate you. Instead of giving you the simplest, fastest solution, I will actually try to answer all of your questions, since you did ask.
I do think I'd like Jelly Bean too, seeing some of the features is what prompted me to finally catch up.
Can you explain this part to me? I'm not familiar with this stuff.
Click to expand...
Click to collapse
To give a very superficial explanation of Jelly Bean, it is everything that ICS does, and more. It just does it smoother. It also brings Google Now, which was – and still is – the selling point of Jelly Bean. The Sense launcher got a few changes, too, but you will have to explore those changes on your own (mainly because I don’t remember them off hand, and this post is beginning to become lengthy).
Maybe I grabbed the 3 or 4 OTA updates that I needed to catch up on.
If I no longer see the notification, does that mean the updates worked? My Android version still shows 4.0.3.
Click to expand...
Click to collapse
If the first update didn’t update properly, then the phone is simply downloading and trying to install the same update over and over. When you boot back into Android after a successful update, you will be greeted by a welcome message congratulating you for installing the new version.
If you are rooted, odds are, you are using a custom recovery, such as TWRP or CWM. OTAs are only installed through the stock recovery & a locked bootloader. The stock recovery doesn’t make nandroids, or do anything of the sort. To install the stock recovery, go here:
http://downloadandroidrom.com/file/HTCEvo4GLTE/rooting/Evo4GLTERoot2.zip
Click to expand...
Click to collapse
The stock recovery is located somewhere within the zip file.
So, there's more than one recovery mode, the stock one, and ...whatever else you can install?
When I see the white screen that says **TAMPERED** (looks basically like this screen)...
should I have chosen Recovery instead of the usual reboot option?
Click to expand...
Click to collapse
You can flash install the stock recovery by using fastboot commands from the bootloader (which is the screen that shows the TAMPERED status on the top), or you can use Flash Image GUI. It is a paid app on the Play Store, or you can get it from XDA (the dev let XDA users download it for free…Google it).
Lastly, there are a few things that I suggest that you do. First, obtain S-Off (Google, Google, Google...very simple), so you can install the new firmwares directly, instead of using OTAs. Otherwise, if you accept the OTA, you will lose root, and you will have to root your phone again and again. Installing the firmware, then the new rom is the same as accepting the OTA, then rooting.
Another alternative is to get S-Off, then accept the OTA (after installing the stock recovery). Your bootloader does not need to be locked, and there are recovery zips floating around here that can be installed through the bootloader (therefore, you will not be stuck rooting the phone the hard way, just boot into recovery and flash SuperSU). I highly suggest achieving S-Off.
If you want to jump straight to the latest version (Android 4.3, Sense 5.0) by installing the RUU located somewhere in this forum. I actually suggest that you try Sense 4 with Jelly Bean first, but that is completely up to you. Keep in mind that using the RUU will wipe your internal memory, so back up what needs to be backed up. This doesn’t require you to be rooted, and the state of the bootloader does not matter. It will lock the bootloader, load the stock recovery, and you will lose root. You won’t be able to downgrade without S-Off.
Other Notes:
When using the 4.3 RUU, make sure that Android USB Debugging is enabled.
Bookmarking for later but I wanted to say thanks for the thorough reply!
I can confirm the update never worked, because I never got the confirmation message
and I got prompted again a few hours after I posted.
Are you willing to answer just a few more things?
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
- Get my phone into S-OFF status.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
Are you willing to answer just a few more things?
Click to expand...
Click to collapse
As always, I'm open for questions. Not to sound egotistic, but I enjoy sharing my opinion.
Based on what I've read, it sounds like this is what I ought to do:
- Back up anything I need to. Just to confirm, updating firmware and flashing a new rom wipes out everything in the phone's internal memory, but not external SDcard? Or both?
Updating to the 4.3 firmware wipes your internal memory, not your sd card (although, that may be a very unfortunate circumstance, so it should be backed up as well). The other firmware updates do not affect your memory.
Are apps considered "on the cloud" and I can reinstall by just redownloading, without paying again?
Technically, yes they are "on the cloud." The fact that you paid is saved somewhere within your main Google account that you downloaded the app with. It is possible to pay for apps with your secondary gmail account, which can be switched within the Play Store app.
Except sideloaded apps? Or will I need to find all those APK files and save them somewhere else?
Use Titanium Backup if you can't find the apks. I do save my apks that I download, and I also upload them to Google Drive, since I have multiple Android devices, and I also have a faulty micro sd card that I am yet to replace. I can lose my data at any given moment, but everything is backed up, so I'm not worried.
Is it safe to say they're all in \data\app and \system\app? Or would system\app be unwanted since it's what came with the old phone OS?
Everything within the /system folder is wiped when you flash new roms. That data is NOT backed up while flashing between roms. Also, since it is from an older Android version, it's best to leave them alone. You may back up the data if you like, but I would refrain from restoring the apks along with the data.
The /data directory may be wiped, depending on the dev who built the rom zip. If they added the superwipe script, then /data will be wiped as well. Most devs do not include this, since many people "dirty flash," which is flashing new roms or updates of the current rom without wiping /data first.
- Get my phone into S-OFF status.
You will save yourself a LOT of headaches in the future. It was my S-Off status that allowed me to reflash my firmware when I lost the function of my data/voice antennas while carelessly flashing a port of a phone on a different carrier. Also, if you feel curious to try AOSP roms, then you do not need to do any extra steps to flash them.
- Update firmware (this is a separate process from updating the rom? Where do I get this firmware? Google google google?)
Yes, the firmware handles manages how the hardware of the phone operates. Updating the rom changes how the software looks and behaves. The kernel is sort of a bridge between the firmware and the software, since it manages the firmware (like battery life, processor speed, antennas, etc.), but the kernel is dependent on the software version. The firmware is not dependent on the software version, just as the software version is not dependent on the firmware version.
The only exception of the firmware/software independence is the 4.3 update, which requires a complete update of the firmware, and the older software cannot run on the new firmware without being modded by a dev.
- Install a new ROM (stock or otherwise) which will have these updates built in, so I won't need to regain root.
- Not sure what my bootloader is, maybe TWRP, does it matter? Do the above steps affect it? Should I change it to stock anyway?
Your bootloader is the white screen that shows the TAMPERED status on the top, and little Androids on skateboards on the bottom. With the exception of the firmware information in the top left corner, this screen does not change...ever.
TWRP is your recovery image, which is accessible through the RECOVERY option in your bootloader, or you can boot directly into it through different apps in Android - Titanium Backup is one of them (yes, that's one of the options, even for the free version).
The only reason to return your recovery to stock is to accept OTAs, and also to bring your phone back to the complete factory settings, just as the day when it was first purchased (for the sake of selling the phone, or returning back to Sprint for service}. Otherwise, don't bother with it. You may want to update your version of TWRP, though. If you update to 4.3, you will have to update it. I'm not going to take the time to get into that right now. I've given you enough homework.
- You suggested trying Sense 4 rather than Sense 5 first... any special reason?
I am a very patient person. To me, exploring Android takes time. I enjoy reading before I test, and testing before I settle (which I'm yet to "settle"). All of that being said, I suggested Sense 4 before Sense 5 because I wanted you to experience the both of them. They are truly two different versions of Sense, which one might not realize, as their version numbers are differentiated by one integer (in other words, 4 to 5). Sense 3 was a small step above Sense 2, and Sense 4 was a bigger step from Sense 3. Sense 5 is a complete overhaul of the Sense UI, save the flip clock.
I just feel that skipping from 4.0 to 4.3 is missing out on a great experience, but that is mainly if you actually want to try out different roms. Until the Sense 5 RUU, I still visiting ICS on occassion, but I usually didn't last more than 3 hours before I jumped back to JB.
Click to expand...
Click to collapse
Whew...you're making me work. But I like it. Anymore questions? Feel free to ask.
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
CreeDo said:
OK I've been working on this all afternoon and I'm at an impasse.
You've been a huge help so far and I hope you can guide me through this part.
I want to S-OFF and am following a tutorial: http://www.thefortressofnerditude.com/s-off-your-sprint-htc-evo-4g-lte/
Step 3 says root and install recovery. So I decide I need TWRP.
Already have nandroid and titanium backups both completed.
And I copied the whole SDcard to my computer after.
Annoyingly, TWRP's install page suggests that I need to be in S-OFF.
TWRP says I need S-OFF. S-OFF guide seems to suggest I need TWRP working.
I installed "TWRP Manager". Realize that might not be the same thing as TWRP.
Googled and found it on the TeamWin page.
The page asks first to input my device. I choose Evo 4G LTE (Jewel).
That brings me to this page: http://teamw.in/project/twrp2/98
They suggest I do the android app install method. I follow the first link (Market Link)
and install GooManager, and follow their steps.
Install the app and open it. Tap menu then hit Install OpenRecoveryScript. Tap Yes. Verify that the filename displays your device's code name and hit Yes. The file will download and your device will reboot and install the recovery automatically.
This all goes smoothly, but here's my issue.
It doesn't reboot automatically, or install anything automatically.
I see in the comments a recommendation to reboot into recovery mode.
I choose that in GooManager's menu, and after rebooting I get my bootloader screen with 4 menu options:
Bootloader
Reboot
Reboot Bootloader
Power Down
The only one that sounds sensible to me is bootloader so I pick that.
Now I get some new options:
Fastboot
Recovery
Factory Reset
Clear Storage
Simlock
Image CRC
Show Barcode
So, the only one that makes sense is Recovery. I choose it. The phone reboots.
Now I'm back at the first menu. So I'm in a loop.
Nothing I do in this loop seems to install anything.
So I just rebooted the phone normally and I'm back to my OS.
Where to go from here?
Click to expand...
Click to collapse
Did you unlock your boot loader first? You don't need to be S-off to install a custom recovery. Unlock your bootloader at htcdev.com then install twrp.
Read here for more info:
http://forum.xda-developers.com/showthread.php?t=2420916
Also, I suggest learning how to use fastboot commands. Install twrp using fastboot.
Sent from my EVO using XDA Premium 4 mobile app
OK, so I'm semi-bricked but not panicking yet.
Here's where I'm at.
• Unlocked boot loader successfully
• Installed TWRP using fastboot.
• Followed instructions as closely as I could on moonshine.io to get S-OFF working.
Several times during the process I got "installing device driver software" in my win7 system tray.
Not sure if that's normal. But the drivers seemed to install fine. At first.
But then, during this part of the process:
Moonshining .................(1)
Windows prompted me that it was installing some drivers again, But it failed to install the MTP driver.
After ten tries with the "Moonshining" step, I got "ERROR: don't drink and moonshine!" or something like that.
So, it seems like I need to get this MTP driver going. First I tried solutions on the computer:
• Uninstalled all HTC software, unplugged phone, rebooted,
installed HTC Sync Manager (setup name setup_3.0.52.0_htc.exe), then uninstalled it...
because a tutorial said this would keep the drivers but remove the software. Still no luck on the MTP driver though.
• Found "Mass Storage Device" (my phone) under device manager, removed it, unplugged, rebooted, replugged.
• Plugged cord into back of PC, so I'm using USB 2.0 rather than USB 3.0.
• One suggestion said a certain registry section might have an upperfilter key that shouldn't be there.
But I don't have that upperfilter key so that's not the issue.
Some fixes require getting into my phone (one guy suggests turning off USB debugging)...
but I no longer have a working OS. I can get into my bootloader, I tried Factory Reset.
But after choosing this I go into TWRP and I have no TWRP backups that I can restore.
So my next guess is, I need to get a recovery ZIP (is that basically a ROM?) that TWRP can install.
If that's correct, what ZIP should I get? I was on Android 4.0.3 Sense 4.0, can I download jellybean with Sense 5.0,
and install it via TWRP?
That was my goal all along, but I'm determined to get S-OFF working, so if doing that means my phone gets wiped again,
I guess I just want whatever ROM/recovery/whatever that allows me to change this USB debugging setting,
and try other phone-related fixes to the MTP driver issue.
First of all, flash an ICS rom. I'm assuming that you are still using the same ICS firmware, and you will want to have your phone operational (to enable USB debugging). The link for MeanRom ICS still works. http://old.androidfilehost.com/main/EVO_3D_Developers/mikeyxda/LTEvo/MeanROM-ICS-v65-jewel-ltevo.zip
Ok....since you are on the old HBoot, I think that you need to use the older S-Off methods (LazyPanda or DirtyRacun), if I'm not mistaken. You can not download and flash Sense 5.0 through TWRP as of yet, because you need to be using the new firmware to do so. You may want to pay http://unlimited.io/jewel.htm a visit. Also, to use LazyPanda or DirtyRacun, you need to be using Ubuntu. Another option that you have is to use the regular RUU and update directly to Sense 5.0. You will be stock, unrooted, but you can easily use the latest S-Off method.
Lastly, for your rooting/S-Off needs, you can also use a handy-dandy toolkit from @WindyCityRockr that can handle everything that you need to do. I usually encourage manual labor, but there are some exceptions. http://forum.xda-developers.com/showthread.php?t=2436217
Thanks again for jumping in.
I'm getting somewhere, but still so many difficulties.
Fix one thing, break two more.
I finally have a new working rom, but almost against my will it ended up
being CyanogenMod.
The short version:
- unlocked bootloader, got TWRP going, finally got ADB working (don't think it's the right driver,
but whatever, ADB commands work fine), wiped everything... factory reset, Dalvik, external storage.
- Didn't wipe Internal storage, I wiped only /data/ per some post's recommendation.
- I used ADB PUSH to get a few possible roms onto /sdcard/
PJ75IMG_1.13.651.1.zip (failed with "unable to open zip")
(ROM)_Stock_Rooted_OTA_(3.16.651.3)V2.zip (failed with "unable to execute updater binary in zip")
cm-10.2.0-jewel.zip (cyanogenmod) - success!
So, the phone works. It appears to be at least based on android 4.3... and I'm guessing CM, which updates
frequently, has all those OTA updates bundled into it. Any downsides to CyanogenMod?
I could just proceed from here to reinstall my old apps etc.
I'm still not "S-OFF" which annoys me, but I read a post suggesting it's not really that necessary.
The way they put it is, s-off allows you to access partitions so they can be modded,
but nobody is developing anything interesting for those partitions. Like nobody's doing custom radios and such.
Should I still pursue S-OFF anyway?
If so, is there a way to do it with CyanogenMod?
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Should I still pursue S-OFF anyway?
Click to expand...
Click to collapse
Yes! Being S-On is a complete pain in the BUTT when switching AOSP roms. Have you tried to flash the rom that I posted, MeanRom ICS? I'm really trying to get you to stay on Sense, because S-Off and other different tools work so much better while using Sense. AOSP is better after S-Off. But that's up to you.
If so, is there a way to do it with CyanogenMod?
Click to expand...
Click to collapse
I am not sure. You can try if you have the time. I suggest making a nandroid of your CM rom, and try to flash a Sense ICS rom, not JB...yet.
That awesome app (Windroid Universal Toolkit) doesn't recognize the phone.
Click to expand...
Click to collapse
CM might be the issue here, as well as it might not.
Last question, how should I go about restoring everything?
I had titanium and nandroid backups copied to my computer.
Can it restore to such a wildly different version of the OS?
Click to expand...
Click to collapse
Yes, TB will still work. There are some apps that might cause the restoration process to freeze, so I suggest killing TB and skipping over the app that froze the process when you return.
Can I get back not just apps, but stuff like my keyboard preferences, texting history, etc.?
Click to expand...
Click to collapse
If your keyboard preferences was not backed up, then no. If you were using the stock Sense keyboard, then that is a no as well. As long as your texting history was backed up, it can be restored. Texts are not like apps...their data is typically stored in XML files which are readable through any version of Android (2.3+).
I'm still soliciting my help if you need it.
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
CreeDo said:
I'm for sure going to need it, so thanks very much for the ongoing support!
I got discouraged after all the failures but I'll download Meanrom now.
The thing is... now that Cyanogen mod works, I hesitate to wipe it and try a new one.
Especially since several other roms I tried mysteriously failed to install.
I like that it's jellybean and don't wanna move backwards to ICS.
And I like their goal of cutting out the fluff.
I still want S-OFF, will I end up having to wipe everything again to get it?
Also, I really don't feel confident I have the right drivers for my windows machine.
I can transfer files in USB mode, go into USB debugging, and do the usual ADB commands.
But the phone shows up as a nexus in device manager, but it's definitely evo 4G lte.
I tried installing an executable RUU and it failed after a bit saying it can't detect the device.
And there's that issue where Windroid doesn't detect it.
So I have the feeling that without the right USB drivers, tools like Moonshine will still fail.
I specifically got errors every time when anything tried to install MTP usb drivers. Do I really need them?
You think LazyPanda or DirtyRacun's tools will work even if I never get the MTP thing installed?
Click to expand...
Click to collapse
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Evolution_Freak said:
Feel free to try the facepalm S-off method as well. Works on devices with older software and is super easy. Look here:
http://forum.xda-developers.com/showthread.php?t=2163013
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
CreeDo said:
Cheers, it does look pretty straightforward.
Of course that's what I thought hours ago when I tried moonshine haha.
I'll give it a go.
To be clear, does this method wipe anything?
They don't actually say.
Click to expand...
Click to collapse
Can't remember if it wipes or not. Best thing to do is make a backup with TWRP and keep the backup on your external SD card. If it wipes you can always restore your backup.
Sent from my HTC device
Thanks for the help so far guys. I am currently really enjoying Cyanogenmod. I suspect it's eating battery more,
but then against I am on the phone for hours redoing everything that got changed/removed.
Does anyone know if there's a simple way (or even a difficult way) to restore my texts?
Because the app is totally different, and the old text app was the one that came
with the stock rom, I cannot restore it in titanium. But if I could extract even the raw text that'd be helpful.
Get back to Sense, or get someone with Sense to restore it for you, and save it using a different app. Or maybe try using SMS Backup & Restore from the Play Store. I'm not sure if it can read the backups saved through Sense, but it's worth a try. You just have to navigate to the location of the old backup.
It looks like I can import an XML in this messaging app so maybe if sense offers an export to XML option, I'll be set.
Sense is sort of an OS on top of the OS, right?
Can sense be loaded without flashing a new rom? or is it too integrated with the OS?
This is a ROM Base of the latest LP VS985 23C & 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working updater-script, but this way is much easier & straightforward.
23C Installation Instructions: - Official
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v7.0.zip - BE PATIENT !
FLASH SuperSU for ROOT access
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23C Installation Instructions: - Leak
BACKUP your apps via TitaniumBackup
REBOOT to TWRP recovery (the latest TWRP v2.8.6.0 can be found here)
WIPE everything (system/data/cache/dalvic)
FLASH JasmineROM_v6.0_Unmodified.zip - BE PATIENT !
RESET factory from within ROM (in Settings) is required.
If you run into WiFi/Sync issues, flash CRONTAB_DisableIPv6.zip
Click to expand...
Click to collapse
23B Installation Instructions: - Leak
The installation of 23B is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
1. Make Nandroid backup of your ROM via TWRP recovery
2. Download & extract JasmineROM_v5.0.zip (use Zarchiver)
3. Make sure you don't have any partition images in internal storage (/sdcard)
4. Copy all files in JasmineROM_v5.0 directory to internal storage (/sdcard)
5. (Re)boot into TWRP recovery
6. Use Terminal Command (in TWRP) OR ADB (from PC/Mac/Linux via adb shell) to run the following 3 commands:
Code:
cp /sdcard/installROM.sh /sbin/
chmod 0755 /sbin/installROM.sh
sh /sbin/installROM.sh
The first two commands shouldn't print anything.
The 1st command copies the script to /sbin & the 2nd sets its permissions.
The 3rd command runs the script only if it's in /sbin (1st command) & has executable permissions (2nd command).
If you've messed up with your partitions layout or filesystem (e.g., formatting f2fs), revert to factory setup (e.g., ext4 filesystem - since stock kernel doesn't support f2fs).
The last command will take some time (~10 minutes). BE PATIENT !.
Some entries will appear to hang, do not interrupt or disconnect cable!
The "No space left on device" warning is NORMAL
You should see command prompt & ROM info/release date at the end !
Click to expand...
Click to collapse
7. Flash Download Mode Fix + Debuggable Kernel & Reboot
If you run into issues, it's because you've conflicting data from KK.
Do a factory reset in Settings to restore default LP databases!
You may use TitaniumBackup instead of factory reset > Tap batch actions on the top right > Scroll down to "Manipulate data" > Run "Wipe data for user & system apps"
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Downloads:
Please read carefully the instructions above before proceeding at you own risk!
JasmineROM v7.0 Release: JasmineROM_v7.0.zip
md5: 7ac04a41e1f6bb26f51e50760023395d
JasmineROM v6.0 Unmodified: JasmineROM_v6.0_Unmodified.zip
md5: 18887557219ccbf428a4fe99733698da
CRONTAB + Disable IPv6: CRONTAB_DisableIPv6.zip
md5: c6487922357b330cbb6257d91076ca7d
JasmineROM v5.0 Unmodified: JasmineROM_v5.0.zip
md5: 4e6aec50ab9763c4396dcb5e45408a95
Click to expand...
Click to collapse
Thanks to:
All devs/testers/users contributed to it
@HolyAngel for collaboration on Stock-based ROMs
@bweN diorD & @autoprime for the images!
@annoyingduck & @krazy_smokezalot for final tests
Click to expand...
Click to collapse
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
guitarbedlam said:
You guys are the best! I know everyone has been looking forward to this day. If you wanted to flash KK back, would it work to just flash the modems/KK ROM over this?
Click to expand...
Click to collapse
Yep, just flash the KK ROM + proper kernel & modem
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
jthompson0019 said:
Will this method work for 23a stock? I can't get any method to work for kdz, tot, or root. I lost root when I used active launcher to push 23 a.
Click to expand...
Click to collapse
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
hsbadr said:
This method is for those coming from Stock KK 10B/11C/12B or AOSP LP with KK firmware.
Click to expand...
Click to collapse
Is there a method you would recommend? I can't seem to get anything to work.
jthompson0019 said:
Is there a method you would recommend? I can't seem to get anything to work.
Click to expand...
Click to collapse
You may try this at your own risk. It may work, but not tested.
hsbadr said:
This is a ROM Base of the latest LP VS985 23B for all devs who work on Stock LG system. It was a part of JasmineROM, but since it's Unmodified Stock/Rooted ROM, it should be just a ROM base. It makes it easy to upgrade to LP without the OTA hassle & to prepare partitions for future updates. It also keeps Bump-signed images (TWRP recovery & custom kernels) working without affecting any of the current ROMs/Kernels. You might need to just flash modem & kernel (check this post for official firmware) if you'd like to downgrade or switch ROMs (only if they're not already included in that ROM).
I went the image route (the new method) because I had some issues with some firmware. It run perfectly on my device, but failed to boot (or stuck in a bootloop) for some testers. The reason for Data/WiFi & other issues I've experienced during testing was due Symlinks, Permissions, & SELinux context. They should be identical to stock system. So, to avoid any other unforeseen issues, I decided to write stock images (so it works as expected) & updates will automatically follow the correct symlinks/permissions/context. I can make a working installer-script, but this way is much easier & straitforward.
The installation is quite simple (much less complicated than it sounds): you just need to run installROM.sh script; the other steps are just for preparation/clarification. This method just works in all situations (coming from Stock KK 10B/11C/12B or AOSP LP) we tested to update all relevant partitions. The future updates will be in the form of a regular flashable .ZIP file.
Installation Instructions:
Did you know that... You are the best? ?????
Click to expand...
Click to collapse
Thanks a lot. Worked great. Is anyone having trouble with ADB after updating? My ADB worked fine before. I'm trying to find new drivers to install but can't seem to get it.
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
AngryManMLS said:
Coming from the stock KK running AOSP based LP ROMs right now should I install this to get my modem updated to the LP one? Or can I just flash the LP modem to get that updated?
Click to expand...
Click to collapse
You can just flash the modem, but I have no idea if the 23B modem works with AOSP/CM 12.
Sent from my VK810 4G
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200.
Click to expand...
Click to collapse
You shouldn't post the same thing in multiple threads.
Sent from my VK810 4G
cap1tal1sm said:
I'm having trouble installing the original jasmine from page 200. I go through all the steps to run the install script, and everything goes fine and it installs correctly. When I boot it up, however, it won't load and it gives me the stock verizon boot animation and it hangs there. I didn't flash the download mode fix, was going to do that after I booted up for the first time
EDIT: I reinstalled the script, again, everything goes fine and it shows the release data at the end. Then, I flash the last zip, goes fine, and I reboot just like in the instructions and it gives me a blue and green light from the notification light and it's hanging at the stock verizon boot animation and it doesn't look like it's going anywhere. Anyone can help??
Click to expand...
Click to collapse
Hey, friendly advice. Don't cross post. Especially 3 different threads.
From my VS985 - Jasmine 5.0.11
whatever gets the fastest response
cap1tal1sm said:
whatever gets the fastest response
Click to expand...
Click to collapse
Lol. Ok, not really the best justification. This isn't an IT help desk.
Sent from my Nexus 7 2013
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
cap1tal1sm said:
True that, and let me give you a counter point: How does one extra marginal post in a different forum deteriorate your life in any way possible or imaginable? What is the cost of one more forum post, which by mathematical truth can only lead to one extra page at most?
Is it the opportunity cost of reading my post, and realizing you read the same text somewhere else? Is my ire at my cross post really just anger at re-posts in general? The concept of copying content and under valuing originality? If this is the case, I concede you have a point. I too am an effervescent searcher for good, funny, original and insightful content. My jimmies become quite rustled when I see something I've already seen before.
But here's the irony: just now, you've taken more time to read this post, than the last one!!! Isn't that funny? And it's interesting to think about, for the following reason: What is a post's ultimate value? It's a + b , where a is the value I gain from my post being answered, and b is the value you gain from reading it. Let's think about this post again; this post is literal poop. It is worthless, it's a waste of my time and yours. So really, this post is valueless for everyone involved. Yet, according to the logic of this website's forum, this post is completely fine since it's an original, non-cross post.
Yet my cross posts, which are bad as you suggest, give me immense value! Because my question is answered nearly (but not perfectly) twice as fast, so I get 2a + b return on the post. Do you see how illogical your conception of what is good posts/content, and what is bad?
Eh, but what do I know: I just go to the number 1 school in the US.
Click to expand...
Click to collapse
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
I never bothered doing Bump to get a custom recovery installed. I simply got root on 10B and then disabled automatic updates. As such, I figure this method won't work for me as it involves steps within TWRP. Would my best bet for getting stock rooted Lollipop be to enact Bump to get a custom recovery, and then follow these steps? The Bump stuff didn't make sense to me so I didn't dare venture down that road, and am hoping I can still avoid it...
crazy4android said:
we got us a arrogant lill fellow here...haha thinks he's the only smart person in the world all that schooling and can't even correct a minor android problem kinda ironic having that attitude will not get u any help '
update:
have u ever changed ur file system from ext4 to f2fs? mind the same but it was bc i had changed my filesystem to f2fs...i reformatted it to ext4 and it booted no problem...initial boot takes quite a bit...5 mins or so
Click to expand...
Click to collapse
It's called trolling son. Back in my day, it was an art. Now I just do it for the thrill.
I have no idea how to change file systems. The whole boot partition thing is what weirded me out, I have no idea about that stuff. I ended up flashing back to my kit kat recovery (which had a date of like january 5, lol. So I had been off stock rooted xposed for almost 4 months) and running the commands. Then instead of hanging at the verizon screen at boot, it went into the android is upgrading thing fine.
So I guess it's a directional thing, where you can go forwards in time but not backwards. Which was where I was coming from on Illusion 6.0.