Related
FYI, I to have some Linux/unix experience, but I'm getting rusty. I have never rooted an Android device, but I have on a Palm Pre....
Ok, so now I have instructions on how to root my hero from here:
http://forum.xda-developers.com/showthread.php?t=581577
And I really want a fix for this bug ( http://forum.xda-developers.com/showthread.php?t=581806 ), as well as to run apps2sd, wifi-tether etc.
But before I do, I want to make sure my bases are covered. I've done some searching on the forums, and I keep getting bogged down in a number of lengthy discussions, that don't quite answer everything, so I will ask for some help here.
When I make a recovery rom using the above steps, will that be for a factory fresh install, if I use it to recover? Or, do I have to wipe the phone, and then make the recovery rom image?
If needed, how do I do a restore, using the recovery rom?
How am I supposed to make a Nandroid backup? All I can find are the source code. Where are some executables I can use?
If I need to restore using Nandroid how do I do it? The provided instructions tell me to use the camera button (G1), but my Hero doesn't have one.
Is there anything else I need to do, to make sure I can get back to a factory stock, non-rooted device if needed?
Is there anything else i need to do, so that I can run stuff likes apps2sd, wifi-tether, or any of the root apps at the market?
thanks
fx17 said:
FYI, I to have some Linux/unix experience, but I'm getting rusty. I have never rooted an Android device, but I have on a Palm Pre....
Ok, so now I have instructions on how to root my hero from here:
http://forum.xda-developers.com/showthread.php?t=581577
And I really want a fix for this bug ( http://forum.xda-developers.com/showthread.php?t=581806 ), as well as to run apps2sd, wifi-tether etc.
But before I do, I want to make sure my bases are covered. I've done some searching on the forums, and I keep getting bogged down in a number of lengthy discussions, that don't quite answer everything, so I will ask for some help here.
When I make a recovery rom using the above steps, will that be for a factory fresh install, if I use it to recover? Or, do I have to wipe the phone, and then make the recovery rom image?
If needed, how do I do a restore, using the recovery rom?
How am I supposed to make a Nandroid backup? All I can find are the source code. Where are some executables I can use?
If I need to restore using Nandroid how do I do it? The provided instructions tell me to use the camera button (G1), but my Hero doesn't have one.
Is there anything else I need to do, to make sure I can get back to a factory stock, non-rooted device if needed?
Is there anything else i need to do, so that I can run stuff likes apps2sd, wifi-tether, or any of the root apps at the market?
thanks
Click to expand...
Click to collapse
Hey, thanks for seperating out all your questions! That makes it a lot easier to read!
Ok, time for answers...*cracks fingers*
Recovery ROM doesn't modify your OS, just changes the OS it boots into when you go into "Recovery Mode" (Volume Down+Power, then Home). This is where Nandroid will be (there's a backup and a restore option there...it drops the backup to the sdcard).
When you flash a recovery image, you are still on the factory/stock OS, nothing has changed there. However, if you want to go back after a custom ROM, the Nandroid restore option will be there to pop you back (as if you never left!).
If you want to go back to factory settings, as if you just bought it, there's an official RUU (Rom Update Utility) you can download...check out the stickies in the android development section.
Root things just require the "asroot2" instructions (one of the threads in this forum (How to Root)...shouldn't be hard to spot). That's all that's needed to my understanding.
The Recovery ROM is more just there for Nandroid and if you want to install a custom ROM (like MoDaCo's).
Hope I didn't miss anything!
EDIT: Oh and one more thing, Nandroid just makes an image of the last Nandroid backup to the sdcard. If you want (and I do this), after a nandroid backup, copy off the nandroid folder and rename it (I did nandroid-[date or changes]). Then you can go back to any point in time, drop the folder back in, rename it to "nandroid" and restore.
I'll take a stab
fx17 said:
FYI, I to have some Linux/unix experience, but I'm getting rusty. I have never rooted an Android device, but I have on a Palm Pre....
Ok, so now I have instructions on how to root my hero from here:
http://forum.xda-developers.com/showthread.php?t=581577
And I really want a fix for this bug ( http://forum.xda-developers.com/showthread.php?t=581806 ), as well as to run apps2sd, wifi-tether etc.
But before I do, I want to make sure my bases are covered. I've done some searching on the forums, and I keep getting bogged down in a number of lengthy discussions, that don't quite answer everything, so I will ask for some help here.
When I make a recovery rom using the above steps, will that be for a factory fresh install, if I use it to recover? Or, do I have to wipe the phone, and then make the recovery rom image?
When you use the recovery image you have the option to do a complete wipe/factory install or flash a backed up ROM that you made (Restore).
If needed, how do I do a restore, using the recovery rom?
Just hold down the home button then press the power button which will get you into the recovery screen. From there select restore option.
How am I supposed to make a Nandroid backup? All I can find are the source code. Where are some executables I can use?
After you root your phone you need to flash the recovery image file onto your phone. This will allow you to got into recovery mode by hitting the home/power button as stated above.
If I need to restore using Nandroid how do I do it? The provided instructions tell me to use the camera button (G1), but my Hero doesn't have one.
Home/power button.
Is there anything else I need to do, to make sure I can get back to a factory stock, non-rooted device if needed?
Nope, there is a stock RUU floating around here someplace so if you need it to be unrooted again you can flash that. Otherwise, you can just do the "Factory reset" option from the recovery menu.
Is there anything else i need to do, so that I can run stuff likes apps2sd, wifi-tether, or any of the root apps at the market?
Apps2sd is built into the modaco custom ROM so all you need to do is format the SD card. And wifi is included as well and works on modaco too. If not flashing to modaco then you will need to install apps2sd and format your SD card for it to work. Wifi tethering currently does not work for some reason on a regular rooted ROM.
thanks
Click to expand...
Click to collapse
Hope that helps.
fx17 said:
http://forum.xda-developers.com/showthread.php?t=581577
When I make a recovery rom using the above steps, will that be for a factory fresh install, if I use it to recover? Or, do I have to wipe the phone, and then make the recovery rom image?
If needed, how do I do a restore, using the recovery rom?
How am I supposed to make a Nandroid backup? All I can find are the source code. Where are some executables I can use?
If I need to restore using Nandroid how do I do it? The provided instructions tell me to use the camera button (G1), but my Hero doesn't have one.
Is there anything else I need to do, to make sure I can get back to a factory stock, non-rooted device if needed?
Is there anything else i need to do, so that I can run stuff likes apps2sd, wifi-tether, or any of the root apps at the market?
Click to expand...
Click to collapse
lots-o-questions
1)that guide will work just fine
2)recovery rom isn't a "recovery" of your stuff, you are pushing a custom recovery environment so you can flash custom files on your phone
3)there's a nandroid backup application once you flash the custom recovery to your phone, try backing up, then restoreing to build confidence (backup your /sdcard/nandroid afterwords)
4)don't worry about that... it's in the custom recovery... you'll see it once you flash it to your phone... and the custom recovery will not effect any functionality if you just want to stop at that step and take a breather... it's kinda stressfull
5)self explanitory once you get in there... it's like option 3 in custom recovery once you flash it to your phone
6)find the cdma sprint RUU ... there's links to it spralled across this forum and if you check my past posts I just posted a link to it eairlier today and yesterday evening
7)all the apps you mentioned are built into modoco's custom cdma rom in this thread and work fine out of the box.... i can't vouche for apps2sd cause i only flashed his 1.1 build.... haven't tried 1.2 yet
hope this helps.... and agian... the info is out there if you are willing to find it and if one of us gets a chance we'll try to find answers to the problems you have along the way
so where do I find Nandroid executables?
thanks
OK, I think I got it. The recovery image is just a small file you flash to the device that lets you load other roms. Is that right?
Its the RUU rom, nandroid, or custom roms that you load using the recovery mode right?
thanks
fx17 said:
so where do I find Nandroid executables?
thanks
Click to expand...
Click to collapse
It's not an executable file, it's an image file. It's in the how-to link you posted above. "download http://www.androidspin.com/downloads...roc-v1.2.3.img and place that into the same directory you extracted asroot2."
After you successfully root your phone you need to follow the directions at the end of the how-to in order to flash this image to your phone. This is basically like a "bootloader".
Once you have done this, the next time you hold down home while pressing power you will get the following screen...
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is where you do your flashing/backups/restore.
That's pretty much right!
Now I get it. Most of the work has been done! that makes it a lot easier.
thanks guys.
One final question. how big are the backups that nandroid makes? How much free space do I need on my sd card?
fx17 said:
One final question. how big are the backups that nandroid makes? How much free space do I need on my sd card?
Click to expand...
Click to collapse
Mine was somewhere around 240MB.
thanks guys! this forum is the best!
Got my Hero rooted, recovery flashed, and nandroid backup made!
does the nandroid backup make a copy of your system apps just in case I want them back after I wipe my phone?
kr9091 said:
does the nandroid backup make a copy of your system apps just in case I want them back after I wipe my phone?
Click to expand...
Click to collapse
yes.
basically its a image of the phone at that moment in time.
so you should always backup before you flash anything (themes, roms, beta apps) and i try to backup at least once a week just in case anything happens.
you can copy your nandroid folder to your PC also, that will keep your backup safe if you format/mess up the sd card.
if all else fails, then you can always RUU back to the shipped software and start over at square 1
thedudejdog said:
yes.
basically its a image of the phone at that moment in time.
so you should always backup before you flash anything (themes, roms, beta apps) and i try to backup at least once a week just in case anything happens.
you can copy your nandroid folder to your PC also, that will keep your backup safe if you format/mess up the sd card.
if all else fails, then you can always RUU back to the shipped software and start over at square 1
Click to expand...
Click to collapse
Awesome thanks for the quick reply. Is there really any advantages of wiping my phone instead of just installing a custom ROM over the stock? I have been searching for DAYS here on the forums but can't seem to find a straight answer. Thanks again for all the help!!
kr9091 said:
Awesome thanks for the quick reply. Is there really any advantages of wiping my phone instead of just installing a custom ROM over the stock? I have been searching for DAYS here on the forums but can't seem to find a straight answer. Thanks again for all the help!!
Click to expand...
Click to collapse
some roms will need a wipe before flashing. but others you can get away with no wipe.
pretty much, if you change firmware (1.6,2.0,2.1) you will have to wipe before it will boot. but if you just flash a android 1.5 rom (ttg, fresh, modaco, gumbo, gutted...the list goes on) you shouldn't need to wipe, it is recommended if you have any problems tho.
android isn't like windows mobile you can flash rom after rom after rom on-top of the other as long as you don't change firmware versions (for the most part)
so.... if after the flash you have a lot of force-close messages or if the phone doesn't boot you will need to wipe data. but other than that you should be good.
If you are flashing an Android 1.5 based ROM, you usually don't have to wipe before flashing; I do so I have a clean slate to flash on. If you are flashing a non-Android 1.5 based ROM, then you do have to wipe, or at least it's highly recommended.
EDIT: Damn thedudejdog beat me to it. I need to stop bouncing around so many tabs
Awesome Thanks so much for the help!! All of you guys in the forums are awesome!!! Keep up the good work!!
This is a good way to bring an A500 back to full stock from just about any rom, custom or stock rooted. You need to already have CWM installed.
WIPE SYSTEM/DATA/CACHE/DELVIC FIRST!!!!!!!!!!!!!!!!!!!!!
If you don't already have your UID and SBK get those first and back them up in multiple locations!!!!!!!!!!!!
This quote is shamelessly plagiarized from an answer posted by Moscow Desire on a different thread. Drop in and say thanks to him if it does you some good.
Moscow Desire said:
When you install a custom Rom, you have to wipe the original Data first. This is done in the CWM recovery which you installed.
EDIT; Here are two Gen 1 roms provided by dibb_nz . Please say thanks to her.
HC_3.2_Gen_1_OTA_update.zip
HC 3.1_Gen_1_FULL_update.zip
When you boot to CWM Recovery, you have a menu item "Wipes"
In Wipes;
1. Data/Factory Reset (don't worry, it skips your photos and such)
2. Cache
3. Dalvik Cache
Wait, you're not finished.
Go back to the previous menu, and select "Mounts and Storage".
1. Format System
2. Format Flexrom
Now, go back to the previous menu, and select Install Zip from SD (or similar)
MD
Click to expand...
Click to collapse
You are going to lose all data. I make nandroid backups with data toggled everytime that I do anything to my tablet. Do you?
After following the above instructions,
Just simply flash a stock 3.2 image. It's really too simple. Flash it in recovery. This even works while using the patched bootloader by skryllax_cz. There are a selection of roms midway down this post and at the bottom. Any of them should work for this.
When the 3.2 finishes it's flash and you reboot. The tablet will show "Flashing Bootloader" under the custom skryllax_cz text.
It will reboot on it's own.
That's it. You should be able to OTA.
I recommend going to the Play store and downloading/install the Acer Update Enhancement utility after the tablet settles down.
However, my tablet downloaded a small update right away without it.
Here is an additional option as suggested by dibb_nz in the 11th post below. drop down and say thanks if it helped!
dibb_nz said:
Just a thought, the update zips can be flashed in 2 ways.
If u use the stock recovery then rename the file to "update.zip" and remember to remove it from yr sdcard after you're done. This is really important!! You'll end up in strife if u don't!!
With a custom recovery then use install zip option.
With the 3.1 zip u can retrieve yr cpuid (if u need to) then update to the unlocked ICS bootloader directly. This isn't possible with the 3.2 zip
Have a gr8 day people
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
Good luck and please post your results. Thanks.
Here's a link to a stock 3.1 https://www.dropbox.com/s/fpdy13u4ufec461/Acer_A500_4.010.38_COM_GEN1.zip. It is probably easier to go with one of the 3.2 roms below. But if you want it there it is.
(Directions; Flash the stock 3.1 (Acer_A500_4.010.38_COM_GEN1.zip) AFTER WIPING SYSTEM/CACHE/DATA/DELVIC, reboot, then ota to ICS. After you do the first OTA and it reboots it will say a Flashing Bootloader message then reboot with all stock everything.)
Stock 3.2 - https://www.dropbox.com/s/fpdy13u4ufec461/Acer_A500_4.010.38_COM_GEN1.zip
Stock 3.2 provided by dibb_nz - http://www.4shared.com/zip/GgHzZieZ/HC_32_update.html
Here are two Gen 1 roms provided by dibb_nz. Please say thanks to her.
HC_3.2_Gen_1_OTA_update.zip
HC 3.1_Gen_1_FULL_update.zip
New Link
jasenlee1984 had success using Acer_A500_7.006.03_COM_GEN1 3.2 rom from blackthund3r's stock firmware thread, http://forum.xda-developers.com/showthread.php?t=1816560
If it helps you, click his name and then the thanks button.
-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
I have included post 20 from below. It is a guide for getting recovery back should something go wrong. What it will do is install CWM as well as the V8 bootloader. After that you can start all over or flash whatever you want.
I prefer to use Blackthund3rs APX Flash Tool. To get the apx tool google this. blackthund3r apx tool
Basically what you will do is get the tool, open it, choose bundle market, choose 17, use default bct, enter APX download mode, and flash the V8 bootloader with CWM.
The steps are... (Copied from here.)
Step 1.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Step 2.
Step 3.
Step 4.
I used number 17.
Step 5.
Step 6.
Step 7.
I used the default since my tab was fried.
Step 8.
At this point you will have to choose to enter APX mode manually. Follow the instructions on the next screen.
Once you are in APX mode and plugged into the pc you should see the message APX device connected. Choose the next arrow, once it runs for a few seconds it will ask you to confirm that the APX download mode has started.
Once it has. Confirm and wait for it to finish. Get into CWM, flash the rom and you should be good to go.
But other than that you should be back to normal in no time.
Good luck.
And again with the links.
Here's a link to a stock 3.1 https://www.dropbox.com/s/fpdy13u4ufec461/Acer_A500_4.010.38_COM_GEN1.zip. It is probably easier to go with one of the 3.2 roms below. But if you want it there it is.
(Directions; Flash the stock 3.1 (Acer_A500_4.010.38_COM_GEN1.zip) AFTER WIPING SYSTEM/CACHE/DATA/DELVIC, reboot, then ota to ICS. After you do the first OTA and it reboots it will say a Flashing Bootloader message then reboot with all stock everything.)
Stock 3.2 - https://www.dropbox.com/s/fpdy13u4ufec461/Acer_A500_4.010.38_COM_GEN1.zip
Stock 3.2 provided by dibb_nz - http://www.4shared.com/zip/GgHzZieZ/HC_32_update.html
Here are two Gen 1 roms provided by dibb_nz. Please say thanks to her.
HC_3.2_Gen_1_OTA_update.zip
HC 3.1_Gen_1_FULL_update.zip
New Link
jasenlee1984 had success using Acer_A500_7.006.03_COM_GEN1 3.2 rom from blackthund3r's stock firmware thread, http://forum.xda-developers.com/showthread.php?t=1816560
If it helps you, click his name and then the thanks button.
edit: update 16th Dec
GUYSnGURLZ I have uploaded a folder for you....its the 3.1 Full Update and includes iconiaroot.apk and acer recovery intaller.apk
There's also a readme file in there how to install, root and flash a custom recovery...enjoy
http://www.mediafire.com/?9hsmbilzz4c1a
@ jdgM3NT4L Excellent Post/Thread and thanks for this its sooooooo easy, nice find!
dibb_nz said:
hi m8 I have it uploaded to 4shared if that helps.
Click to expand...
Click to collapse
Hey thanks. I'd be glad to link to it if you don't mind.
dibb_nz said:
Did this again yesterday on v6 still w8n for OTA, flashed v8from HC but nothing as yet,
maybe need v8 from ICS?? I give it a few hours more, missing stryker, lol.
Click to expand...
Click to collapse
Did you update from the Play Store that silly Acer Enhancement app or whatever it is called?
dibb_nz said:
And thanks for this its sooooooo easy, nice find!
Click to expand...
Click to collapse
Thank you for all that you do here. You're really saving alot of peoples arses lately.
Kinda curious. Did this method work for the A501 folks?
not working for me
followed the instructions as posted, still waiting on the OTA update to ICS
i can't even boot into CWM now, i get a android robot with a yellow exclamation mark.
how can i fix it? plz help
thanks
The Stock rom that you put on is just that... Stock. So you lost CWM when you flashed it.
What you can do now is...
a: Wait for a little bit, check for updates again.
b: This one kind of blows the whole point of doing the downgrade in the first place. But... Use this and get Root. Install Acer Recovery Installer from the Play Store and install a custom recovery.
c: This one at your own risk. Mainly because I have not tested this way and I have no idea if the bootloader will flash properly or not. Go here and get the update for a 3.2 (Acer_A500_7.006.01_COM_GEN2) stock rom, then see if you can update the rest of the way to ICS. Be sure to put it in the root of your SD card and name it properly to update.zip. Then reboot as if you are going into CWM. If you want to wait until tomorrow I am downloading the roms tonight and I will test it. Should be finished by noon Central U.S. time (-06:00gmt)
d: Go here http://forum.xda-developers.com/showthread.php?t=1205204&highlight=cwm+honeycomb+3+1 and look around. See if any of the options there suit you better.
Good luck.
And if you have any more trouble say the word.
EDIT. I am having a pretty busy day. I'll have to try this a little later this afternoon. Sorry if you are waiting.
JdgM3NT4L said:
Hey thanks. I'd be glad to link to it if you don't mind.
Did you update from the Play Store that silly Acer Enhancement app or whatever it is called?
Thank you for all that you do here. You're really saving alot of peoples arses lately.
Kinda curious. Did this method work for the A501 folks?
Click to expand...
Click to collapse
Ended up flashing my old 3.2 update.zip and it OTA'd me all the way to ICS from that??
Yep 2nd time I tried it I had enhancement app
PM'd u really links, I also uploaded the update. Zip if folks want it 7.006.03gen1
And thanks for yr kind words J all part of the service
Sent from my A500 using XDA Premium HD app
Frozen Goodness
Thanks for this easy pass. I used this yesterday and the OTA'd my way to ICS and then used Blackthun3ers tools to root and install the V8 bootloader. All in all it was pretty painless.
Glad that it worked for you. I've updated the first post. Sorry for putting you through the extra step of installing 3.1. It seems to work even better when I just flash a nice stock 3.2.
New links posted for going directly to 3.2 Honeycomb Stock with factory bootloader in the OP.
And again. This is safe to do when running any bootloader. If you want full stock. This works well.
And thanks a million dibb_nz. So glad you're here to help out.
So this method works also for ICS bootloader?
knevski said:
So this method works also for ICS bootloader?
Click to expand...
Click to collapse
Seems to work with any boot loader. Just wipe first or be prepared to have problems.
It is easy to fix, but a bit of a pain.
Just a thought, the update zips can be flashed in 2 ways.
If u use the stock recovery then rename the file to "update.zip" and remember to remove it from yr sdcard after you're done. This is really important!! You'll end up in strife if u don't!!
With a custom recovery then use install zip option.
With the 3.1 zip u can retrieve yr cpuid (if u need to) then update to the unlocked ICS bootloader directly. This isn't possible with the 3.2 zip
Cannot confirm whether we can repair borked partitions with this, has anyone tried it??? Would save alot of probs some have had with drivers and apx mode...
Have a gr8 day people
Sent from my GT-I9300 using XDA Premium HD app
dibb_nz said:
Just a thought, the update zips can be flashed in 2 ways.
If u use the stock recovery then rename the file to "update.zip" and remember to remove it from yr sdcard after you're done. This is really important!! You'll end up in strife if u don't!!
With a custom recovery then use install zip option.
With the 3.1 zip u can retrieve yr cpuid (if u need to) then update to the unlocked ICS bootloader directly. This isn't possible with the 3.2 zip
Cannot confirm whether we can repair borked partitions with this, has anyone tried it??? Would save alot of probs some have had with drivers and apx mode...
Have a gr8 day people
Sent from my GT-I9300 using XDA Premium HD app
Click to expand...
Click to collapse
Thanks for adding the good info.
I agree with your assesment of 3.2 HC. It's really only good to me as a waypoint on the path to full stock ICS.
I don't know if the 3.2 rom repairs the partitions or not. I would not be terribly suprised if it did fix those.
You can flash the unlocked ICS bootloader to the 3.2. But, the only good ( And this is pretty good) thing that doing this does is...
On the reboot from the pass screen hold your volume rocker. Depending on the one that you press, you'll either get the boot options. Or you'll boot to CWM. It is great to fix the bootloop issue if you are as goofy as I was and forgot to wipe first.
This was how I tried to do it a few weeks ago, through the stock recovery, and I got stuck in a bootloop
BUT, I did the thing where you hold down Vol Up+ Power then flick the switch back and forth and that got me booted into stock HC
Wow this is awesome! Cannot believe how easy this was. Worked flawlessly. I flashed the stock 3.2 rom, booted up and DL the acer app right away then checked for updates. After a few websites, I was on stock ICS. Thanks!
Thanks for posting your results guys. Glad that it worked for you.
Thumbs up to every post in this thread
I used all of my daily thanks on this thread, it was more than helpful to me. The information in this thread is clear and precise as well as very easy to follow. Because of this thread I am now on stock Android 4.0.3 finally.
Let me give a little back story. I bought my Iconia A500 in August of 2011 and loved it. Within the first night I had it I had Clockwork Mod Recovery on it with a custom 3.2 ROM on it. I had my A500 for about 2 months and then life through me a curve and I lost my job week made my finances really tight so I had to pawn my beloved A500. I know I know how could I dare do that, but like I said my finances got bad tight. I managed to get another job about two months after I pawned it but I could not ever seem to get enough cash saved to get it out of pawn but I did manage to pay the renewal fee on it every month until this last Monday when I finally got it out of pawn.
Now I had been reading thread after thread to learn how to go back to stock so I could do the OTA update. I found this thread earlier today and now I after a flash of the file I downloaded from the four share link in the OP and three separate OTA updates my tablet is on ICS. A big thanks to everyone that posted in this thread. In my opinion it should be made a stickie.
T-Macgnolia said:
I used all of my daily thanks on this thread, it was more than helpful to me. The information in this thread is clear and precise as well as very easy to follow. Because of this thread I am now on stock Android 4.0.3 finally.
Let me give a little back story. I bought my Iconia A500 in August of 2011 and loved it. Within the first night I had it I had Clockwork Mod Recovery on it with a custom 3.2 ROM on it. I had my A500 for about 2 months and then life through me a curve and I lost my job week made my finances really tight so I had to pawn my beloved A500. I know I know how could I dare do that, but like I said my finances got bad tight. I managed to get another job about two months after I pawned it but I could not ever seem to get enough cash saved to get it out of pawn but I did manage to pay the renewal fee on it every month until this last Monday when I finally got it out of pawn.
Now I had been reading thread after thread to learn how to go back to stock so I could do the OTA update. I found this thread earlier today and now I after a flash of the file I downloaded from the four share link in the OP and three separate OTA updates my tablet is on ICS. A big thanks to everyone that posted in this thread. In my opinion it should be made a stickie.
Click to expand...
Click to collapse
Hope you get to enjoy your tablet now that you've got it back!
And thanks for the kind words. I'm very glad that it helped you.
T-Macgnolia said:
I used all of my daily thanks on this thread, it was more than helpful to me. The information in this thread is clear and precise as well as very easy to follow. Because of this thread I am now on stock Android 4.0.3 finally.
Let me give a little back story. I bought my Iconia A500 in August of 2011 and loved it. Within the first night I had it I had Clockwork Mod Recovery on it with a custom 3.2 ROM on it. I had my A500 for about 2 months and then life through me a curve and I lost my job week made my finances really tight so I had to pawn my beloved A500. I know I know how could I dare do that, but like I said my finances got bad tight. I managed to get another job about two months after I pawned it but I could not ever seem to get enough cash saved to get it out of pawn but I did manage to pay the renewal fee on it every month until this last Monday when I finally got it out of pawn.
Now I had been reading thread after thread to learn how to go back to stock so I could do the OTA update. I found this thread earlier today and now I after a flash of the file I downloaded from the four share link in the OP and three separate OTA updates my tablet is on ICS. A big thanks to everyone that posted in this thread. In my opinion it should be made a stickie.
Click to expand...
Click to collapse
We have some of the best people in the XDA community right here at this forum. Some really good helpers and knowledgable folks.
Makes me glad to be a Mod.
Kudos people.
MD
man i suck so bad at this. well, i followed all your steps exactly from what i could tell. i mean there weren't that many nor were they complicated. now i have a continuous android with gears logo that never ends when i boot normally and when i go to recovery its an android with an exclamation. wtf did i do to screw this so bad. do i need to run linux now to fix this garbage or just chuck this pos. damn acer, ever since i updated to ics it was downhill and me tryin to fix it since then. probably me just not leet enough to fix it myself im guessing. id appreciate any suggestions on how to dig myself out of this. thnaks.
raotheconqueror said:
man i suck so bad at this. well, i followed all your steps exactly from what i could tell. i mean there weren't that many nor were they complicated. now i have a continuous android with gears logo that never ends when i boot normally and when i go to recovery its an android with an exclamation. wtf did i do to screw this so bad. do i need to run linux now to fix this garbage or just chuck this pos. damn acer, ever since i updated to ics it was downhill and me tryin to fix it since then. probably me just not leet enough to fix it myself im guessing. id appreciate any suggestions on how to dig myself out of this. thnaks.
Click to expand...
Click to collapse
Hi, sorry to hear that you are having problems. The good news is as long as you followed my big red warning about having your sbk you aren't in too bad of shape. The only reason to do the linux thing is if you did not get your sbk/uid.
There is more than one way to take care of this. I prefer to use Blackthund3rs APX Flash Tool. To get the apx tool google this. blackthund3r apx tool
Basically what you will do is get the tool, open it, choose bundle market, choose 17, use default bct, enter APX download mode, and flash the V8 bootloader with CWM. After that you can start all over or flash whatever you want.
The steps are... (Copied from here.)
Step 1.
Step 2.
Step 3.
Step 4.
I used number 17.
Step 5.
Step 6.
Step 7.
I used the default since my tab was fried.
Step 8.
At this point you will have to choose to enter APX mode manually. Follow the instructions on the next screen.
Once you are in APX mode and plugged into the pc you should see the message APX device connected. Choose the next arrow, once it runs for a few seconds it will ask you to confirm that the APX download mode has started.
Once it has. Confirm and wait for it to finish. Get into CWM, flash the rom and you should be good to go.
But other than that you should be back to normal in no time. To get the apx tool google this. blackthund3r apx tool
Good luck.
EDIT; Here are two Gen 1 roms provided by dibb_nz. Please say thanks to her.
HC_3.2_Gen_1_OTA_update.zip
HC 3.1_Gen_1_FULL_update.zip
Hi. I have this problem. I have downgrade my mytouch 4g to 221. It work like a charm. And than I use TRUE PermaRoot and the ULTIMATE S=Off!!! to get to the root. Everything worked but after reboot I have blank screen and flushing orange light. When I vol down and power button for boot loader then I have blank screen and steady green light and nothing is happening. How do I fix it? and now when I connect the phone to the computer its not recognizing the phone as htc. The computer is looking for drivers for a qualcomm device. Any advise or should I get new phone?
You're right, the bootloader is gone. Nothing can be done in this case. Well, unless you are able to dig really deep.
There is a thread for resurrecting HTC Sensation and the similar procedure exists for a couple of other phones (Samsung SkyRocket, if I remember right). If you're proficient, you can try how it was done and recreate a similar procedure for MT4G. You need the special drivers, special SW, hboot.img that was the last on your phone, and some more stuff.
I really like the phone...
I would direct you to http://forum.xda-developers.com/showthread.php?t=1394238 for assistance.
shadowharbinger said:
I would direct you to http://forum.xda-developers.com/showthread.php?t=1394238 for assistance.
Click to expand...
Click to collapse
His phone is a paperweight unless he is able, by some miracle, to do what Jack was talking about.
Ordered my Nexus 4 on the 13th. Still waiting.
Thanks guys, but I have no screen to look at. The computer dose not recognize the phone as HTC. I can not just enter bootloader, its not there any more or is badly corrupted.
If you didn't understand what I wrote - then you answered my implicit question, and you don't have the skills that it takes to even try to resurrect QHSUSB_DLOAD brick. In that case, send your phone for JTAG-repair or sell it and get another one.
darekmos said:
Thanks guys, but I have no screen to look at. The computer dose not recognize the phone as HTC. I can not just enter bootloader, its not there any more or is badly corrupted.
Click to expand...
Click to collapse
Jack_R1 was referring to this thread http://forum.xda-developers.com/showthread.php?t=1522351 and you would need to adapt it to the glacier phone. Also, this is really a great read http://tjworld.net/wiki/Android/HTC/Vision
---------- Post added at 11:16 AM ---------- Previous post was at 10:23 AM ----------
acefsw said:
Jack_R1 was referring to this thread http://forum.xda-developers.com/showthread.php?t=1522351 and you would need to adapt it to the glacier phone. Also, this is really a great read http://tjworld.net/wiki/Android/HTC/Vision
Click to expand...
Click to collapse
Also, as an fyi to lurkers, the VISIONary method was known to create bricks in the G2 community and since the devices are similar, I would think that it has a fair chance of bricking glaciers. I would always recommend the afb method found here http://wiki.cyanogenmod.org/wiki/TMobile_myTouch_4G:_Full_Update_Guide
It was never proved nor disproved, but all the factual evidence was pointing to the fact that there was no "bricking" method of rooting, there were just crappy eMMC parts that went bad anyway after some time, even if not rooted - rooting and flashing just made it faster. You might want to read long debates that went during that time.
Jack_R1 said:
It was never proved nor disproved, but all the factual evidence was pointing to the fact that there was no "bricking" method of rooting, there were just crappy eMMC parts that went bad anyway after some time, even if not rooted - rooting and flashing just made it faster. You might want to read long debates that went during that time.
Click to expand...
Click to collapse
Yeah, I read a bunch about it at the time, hence I never loaded a custom rom after rooting as I had the supposedly bad eMMC on the MTg4. I eventually flashed the Glacier One v2 rom, which solved some minor issues. When I originally rooted, I did the G2 first (good eMMC), via the adb method because a lot of guys got bricks using VISIONary which it was claimed at the time that it corrupted the bootloader and there were fewer reports of bricks even with the bad eMMC via adb, and those were mostly due to not following instructions and poor typing skills. That, and I feel more comfortable using adb rather than some one or two click solution. ymmv.
acefsw said:
Yeah, I read a bunch about it at the time, hence I never loaded a custom rom after rooting as I had the supposedly bad eMMC on the MTg4. I eventually flashed the Glacier One v2 rom, which solved some minor issues. When I originally rooted, I did the G2 first (good eMMC), via the adb method because a lot of guys got bricks using VISIONary which it was claimed at the time that it corrupted the bootloader and there were fewer reports of bricks even with the bad eMMC via adb, and those were mostly due to not following instructions and poor typing skills. That, and I feel more comfortable using adb rather than some one or two click solution. ymmv.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Erm, I believe you misundertood. Not trying to be offensive, just saying.
Ordered my Nexus 4 on the 13th. Still waiting.
estallings15 said:
View attachment 1558834
Erm, I believe you misundertood. Not trying to be offensive, just saying.
Ordered my Nexus 4 on the 13th. Still waiting.
Click to expand...
Click to collapse
Maybe not, but my understanding is that rooting wasn't the problem per se, but flashing may have sped up eMMC failure. It was never proved either way. However, a lot of G2s with bad eMMC bricked using VISIONary, but not via gfree using adb, So, my conclusion: don't use VISIONary. Hence, I did not use VISIONary to root Mtg4, (bad emmc). After rooting via adb/gfree, I left it stock because it was theorized that flashing might speed up the process of emmc failure i.e played it safe based on what was known at the time. Also, many people never bothered to check emmc or rom version, (e.g. 2.3.4 vs 2.2.1), prior to using VISIONary, (or the VISIONary +gfree method for that matter), and either bricked or soft bricked their phones, hence my opinion that the safest method regardless is the one posted at cyanogenmod or the pdf by strawmetal and that their instructions are clearer than the VISIONary+gfree method. So, maybe I don't understand the whole subject, but those are my conclusions based on reading here and other forums. Maybe, you could explain the known causes of emmc failure better for me and share your opinion regarding rooting methods. Thanks.
acefsw said:
Maybe not, but my understanding is that rooting wasn't the problem per se, but flashing may have sped up eMMC failure. It was never proved either way. However, a lot of G2s with bad eMMC bricked using VISIONary, but not via gfree using adb, So, my conclusion: don't use VISIONary. Hence, I did not use VISIONary to root Mtg4, (bad emmc). After rooting via adb/gfree, I left it stock because it was theorized that flashing might speed up the process of emmc failure i.e played it safe based on what was known at the time. Also, many people never bothered to check emmc or rom version, (e.g. 2.3.4 vs 2.2.1), prior to using VISIONary, (or the VISIONary +gfree method for that matter), and either bricked or soft bricked their phones, hence my opinion that the safest method regardless is the one posted at cyanogenmod or the pdf by strawmetal and that their instructions are clearer than the VISIONary+gfree method. So, maybe I don't understand the whole subject, but those are my conclusions based on reading here and other forums. Maybe, you could explain the known causes of emmc failure better for me and share your opinion regarding rooting methods. Thanks.
Click to expand...
Click to collapse
I will say that I've rooted 3 Glaciers with Visionary + gfree and none of them have failed.
I would have to agree with Jack_R1's earlier statement. Poor quality components brought about a higher rate of eMMC failure. Flashing only sped the process up. There were several instances of unrooted Glacier's failing while doing official updates. It seems that flashing just sped up a process that was bound to happen on multiple devices due to quality issues. Rooting usually leads to flashing.
TL; DR. Hardware failure.
Ordered my Nexus 4 on the 13th. Still waiting.
LG G Stylo (T-Mobile/MetroPCS) ROOT (5.0.2 & 5.1.1 ) - TWRP Recovery - Unbrick Guide
DO THIS AT YOUR OWN RISK
WARRANTY IS NOW AVOID IF YOU PROCEED WITH ROOT AND TWRP
Windows Machine/OS Only
----------- Lets Proceed on to Rooting LP 5.1.1 (One Click Method) -----------1- Click Here and Download LGGSTYLO_LP511_OneClickRoot.zip File
2- Click Here and Download LG USB Drivers ( Thanks @GameTheory. )
"NOTE: skip Drivers if you have them already install"
4- Enable USB Debugging via Developer Option.
5- Decompress LGGSTYLO_LP511_OneClickRoot.zip on Root C: drive for easy access or any convenient location.
6- Now lets head over where we decompress that zip file and just double " LG_Root_Script.bat "
7- LET the script run to FULL COMPLETION, Your Device will Reboot twice so be patient.
IF YOU HAVE YOU DEVICE WITH LOCKSCREEN CODE / SWIPE CODE NEED TO UNLOCK SCREEN ON EACH REBOOT FOR THE SCRIPT TO PROCEED
Check Image for the whole process - CLICK TO SHOW CONTENT
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
8- when the process say
Code:
ui_print - Done !
press Ctrl+C
press N then ENTER
( Check Image - CLICK TO SHOW CONTENT )
- And you are done your device is now Rooted
- Phone will Reset and you need to wait till phone is fully Rebooted to system it may take a few minutes so be patient.
NOW YOU CAN PROCEED TO FLASH CUSTOM RECOVERY (TWRP)
-----------------------------------------------------------------------------------------------------------------------
THIS METHOD ONLY WORKS IF YOU ARE IN LP 5.0.2
----------- Lets Proceed on to Rooting LP 5.0.2 -----------
First of all Thank you @avicohh for LG One Click Root GUI/Script base on his Guide I Have successfully Rooted the Stylo using and Following some steps from there just adding some thing you may see in the progress of rooting:
Original LG One Click Root Guide and File Download -CLICK HERE-
After getting all necessary files this is what i did
1- Install LG drivers if they are not installed yet. (VERY IMPORTANT)
2- Download the LG One Click Script Root file above and extract to some folder. (double click on the 7z exe file)
3- Enable Usb debugging on your phone. (Go to Settings > General > About phone > Software information, tap Build number seven times and then go to Settings > Developer options and turn on Usb debugging) (THIS IS VERY IMPORTANT STEP)
4- Connect your phone to pc. (it will install driver when connected just wait till is done)
5- Switch to MTP when drivers are full install
6- Double click on the LG Root Script.bat file (the Script will run)
7- Follow the instructions.
*Please leave your feedback if it worked for you
Many Many Thanks to @avicohhfor the LG One Click Root
P.S. I'm not a Dev. I just followed the original guide and the only thing i haven't install is Custom Recovery.
If you came across some Fail attend messages just wait a few more seconds, if that doesn't work try again in my case the first try work and 2 fail attends messages came up so just wait a few sec. if that happen
BE PREPARED. First boot can take a while!!! can stay on logo for up to 3 to 5 minutes or sometimes little more before it goes into Optimizing Apps. Have patience. Subsequent boots a pretty speedy.
------------------------------------------------------------------------------------------------------------
TWRP (Custom Recovery) for LG G Stylo T-Mobile (H631) and Metro (MS631) Variant ONLY
------------------------------------------------------------------------------------------------------------
- Download Custom Recovery File from TWRP 2.8.7.0 v10j Click HERE (Thank you @Unjustified Dev and @fix-this! )
After Rooting your device (T-Mobile or Metro Variant)
1- Check -Enable OEM Unlock- under Developer Option (Skip this part if you are 5.0.2)
2- download Flashify from Google Play Store
3- Open Flashify.
4- Do a Stock Recovery Back-up (Recommended)
5- Flash Recovery Image.
6- Will ask to Reboot System and will take you to TWRP Custom Recovery.
7- Now you are done just Reboot System from Recovery or do a FULL BACK-UP
NOTE : This New TWRP (Custom Recovery) have the new fix (Showing Half Screen only) for the new LG G Stylo Hardware Panel.
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
LG G Stylo Update Firmware | Unbrick Guide by @GameTheory.
IF YOU ARE USING @GameTheory. v10i UPDATE ZIP DON'T FLASH v10j UPDATE ZIP , I REPEAT DON'T FLASH v10j UPDATE ZIP YOU'LL END UP WITH BOOTLOOPS/SOFT BRICK
-------------------------------------------------------------------------------------------------------------
Just Follow step from link below - Thank you @GameTheory.
http://androidcreations.weebly.com/lg-g-stylo.html
------------------------------------------------------------------------------------------------------------
Every KDZ Release for T-Mobile and Metro can be found here :
http://forum.xda-developers.com/android/development/read-trying-to-root-kdz-files-kdz-tmo-t3152531
------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
Full v10j Stock Restore / Update
Use this guide if you are on @GameTheory. v10i or want to deleted all trace of root and twrp (Back to Stock)
Full v10j Stock Restore / Update
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
i just picked up the tmob version yesterday, nice device. not the greatest screen ive had but not bad. im also rooted, we just need twrp so we can use xposed.
waiting on TWRP
As previously posted, I am also waiting on a conduit to get xposed installed.. a device without it and all the benefits it brings feels unreal to me..
i think we need to ask xda to make a dedicated section for this device. the battery life is unreal on this thing, my lcd has been on and in use for almost 10min and i have not dropped even 1%.
fix-this! said:
i think we need to ask xda to make a dedicated section for this device. the battery life is unreal on this thing, my lcd has been on and in use for almost 10min and i have not dropped even 1%.
Click to expand...
Click to collapse
+100 on that (Battery life + dedicated section for the phone) i have to agree with the battery life pretty neat and i'm sure is because CPU is doesn't have higher clock and screen is not so power hunger, other thing i'm satisfied is the memory management no matter what i do i haven't seen going lower than 1gb of ram always i been having between 1.2gb to 1gb free never had that before so pretty neat and i do have a lot of apps install most of them run in the background,
How can be make a request about making a Dedicated Section for the LG G STYLO? where do i need to sign if that happen i'll be posting some Bootanimations for this phone porting some old ones i created for the G2 and probably making some new ones.
I am pretty impressed with the device. I just bought it for my wife, which she doesn't care what phone I give her as long as it doesn't break the bank. Not able to do that with any of the flagships. Decided to give it a try risking not having the dev support. Hopefully more people takes the risk so we can have custom roms to play for. (not sure if my wife would like that) LOL
Ah, good, a T-Mobile Stylo thread. I just posted my thoughts in the thread for the Boost (Sprint) version, but anyway, I'm mostly liking this phone (except that the camera app doesn't offer manual exposure controls). I'm not sure I'm going to root mine just yet (hell, I still haven't rooted my Avant!), but it's nice to see that a root is available.
i'll leave this here First Custom Boot Animation for the Stylo
https://www.youtube.com/watch?v=wP5EZfmE-oQ
This is really a Lollipop issue, rather than a problem with the phone itself, but I found that the Embware call blocker (which disappeared from Google Play, go figure) doesn't work on the Stylo. It turns out, most of the call blockers out there aren't working on Lollipop.
What I particularly want is a pickup/hangup type of block, so Rachel from Card Services can't even leave a voicemail. I had this capability with the Embware blocker on the KitKat-equipped Galaxy Avant, even before I got around to rooting it. It looks like Google tweaked Lollipop to prevent pickup/hangup blockers from working. #&^%$%^!!!
Extreme Call Blocker claims to work on L, but I'm wary of forking over the cash for it.
There is a built-in reject list under the Call Settings menu, but it's just a straight-to-voicemail reject. I don't want to waste my time deleting spam voicemails, though Visual Voicemail is at least quicker than calling in.
I suppose I could just call T-Mobile and see if they could turn off voicemail entirely. That would at least make the native call blocker useful.
Timberwolfhusky said:
,
Click to expand...
Click to collapse
i found this post to open a new phone section if we show support for the STYLO we may get a Section for it and people can just go there for Q&A, Themes,Dev work and so on, i know the Phone still brand new in everyone eyes but early support doesn't hurt
http://forum.xda-developers.com/show....php?t=1660354
P.S. @Timberwolfhusky you are the only person not in Boost Mobile thread so
I'm considering buying the Stylo. Is it going to get a lot of support or is it mostly about flagships G3/G4 these days?
guest_2011 said:
I'm considering buying the Stylo. Is it going to get a lot of support or is it mostly about flagships G3/G4 these days?
Click to expand...
Click to collapse
is to early to say it but i have seen a lot of activity and a lot of people are interested on this device, some user with the Zmax are going to be upgrading to the Stylo, we have a pretty good start phone is 100% Rootable as you can see on the 1st post and @fix-this! is working getting the TWRP (Custom Recovery) so i would say we are getting good support so far, Not a lot of support but good.
P.S. this Device is Brand new just got release.
I've also seen some articles that indicate that outside of North America, it's being marketed as the "G4 Stylus" - and also in the international market there's also a G4c model with similar specs; like the Stylo, it has a 720p screen, but it has a smaller form factor than the flagship G4, no stylus, and an 8MP camera.
The T-Mobile G Stylo seems to be the best of the bunch, though: double the RAM and double the storage of the Boost version. Having been a T-Mobile subscriber for a while now, I'm glad to see that they bumped up the specs. It also has the unlock app baked-in, so if you're eligible to unlock it, there's no need to call in or fumble around with unlock codes. I used the unlock app on my Avant before I bought the Stylo, and it worked smoothly and easily. If you're not eligible to permanently unlock it, you can still get a 30-day unlock for international travel.
I'm finding that I like this phone a LOT, in spite of the lack of manual camera settings and the Lollipop-related call blocker issues. The HDR mode seems to be able to handle backlit subjects well enough that the lack of manual exposure control isn't as big a deal as I was thinking it would be.
So far, battery life looks to be in the "outstanding to exceptional" range. It reminds me of the F3 in that respect, but this is a vastly better phone than the F3 could ever hope to be. At least somebody is listening when it comes to battery life!
I'm going to hold off on rooting mine for now, though, at least until I can SIM-unlock it. In any case, I've always been a bit cautious about modding my primary phone.
How's the battery life compared to the tmo zte zmax?(for those that had the zmax)
Also, does this have the "feature" that when the phone reaches certain temps it lowers and prevents you from turning up screen brightness?
Sent from my Z970 using XDA Free mobile app
Will it work (root guide) with Metropcs? I just ordered one. Is metro also the same model LG-H631? I see LS770 on the web, not sure if same phone or something else. Anybody tested USB OTG with Stylo?
Seems our bootloader is unlocked on the tmob version. Just waiting for twrp. The battery life is fantastic on the device. The 720p lcd isnt the greatest but isnt the worst ive used. It definitly is bright and vibrant and contributes to the outstanding battery life. Aosp roms will fly on this thing.
fix-this! said:
Seems our bootloader is unlocked on the tmob version. Just waiting for twrp. The battery life is fantastic on the device. The 720p lcd isnt the greatest but isnt the worst ive used. It definitly is bright and vibrant and contributes to the outstanding battery life. Aosp roms will fly on this thing.
Click to expand...
Click to collapse
Does it mean Metropcs version BL is also unlocked? Metro is owned by tmob.
guest_2011 said:
Does it mean Metropcs version BL is also unlocked? Metro is owned by tmob.
Click to expand...
Click to collapse
Id say yes but i wont know for sure. If you can root like we can then its a good chance. We need a dev and our own forum section here.
Is it possible to unroot?
fix-this! said:
Id say yes but i wont know for sure. If you can root like we can then its a good chance. We need a dev and our own forum section here.
Click to expand...
Click to collapse
agree with you this phone needs his own section i'm sure will be good success from LG i have friend that have the Zmax and they are going to be getting the Stylo, we just need someone with the MetroPCS Variant to verified if is rootable the same way the T-mobile variant is.
guest_2011 said:
Is it possible to unroot?
Click to expand...
Click to collapse
the SU app have an Option to Unroot, i personally haven't try it but maybe someone else know if that works.... never had the need to unroot a phone so i have no idea about that
Greetings!
Allow me to present to you:
How to Dramatically improve your Rooted S8 Display Quality
And Eliminate the Green/Garbled Screen bug
NOTE: Some users are still experiencing the green/garbled screen issue after flashing.
However all reports of this have indicated that it is happening noticeably less frequently.
Update:
I am looking into this and will have some changes out shortly that will hopefully help. It is difficult for me to troubleshoot because I literally can not get it to happen to my phone anymore so it is difficult to verify improvements before shipping them out to you, but I am doing my best.
WHAT?!
I found the following today while digging around chinese phone firmware sites via baidu:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In case you can't tell what that is, it is a BRAND NEW "Combination" Firmware with the label AQI1. The combination firmware is a special factory image used by service workers and XDA members who want to do things like change their CSC or bypass a FRP lock. meaning its almost completely brand new! AQI1 stands for "September 2017", which means this is a brand spanking new image only a few days old!
WHO CARES?
Why is this important? Well it just so happens that the Combination firmware boot image (boot.img) is what we all flashed as part of the SamPWND root. The boot.img file contains the kernel and root filesystem ramdisk. We were running one from sometime around April, which is very old compared to the modern builds most of us flashed after rooting. Furthermore, the image we all are currently running is likely one of the first kernels rolled out for the phone, so its no wonder there was an issue like this that was not fixed (who cares if you get greenscreen in 5m of CSC update).
So all it takes is a simple flash in FlashFire of the AQI1 boot.img (provide at the bottom of this post), an operation that does NOT require a wipe of /system, /data, or anything really (although I recommend a cache wipe in recovery for good measure, but it is very likely not necessary). Your phone will just come back up with a slicker modern kernel and most of all NO MORE ANNOYING DISPLAY BUGS!!!
WHAT IT IS NOT:
Now that I have explained what this thread is about, I wanted to outline a few things it is NOT about, to make a valliant effort to stem off the flow of questions before they begin (ha!):
NOT: A new Stock ROM for Your Phone
THIS IS NOT A FULL OS BUILD! DO NOT DOWNLOAD THE WHOLE THING AND FLASH IT EXPECTING AN UPGRADED OS.
This is ONLY the special factory / Combination CSC and diagnostic ROM that has been floating around forever, just a modern build.
It is also the ONLY AQI1 image I have found. Believe me I looked a bunch of places after I found it
NOT: Oreo Early Preview
Given the predictions that the next release from Samsung would likely be Oreo, there was some initial over excitement. This wound up being NOT the case and if you read at least current Samsung Oreo projections they are predicting AQB now.
NOT: A Fix for the 80% Battery Issue
I know this is completely futile to hope for but:
THIS DOES NOT FIX THE 80% BATTERY ISSUE!!!!
NO WE DO NOT HAVE A FIX FOR THAT OR ONE COMING ANY TIME SOON!
YES SOME PEOPLE ARE STILL TRYING!
PLEASE DO NOT ASK! OFF TOPIC FOR THS THREAD
NOT: Currently Tested by ANYONE
I tested this on my S8 G950U but I don't have an s8+ to test with. I imagine that it will work the exact same way but I can't be sure. Hopefully some of you early adopters can share your results with the thread so that we can build some confidence here
NOTE: This is for the s8+ G955 US Snapdragon models ONLY! Do NOT Flash this on your exynos, your Chinese/HK S8, your N8, your MOTO RAZR flip phone, whatever else you have. Kernels/boot.img files are very device specific and you will surely break it if not completely brick it. See the other thread if you have a regular S8 US Snapdragon model.
DISCLAIMER:
YOUR WARRANTY IS ALREADY VOID if you are paying attention and are doing this to fix bugs with the existing sampwnd root.
HOWEVER IT IS EVEN VOIDER NOW. FLASH THUS TO YOUR DEVICE AT YOUR OWN RISK!
and if you break it I AM NOT RESPONSIBLE! FLASH AT YOUR OWN RISK!
As I said I have not tested this anywhere as I don't have an s8+
STEPS
Download Boot Image
Use the URL here to Download the AQI1 boot.img file: G955USQU1AQI1 BOOT.IMG
Prepare Phone for Flashing in FlashFire
If you did not download it on your phone, copy it somewhere FlashFire can see it.
Flash it
Open up FlashFire
Hit the "+" button
Select the "Flash Firmware Package" option, NOT the "Flash Zip or OTA" option!
You should see a popup window thing that has a checkbox next to the word BOOT, with "boot.img, 22MiB" underneath.
Make sure the checkbox is checked.
Make sure that it says BOOT above boot.img.
I have no idea if its possible for this to get messed up, but BOOT implies flashing the BOOT partition so if it says something else you are headed towards brick town, abort immediately.
Press the Check mark at the top right corner once you have confirmed the two things above.
MAKE SURE EVER ROOT IS DISABLED!!!
Click on the "Reboot" box, and choose "Recovery". MAKE SURE PRESERVE RECOVERY IS NOT CHECKED!
Back at the main menu, click the lightening bolt next to the word FLASH. Confirm.
Wait for FlashFire to do its thing. Sometimes it takes a minute for FF to wake up and start flashing. Occasionally for me it never happens, if this happens DO NOT PANIC ITS FINE. Hold down power+volDown until you eventually wind up in upload mode, then just reboot normally and everything will come back fine.
When FlashFire finishes (it will go really fast, the image is only 22MB we arent flashing a 5GB system here), it will auto-reboot your device into the recovery men
Select Wipe Cache and Confirm
This will wipe cache which is fine and safe. Again maybe not needed, feel free to skip if you know what you are doing. If you mess up and factory reset your device tell me so I can laugh at you.
Reboot into a Clear New World
Select reboot and boot the system normally. If you formatted the cache partition above, it will take a little longer to start your phone. This is just the first time per normal.
Thats it! Welcome to the world of clear screens and bright colors. It could be a total placebo effect but I actually think this kernel drives the display better sometimes.
Please let me know what you think, and if this works for you. I will be here for a while to answer questions or fix anything i typoed above or whatever.
FYI: There is an s8 thread in the s8 forums, if you have one of those use that method. There absolutely are binary diffs between versions so SOMETHING is different, and Id rather not have your briked phone on my concious.
SPECIAL THANKS TO:
@elliwigy and @stf_TimelessGoD and the rest of the SamPWND crew for getting us this awesome root in the first place
@elliwigy again for turning me on to the fact that this was a thing at all
@jhofseth for nerding out with me the last few nights on trying crazy **** to get a bootloader unlock which prompted me to dig at this in the first place
Most of all, the tons of you out who have made so many awesome mods, themes, apps, workarounds, tools, etc etc etc. What you have made I use every day and all of it makes me enjoy my device all the more. I could not be happier to have the opportunity to give back a little.
BONUS: Here is a link to the entire combination image if you want to take a look at the rest of it. Don't flash the rest of it if you don't know what it is, as it wipes everything and you will have to root from scratch again!
http://goo.gl/pYyg7s
@wildermjs8 thanks for digging around. If we flash this and have problems what is the best way to go back?
UPDATE: got impatient and flashed per your instructions and all seams ok so far. Shows Sept 4 kernel version in about phone. Will update later. Thanks again
This can be flashed over AQH3, right ?.
jawonder said:
This can be flashed over AQH3, right ?.
Click to expand...
Click to collapse
why not? as long as its not incremented you are good.. u could prolly even dd it if u want
Working ok for me .
mopartonyg said:
@wildermjs8 thanks for digging around. If we flash this and have problems what is the best way to go back?
UPDATE: got impatient and flashed per your instructions and all seams ok so far. Shows Sept 4 kernel version in about phone. Will update later. Thanks again
Click to expand...
Click to collapse
Good idea I will post a rollback tar in case anyone has issues
All seems to be working well, if not, things are more fluid for me. No green screen yet either. Thanks, will continue to report in.
Glad to hear it's working out!
I thought the screen looked better too but I thought it was likely I was seeing things lol
The green screen came back. But it took like a dozen or more reboots before it appeared. Sprint s8+ on QGL.
Great job @wildermjs8 - thanks for the upload ?????
patmorris said:
The green screen came back. But it took like a dozen or more reboots before it appeared. Sprint s8+ on QGL.
Click to expand...
Click to collapse
sounds like it minimized it at least for u lol.. i dont think there will be a true "100%" fix until we can be rooted on a stock boot.img
elliwigy said:
sounds like it minimized it at least for u lol.. i dont think there will be a true "100%" fix until we can be rooted on a stock boot.img
Click to expand...
Click to collapse
I'm perfectly content. It's definitely much better than it was.
Thanks for this. I have not had the chance to install yet, too late if in the event a problem arises. I don't like to do "10 sec fix" unless I have extra time jut to be safe. But I'll try tomorrow.
This is the wrong thread but root has been pretty good with the exception of excessive battery drain. Maybe just me so ymmv.
Many thanks for this and the files
Sent from my SM-G955U1 using Tapatalk
Araltd said:
Thanks for this. I have not had the chance to install yet, too late if in the event a problem arises. I don't like to do "10 sec fix" unless I have extra time jut to be safe. But I'll try tomorrow.
This is the wrong thread but root has been pretty good with the exception of excessive battery drain. Maybe just me so ymmv.
Many thanks for this and the files
Sent from my SM-G955U1 using Tapatalk
Click to expand...
Click to collapse
Nice to see ya over here! Far cry from the s7 edge root that's for sure!
How bad is the battery drain? While using or while sleeping? These phones even stock don't sleep well, I'd say they lose on average a percentage an hour, which is sad really lol
It's early days with new firmware so we will see
Quickvic30 said:
Nice to see ya over here! Far cry from the s7 edge root that's for sure!
How bad is the battery drain? While using or while sleeping? These phones even stock don't sleep well, I'd say they lose on average a percentage an hour, which is sad really lol
Click to expand...
Click to collapse
I'm late to the s8+ literally just bought a used one (they made me a deal I couldn't refuse).
I'm losing about +3%/hr while screen off... Screen On is another story... Obviously depends on the activity - but battery drain is high in my opinion and as you know @Quickvic30 I'm NEW to all this still learning what the green button does when the phone makes noise and I see a phone number on the screen.
But the rooting method is still young and improvements and tweaks are already coming LIKE THIS THREAD.
Sent from my SM-G955U1 using Tapatalk
Araltd said:
I'm late to the s8+ literally just bought a used one (they made me a deal I couldn't refuse).
I'm losing about +3%/hr while screen off... Screen On is another story... Obviously depends on the activity - but battery drain is high in my opinion and as you know @Quickvic30 I'm NEW to all this still learning what the green button does when the phone makes noise and I see a phone number on the screen.
But the rooting method is still young and improvements and tweaks are already coming LIKE THIS THREAD.
Click to expand...
Click to collapse
i wouldnt say its a fix lol some still have issues.. although it minimizes it so far, all this thread is about is flashing a newer official combo boot.img lol
a "fix" i would say would be finding a way to manipulate the phone to use a stock boot.img while maintaining root..
basically we are still on a factory binary boot.img which means its not fixed and unstable for daily use (it even says this within the logs lol) this type of boot.img isnt supposed to be a daily so regardless of how new it is, its still bound to have some issues at some point
elliwigy said:
i wouldnt say its a fix lol some still have issues.. although it minimizes it so far, all this thread is about is flashing a newer official combo boot.img lol
a "fix" i would say would be finding a way to manipulate the phone to use a stock boot.img while maintaining root..
basically we are still on a factory binary boot.img which means its not fixed and unstable for daily use (it even says this within the logs lol) this type of boot.img isnt supposed to be a daily so regardless of how new it is, its still bound to have some issues at some point
Click to expand...
Click to collapse
That would be better yes but if a later kernel fixes it in the combo build that is a fix for this issue lol
Given the fact that many have reported no issues I wonder if a match between kernel and some other firmware fixes it. It could be that those affected are on older versions than me.
Hmm
wildermjs8 said:
That would be better yes but if a later kernel fixes it in the combo build that is a fix for this issue lol
Given the fact that many have reported no issues I wonder if a match between kernel and some other firmware fixes it. It could be that those affected are on older versions than me.
Hmm
Click to expand...
Click to collapse
u are not understanding my point, a debug kernel is a debug kernel.. they arent meant for daily use so ppl are bound to have issues and it will mot function the same as a regular stock kernel
i have experienced the screen issue at least twice since last night and at least one other person said he still gets it also...
also not trying to be rude but a fix would be a way to use stock boot.img to get away from debug boot as much as possible.. that will actually require development to be done.. u basically just created a development thread by copy pasting a link to the latest combo firmware, these posts typically go in the general section since u didnt develop the combo, its a stock factory binary firmware
now if you somehow modified it and got it to boot then that would be development lol then again if that were the case we wouldnt be where we are today
elliwigy said:
u are not understanding my point, a debug kernel is a debug kernel.. they arent meant for daily use so ppl are bound to have issues and it will mot function the same as a regular stock kernel
i have experienced the screen issue at least twice since last night and at least one other person said he still gets it also...
also not trying to be rude but a fix would be a way to use stock boot.img to get away from debug boot as much as possible.. that will actually require development to be done.. u basically just created a development thread by copy pasting a link to the latest combo firmware, these posts typically go in the general section since u didnt develop the combo, its a stock factory binary firmware
now if you somehow modified it and got it to boot then that would be development lol then again if that were the case we wouldnt be where we are today
Click to expand...
Click to collapse
Except that isn't always the case. Having run pre-release engineering kernels from cupcake-marshmellow I have a little experience in this area, and outside of VERY early days G/Nexus/Pixel never exhibited a problem like this so I find it a bit surprising.
Forgive me for putting the thread in the wrong place, I guess I deserved that for trying putting related things together. Why does it feel like I'm being dragged into a pissing contest?
I was just trying to help people out, maybe I just shouldnt bother.
Mods can move the threads wherever it doesn't matter to me.