Related
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
First go here and download the RUU:
http://www.pcdphones.com/downloads/Eris%20MR1.zip
Next you need to go to verizon's website and login to your account. Click "Suspend/Resume Service" and suspend your phone. You can resume service on the phone after you are done here with no penalties or charges.
Please follow these directions, taken from the first root thread
bftb0 said:
Steps:
[Binny knows this, but if anyone else is reading, it is the same as a factory reset - you will lose all your settings and apps (but not the contents of the SD card)]
1) Unpack the 1.16.605 RUU - by running it as if you were going to actually do the RUU using the USB cable and your host PC, but stop right before you would apply the update to the phone. Pull the "rom.zip" file out of the temporary area that the RUU installer unpacks.
(Poke around under C:\Documents and Settings\<Username>\??? (I can't remember - you'll see folders with names that look like registry entries). You have to do this while the RUU installer is sitting there waiting for you - if you cancel the install, it will nuke everything it unpacked. I just made copies of the entire subtrees.
2) Cancel the RUU install.
3) Move the ROM.ZIP file to the root folder of your SD card, and rename it PB00IMG.ZIP
4) You can cancel the RUU install session on the PC, and unplug the USB cable if you want (so long as you have a well-charged battery!)
3) Power down the phone, and boot it back up holding the Call and End buttons simultaneously
4) Scroll down (or whatever it asks) to go from Fastboot mode to HBOOT mode
5) The phone will automatically discover the PB00IMG.ZIP file, and unpack it and verify it.
6) It will ask you if you want to install; when you (select and) enter Yes, the phone will reboot, and come up again - appearing as if it is repeating the same thing. This time, however, it won't stop and ask you - it will just begin the install.
7) Wait... Wait... Wait... Wait... and then wait some more. If I recall correctly, it seems to hang a little bit at the HTC splash screen after the reboot. That is normal - just WAIT and let the phone do it's thing.
That's it, except for:
8) You probably will want to dial *228 and choose option 1 to complete the programming of your phone - it will reboot after it completes.
Click to expand...
Click to collapse
After you are done, DO NOT start the OTA update that it prompts you to do.
Now we are going to install wireshark and setup the capture environment:
Download wireshark from http://www.wireshark.org/download.html for your versions of windows
Install it - make sure you also install WinPcap
At this point you should turn off any wireless encryption on your router. I know it's not necessary but it makes it easier to go through the captures.
Setup the wireless on your phone to connect to your wireless router and turn off your mobile data connection.
After you have turned off the wireless security on your router, we are going to start the wireshark capture.
Run wireshark - if you are on vista or windows 7 make sure to run it as an administrator
Click "Capture" then "Interfaces"
Click "options" next to the interface that your computer has an IP for
Make sure to check "Capture packets in promiscuous mode"
In the Capture Filter box, type "host <ip_address>" where <ip_address> is the ip address your router gave your phone
Make sure that "Automatic scrolling in live capture" is checked so you can ensure the capture is working
Click "Start"
At this point, you should browse the web with your phone. You should see lots of stuff scrolling by in the wireshark window.
If there isn't, you messed up something above and should try again.
If there is a lot of stuff scrolling by, continue:
Close the browser
In wireshark, click "Capture" then "Restart"
Reboot your phone
On your phone, go to "Settings" -> "About Phone" -> "Check for Updates" and go through with the OTA update
After the update is done and your phone is rebooted, go to wireshark and click "Capture" -> "Stop"
Then click "File" -> "Save As" and give it a name.
Upload that file to Megaupload, or Mediafire, or some other file sharing site, or any private server that I can get access to.
After you have uploaded the file please message me through the forums with a link to the file.
Thanks a ton.
e-mail me at [email protected] i got my wifes phones todo this to shes still on 1.5
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
FireSokar said:
NO need to have a average user do this, guinea pig yourself and roll back down to 1.5 it can and has been done by other devs.
Click to expand...
Click to collapse
You CANNOT downgrade from 2.1 to 1.5.
Videofolife13 said:
Isn't there a "logcat" line you can run through adb to get the same thing? Like, when the update is available, you can plug your phone into your computer, connect it to terminal using adb and run a logcat to find the address of the update.zip
Click to expand...
Click to collapse
We don't need the location of the update file, we need all the extra network traffic that surrounds the OTA process.
Ah. My bad.
We need to know, exactly, how the update process works.
I'm currently working on downgrading 2.1. Will post back a tut if i get it working
Can't we create an AVD to run with a custom rom and use the Eris MR1 ROM to do it?
Scratch that. I don't think AVDs will get OTAs.
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Sadly I tried this a while ago when messing around with AVD Skins but wasn't able to figure it out. If anyone can figure it out please let me know how you do it! -_-"
zifnab06 said:
Scratch that. I don't think AVDs will get OTAs.
Click to expand...
Click to collapse
Wait can't you set it to wireless only mode and get the OTA through wireless? (Simulated by your network connection)
nindoja said:
This is a call to arms for anyone still running 1.5 on their eris. We (developers) need people to capture the update process using wireshark (or an equivalent). This is needed for a new root attempt, but sadly all of the devs have already updated to 2.1 so we can't do this.
...
Thanks a ton.
Click to expand...
Click to collapse
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
FYI,
When you roll back to MR1, the phone seems to have already grabbed and downloaded the OTA update... in less time than it takes to hand-configure the phone. If you want to observe the OTA process via wireless, you need to prevent the phone from having Mobile network access, since that comes up by default after a FR or MRx rom burn.
Here's a long shot. Perform the MR1 rollback inside a cell dead zone, and conduct a MIM attack by setting up a server on the wireless net so the phone downloads a different OTA zip. You control DHCP for WiFi, so you also in principle control the DNS and routing the phone sees via WiFi. In principle, it's not possible because https should prevent Man-In-the-Middle... but if that (Google) server isn't correctly configured, maybe the phone is not really being too careful about certificate problems. (Either that or the Google server is tuning its' responses based on UA strings).
bftb0
bftb0 said:
No need to go to all that trouble. I've already posted a link to the OTA update (1.16.605.1 -> 1.17.605.1) in this XDA thread a couple of days ago. Just copy n' paste into your browser's URL bar. I'll repeat it here for grins.
https://android.clients.google.com/updates/partner/desirec-ota-104882.7b1e5cca.zip
(You might get a browser security warning as that server uses the wrong (google.com) cert.)
Let me know if the above link no longer works - I suppose I could repeat the OTA thing - I am not on 2.1
The OTA process drops the downloaded zip file into /cache, and somehow during reboot, it's presence is detected. If it "only" needs to be dropped in there, or there are some other hooks that need to be present at the reboot, I am not sure. I say "only" because that implies that root privilege is needed to do that - or perhaps it is possible to use "fastboot update" after rebooting the phone with $ adb '(sync; reboot -n oem-78)' The OTA zip file is not signed the way the RUU "rom.zip" files are; it uses the same signing methods as app (.apk) files - the SDK "jarsigner" method.
You can unpack the zip file and look at what it does - there is a script at
META-INF/com/google/android/update-script
which controls the update... and there is a binary patch executable included in zip which is called upon to do file-by-file binary patching.
cheers
bftb0
Click to expand...
Click to collapse
bftb06: could you please PM me? I am going to trade my phone this week if you understand what I am getting at.
nindoja said:
Thanks for the info bftb0, but we aren't looking to snag the OTA file. We are actually trying to see what communication goes on between our phones and the verizon update servers.
Click to expand...
Click to collapse
Sorry, my bad. I didn't read carefully enough.
I could probably attempt what you are asking for - I am quite familiar with wireshark (and even hardware sniffing of WiFi, so long as you have the right nic), but the fact that the phone seems to go and look for updates immediately after a FR or MRx update means that the "check for updates" thing may not do anything useful for you if there is already an update on the phone waiting to be installed by the time you start pressing menu buttons. (Thus the idea about "do MR1 in a cell dead zone")
Beyond that, there is a possibility that the update app does not do a wildcard host bind() when it sets up the socket when it inquires about updates with the Verizon servers - for instance, MMS service works exactly that way (it will only use the mobile network interface), and precisely so because of security considerations. Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
bftb0 said:
Do you know whether or not any of the update conversation actually traverses WiFi if the mobile network is turned off?
bftb0
Click to expand...
Click to collapse
You can force updates to occur over WiFi if the mobile network is turned off. Do you think this would work:
1. on 1.17 do a factory reset but do not activate the phone.
2. Initiate the downgrade process
2a. while downgrading, turn on packet capture
3. When the phone boots back up and wants you to call a number to activate, hang up
I think if you can skip the activation the phone will not have a mobile data connection, which would allow you to turn on wifi and initiate the update process.
Im still on 1.5 PM me and ill help if needed
Do you guys still need this?
TGA_Gunnman created a one click root that new users will want to use, said thread is a sticky in Captivate Development. If you still want to use the old method (and install ADB) please use this one.
I followed my own guide! This works perfectly if you read everything and follow the instructions.
Also: once you are rooted, be EXTREMELY careful! Half of the new threads are people who have screwed up their phones by deleting this or corrupting that. Please, for the sanity of all of the devs and Android veterans, make backups and just be all around careful. Almost all problems that anyone has had are repareable AND PREVENTABLE with a little reading and care. Just to clarify, rooting does not automatically enable sideloading. Please follow http://forum.xda-developers.com/showthread.php?t=738376 to enable sideloading.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way. Your warranty is also void, but you could have figured that out for yourself.
Now that that's over with, lets get to the fun bit. If you are on Windows, you can follow this procedure, or for TGA_Gunnman's one click root program (only on Windows), you can go ahead and skip to the bottom.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/s...iver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. (If you are on a Mac, DO NOT USE SAFARI to download the file, it automatically unzips any zip file. Use Google Chrome or firefox instead.) Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) EDIT--There is an easier way to get to recovery, but do this step anyway. Turn the phone off, then hold power, volume up and volume down. If you still want the android SDK (which will be very useful throughout your rooted experiences) follow the old procedure:
This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
Click to expand...
Click to collapse
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Can we please have more detailed instructions? I don't understand the part where it says "type in the terminal"
I am very new to android as this will be my first Android phone.
Also, after rooting will we be able to install 3rd party applications? Or do we have to do anything else to bypass ATT's restrictions?
adb terminal is software you need to install on your PC , will probably need samsung drivers also , guide is indeed not noob friendly. This will help you get needed bits including ADB
Probably None of us have captivate , so writing a guide is a bit troublesome
Ditto, a guide to the adb terminal please! I will acquire this phone, this Sunday.
Actually, you'd have to install a custom ROM for that. MoDaCo should be coming out with them pretty soon, and so will XDA. It won't be too long. BTW, once you have ADB installed on your computer, you can sideload apps all you want. The command is
Code:
adb install /directory/of/app/on/computer
point me to some functioning samsung drivers and I can do this!
If you cant get it to work on windows, try a ubuntu live cd. All you need to do is go to ubuntu and burn a disc and reboot.
Are there no Windows 64 bit drivers?
Edit- I found some that work. I think. Haven't tried it (yet).
http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Edit 2- Just did the root. Seems to have worked (no errors) but how do I know if it did? How do I delete say, ATT Maps?
Thanks for this. I am new to smartphones and plan on purchasing the Samsung Galaxy-S, but don't want to mess it up. I am new to editing the OS of any smartphone, but I think if I have a tutorial I will be fine
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
NOSintake said:
For Mac and Linux you put a ./ in front of the adb correct? (./adb install...)
Click to expand...
Click to collapse
if you are in the directory above yes. the ./ just saves you from writing out the full path
lets say adb is in "/home/user/Downloads/sdk/tools"
you could type out "/home/user/Downloads/sdk/tools/adb command" regardless of where your terminal window was focused
or if you were currently in the directory "/home/user/Downloads/sdk/tools"
you could use the shortcut "./adb command"
OP I'd change your post based on my experiences... Here's a little more detail and I've rearranged it (you need the drivers before running these commands, for example).
blackjackboy said:
Please let me know if this rooting method works as I have no Captivate to test on. I'm not taking any credit for any of these files, LeshaK made the original file to root the European Galaxy S, Justadude modified it for the T-Mobile Vibrant and chaoscentral edited the file for use on the Captivate.
Follow these steps exactly and there will be no risk of bricking your Captivate, the worst that may happen is the phone rejecting the update.zip.
HOWEVER:
I take no responsibility if ANYTHING at all happens to your device that you don't like. Don't come crying to me if your brand new phone breaks in any way.
Now that that's over with, lets get to the fun bit.
1) You may need Samsung drivers if you are on a PC, which you can learn about here: ADB Drivers at the Unlockr
For 64 bit Windows, you'll need these drivers: http://zedomax.com/blog/2010/07/14/...ic-4g-and-fascinate-galaxy-s-driver-download/
Don't proceed until your phone is fully installed on Windows with the drivers!
2) Download the attached zip (at the bottom of the post) and rename it to update or update.zip if you are on a Mac. Scroll down the notification bar and click "mount" to allow your computer to read the internal memory. Put the file on the INTERNAL SD card of the Captivate, which won't be tough to figure out if you don't have an SD card in the phone.
3) This step requires the Android SDK, and Android Debugging enabled. You can get the SDK here: Android SDK. Just download the zip, extract it to something like C:\Android. You won't need the Java dev pack or anything.
You can enable Android Debugging like this: From the homescreen, press Menu, then click Settings. Navigate to Applications>Development and check USB Debugging. Now, hook the phone to the computer. Next,
On a PC, click start>run>"cmd" (in the text box) or on a Mac, spotlight "Terminal". Linux users, you know what to do.
The command you will use is in the tools folder of wherever you extracted it to (IE: C:\android\tools), so be sure your working directory of command prompt is in that tools location!
Finally, type:
Code:
adb reboot recovery
4) Once the phone is booted into recovery, use the volume keys on the phone to scroll to "Reinstall packages." Use power to select what you have highlighted.
5) Give yourself a pat on the back. You are now rooted. You should see a Superuser application now.
Thank you to LeshaK, Justadude, and chaoscentral. Once again, I didn't discover how to root, that credit goes to LeshaK, bringing it over to the USA was Justadude's doing, and chaoscentral edited the file for use on our Captivates.
MD5 Sum: 1eb65923281c113e8751a7d8a6faff43
Click to expand...
Click to collapse
Ubuntu 10.04 - adb
Any step by step instructions just to get adb running enough on 10.04 to root and side load software? I'm getting command not found when I try to run adb, even after downloading packages.
Hi,
Did this thread worked well to Root the Captivate or anyother suggested link? I'll appreciate any help.
Thanks
rerooting captivate
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Thanks for the answer & More Queston
cellgeek said:
This worked perfectly on my Captivate. I now have the SuperUser Permission on my application screen. Now I can REALLY screw up my Captivate!!!
Click to expand...
Click to collapse
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Muhamadabdelaall said:
Hi,
Thanks for your helpful answer. As I'm getting my Cativate tomorrow, can you please just answer yes or no to each of my questions as follow ?
After Rooting will I be able to:
1- download any 3rd party Android application?
2- install any "Samsung Galaxy S" ROM on my Captivate?
3- Recieve any "OTA" update as a "Galaxy S" phone?
Thanks again
Click to expand...
Click to collapse
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Thanks Drachen
Drachen said:
1. No. You will have to use adb or the database modification method (which having root access makes possible). Both are described in detail elsewhere in this forum.
2. Rooting means simply getting superuser permissions. Loading a ROM has to do with the bootloader and recovery partition. Unmodded Galaxy S ROMs probably will not work on the Captivate, but be patient.
3. Not sure what you're asking. You will still get any Captivate OTA updates as if you hadn't rooted, but you won't get, for example, the rumored Korean FroYo Galaxy S update OTA when it drops. You'd have to wait for the Captivate OTA FroYo upgrade (or there may be a ROM or patch you can flash by then).
Rooting is basically just allowing programs to run as the superuser account. Many programs like Metamorph, some screenshot apps and some wifi tethering apps require more permission than Android normally gives an app.
Click to expand...
Click to collapse
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Muhamadabdelaall said:
Thanks alot for taking all this time & energy to reply to me! WOW, it seems like everytime I wanna step up one, I go back 10 steps. All I need is to use my Captivate for installing a Stock Rom of "Galaxy S" & be able to get rid of any "AT&T" restrictions for anything on this phone, what should I do please?
Thanks
Click to expand...
Click to collapse
The ATT stuff doesn't actually run so they aren't a big deal at this point. I also don't see Amazon MP3 background stuff like some Android devices have, so... There's really not a huge case for rooting yet.
That said, when Custom ROMs for this come out I'll still be getting one.
For those of you having a hard time installing ADB Shell, try this video. It worked for me.
http://www.youtube.com/watch?v=YeWH6Bj1DYw&feature=related
i was looking around on ebay and noticed this
http://cgi.ebay.com/HTC-EVO-ENABLE-...ell_Phones&hash=item2a09ba8398#ht_1734wt_1137
Most likely hev will sell you instructions which you can pr
op find online for free
Sent from my SAMSUNG-SGH-I897 using XDA App
Probably just android wifi tether, which is free in the first place. Or, is there a hacked version of the sprint app out there somewhere?
Hrshycro said:
Probably just android wifi tether, which is free in the first place. Or, is there a hacked version of the sprint app out there somewhere?
Click to expand...
Click to collapse
Doubt an ebayer has a hacked version of the Sprint app, but he does say that this doesn't void your warranty (unless he thinks that rooting doesn't void warranties.)
Doesn't work on Froyo. My money is on a hacked version of the Sprint app.
Tempting to spend the $5. If it involves root, you can get your money back since it is false advertising.
I sent him a piece of my opinion.
mattrb said:
I sent him a piece of my opinion.
Click to expand...
Click to collapse
LOL what'd ya say?
Sent from my PC36100 using XDA App
hes probably sending out instructions on unrevoked and android tether, which you can get on youtube for free
I reported him for selling someone else's intellectual property, since I highly doubt he actually wrote that app, and if it doens't involve hacking the only instructions he could include are "put on SD card and run."
Well .. my opinion...not that it matters..
You will see stuff like this all the time. He isnt selling the software, only instructions on how to do it. I really don't see anything wrong with that. People buy instructions on how to do things all the time. There really isn't anything wrong with that. If someone is too lazy to reseach it and figure it out themselves, oh well. That's the great thing about America. Everyone has a hustle, nobody is forcing anyone to buy it. Maybe it is some college kid scraping to get along, maybe not. Either way, no harm no foul. You don't like it, don't buy it...
Now if he was selling the free software, thats a different ballgame.
I don't see how reporting him for selling someone elses stuff is cool... he's selling instructions. Whoopie.
Agreed. It's no different than someone accepting payment when someone asks for help on this forum and offers to pay someone via Paypal. I occasionally see threads like that around.
Sent from my PC36100 using XDA App
apristel said:
Well .. my opinion...not that it matters..
You will see stuff like this all the time. He isnt selling the software, only instructions on how to do it. I really don't see anything wrong with that. People buy instructions on how to do things all the time. There really isn't anything wrong with that. If someone is too lazy to reseach it and figure it out themselves, oh well. That's the great thing about America. Everyone has a hustle, nobody is forcing anyone to buy it. Maybe it is some college kid scraping to get along, maybe not. Either way, no harm no foul. You don't like it, don't buy it...
Now if he was selling the free software, thats a different ballgame.
I don't see how reporting him for selling someone elses stuff is cool... he's selling instructions. Whoopie.
Click to expand...
Click to collapse
agreed. 100%
TheBiles said:
I reported him for selling someone else's intellectual property, since I highly doubt he actually wrote that app, and if it doens't involve hacking the only instructions he could include are "put on SD card and run."
Click to expand...
Click to collapse
that's pretty lame when you are only assuming. for all you know he knows a data code that unlocks it. before you go run and tell mommy why don't you put up the 5 bucks and see what he is ACTUALLY selling?
nicholaaaas said:
that's pretty lame when you are only assuming. for all you know he knows a data code that unlocks it. before you go run and tell mommy why don't you put up the 5 bucks and see what he is ACTUALLY selling?
Click to expand...
Click to collapse
+1 for that!
I just purchased...will let you know what I get for my $5.00
since your throwing money out in the street,
i have a neat way to allow you to copy your legally purchased music direct to your SD card.
will not void your warranty and i can send the instructions immediately upon payment!
this works on 2.1 and 2.2. you can be rooted or stock.
for you ill sell it for $4.98 US dollars. PM me for paypal info..
marctronixx said:
since your throwing money out in the street,
i have a neat way to allow you to copy your legally purchased music direct to your SD card.
will not void your warranty and i can send the instructions immediately upon payment!
this works on 2.1 and 2.2. you can be rooted or stock.
for you ill sell it for $4.98 US dollars. PM me for paypal info..
Click to expand...
Click to collapse
$4.98 seems a little steep...I will give ya $2.36
On a more serious note, I am just too curious to find out what he is selling and I think others are also. If I have to pay $5.00 to find out what he is selling, so be it. I spend more than that a day giving to homeless people on the street.
Instructions sent to me:
Video here :
http://www.youtube.com/watch?v=uoSBZgqkKME&feature=player_embedded#!
FOR EVO OWNERS DO NOT DO ANY UPDATES JUST YET THIS WILL ONLY WORK WITH THE 1.47 SOFTWARE VERSION.
ALRIGHT HERE THEY ARE, I HAVE INCLUDED 3 DIFFERENT SETS OF INSTRUCTIONS. PLEASE READ ALL OF THEM TO GET A FEEL FOR WHAT YOUR DOING SOME GO INTO MORE DETAIL THAN OTHERS BUT THEY ALL GET YOU TO DO THE SAME THING. RIGHT BELOW IS HOW YOU GET THE WIFI TETHER APP WHICH IS SOMETHING THAT YOU WILL HAVE TO DO AS WELL. BUT JUST READ AND FOLLOW STEP BY STEP.
****RIGHT BELOW IS HOW YOU GET THE ACTUAL WIFI TETHER APP****
1. Now go back to you internet browser on your phone and pull up google.
2. Type in "android wifi tether" and click search.
3. The first option that comes up after the search called "android wifi tether - Project Hosting..."
4. Select the first option and let it take you to the web site.
5. Now the page will pull up and look for where it says "HTC Evo" under device and just to the right of that
you will see a link that says "download" click download.
6. Now click the link that says "wireless tether for root users 2.0.2.apk.
7. Click on "wireless tether for root users 2.0.2.apk" again.
8. Now click "wireless_tether_2_0_5-pre2.apk" and let it install.
******First set of Instructions******
(1) If you have the original unrevoked root installed, uninstall it by using "Menu," "Settings," "Applications," "Manage Applications" and scrolling to "Unrevoked" at the bottom. Tap it, click "Force Stop" at the bottom and then "Uninstall," "OK" to uninstall it. Then power off/on your phone just to be sure.
(2) If you haven't already installed the OTA 1.47 update, do it now: "Menu," "Settings," "System Updates," and "HTC software update" at the bottom, then click "Check Now" to get the 1.47 update. If you do this update, it takes up to 10 minutes so be patient and let the phone reboot (a few times) until it is done. Then once the update is done, power off/on one last time to get a clean start.
(3) Set your phone to "Charge Only:" "Menu," "Settings," "Connect to PC," tap "Default connection type" and select "Charge Only."
(4) Enable USB debugging: "Menu," "Settings," "Applications," "Development," and put a check in "USB debugging."
The process: DOWNLOAD THE REFLASH PACKAGE FROM http://unrevoked.com/recovery/ NO MATTER WHAT!
(1) Download the unrevoked3 install package: Go to unrevoked3 recovery reflash tool, v3.0 and click "Download for Windows." Save the "Reflash-bundle.exe" file somewhere that you can find it on your system.
(2) Using Explorer, run the "Reflash-bundle.exe" file you just downloaded. It'll ask where to install it. Don't just accept the default: change the install location to a folder you can remember: it's just going to unzip some files there: it isn't really a software installer.
(3) Once the files have unzipped, go to the folder you chose in the above step. You should find an "hboot driver.htm" file in that folder: double click on that to open the html instructions on how to install the drivers. Follow the instructions in the html file starting with downloading the actual driver files at the very top. When you download those driver files and unzip those, those are the files (the folder) you'll point to in subsequent steps in those instructions. When done with the html instructions, you should have drivers installed and shouldn't have to come back to this step.
(4) At this point, if you needed to install the drivers, you are probably still sitting at a boot menu on your phone. UNPLUG the phone from USB and select "Fastboot" and then "Reboot" to reboot the phone to restart it. Before the next step, your phone should be on and booted up in its normal operating state (not some boot menu).
(5) Now go to the folder where you unzipped the reflash bundle (step 2 above). Just double click the "Reflash.exe" file.
(6) You should get a window with "Unrevoked 3" on it (on the computer of course). Just follow the instructions in smaller font below "Unrevoked 3" to finish rooting. Note that when it says "Waiting for device," it wants you to plug your EVO into the computer via the USB cable. Note that it wants the EVO to be fully booted normally (not in the Hboot or recovery menus). The prompts at this point are very specific so no need to repeat them. If all works as it is supposed to, the only thing you really have to do is scroll to an item on the phone and select it when instructed. The rest is automated and should result in a "Done" message. The whole thing at this point took maybe one minute so it isn't something you have to wait for or stare at for a long time.
*****Second set of Instructions*****
All the instructions I've found for using unrevoked3 to root an Evo on a Windows PC seem to be piecemeal (all over the place and incomplete), so I thought I'd give a rundown of what worked for me. Some of these steps may be unnecessary but doing all of them should result in a "safe" root. This is written for those with little to no knowledge of rooting but with basic Windows/PC skills and knowledge of how to navigate the Evo interface:
Prep
Before beginning the process, I would recommend doing the following to your phone:
(1) If you have the original unrevoked root installed, uninstall it by using "Menu", "Settings", "Applications", "Manage Applications" and scrolling to "Unrevoked" at the bottom. Tap it, click "Force Stop" at the bottom and then "Uninstall", "OK" to uninstall it. Then power off/on your phone just to be sure.
(2) If you haven't already installed the OTA 1.47 update, do it now: "Menu", "Settings", "System Updates", and "HTC software update" at the bottom, then click "Check Now" to get the 1.47 update. If you do this update, it takes up to 10 minutes so be patient and let the phone reboot (a few times) until it is done. Then once the update is done, power off/on one last time to get a clean start.
(3) Set your phone to "Charge Only": "Menu", "Settings", "Connect to PC", tap "Default connection type" and select "Charge Only".
(4) Enable USB debugging: "Menu", "Settings", "Applications", "Development", and put a check in "USB debugging".
The root process
(1) Go to Control Panel on your system and uninstall any "HTC" software such as "HTC Sync".
(2) Download the unrevoked3 install package: Go to
unrevoked3 recovery reflash tool, v3.0 and click "Download for Windows". Save the "Reflash-bundle.exe" file somewhere that you can find it on your system.
(3) Using Explorer, run the "Reflash-bundle.exe" file you just downloaded. It'll ask where to install it. Don't just accept the default: change the install location to a folder you can remember: it's just going to unzip some files there: it isn't really a software installer.
(4) Once the files have unzipped, go to the folder you chose in the above step. You should find an "hboot driver.htm" file in that folder: double click on that to open the html instructions on how to install the drivers. Follow the instructions in the html file starting with downloading the actual driver files at the very top. When you download those driver files and unzip those, those are the files (the folder) you'll point to in subsequent steps in those instructions. When done with the html instructions, you should have drivers installed and shouldn't have to come back to this step.
(5) At this point, if you needed to install the drivers, you are probably still sitting at a boot menu on your phone. UNPLUG the phone from USB and select "Fastboot" and then "Reboot" to reboot the phone to restart it. Before the next step, your phone should be on and booted up in its normal operating state (not some boot menu).
(6) If you are running anti-virus software, turn it OFF or disable it now.
(7) Now go to the folder where you unzipped the reflash bundle (step 3 above). In XP or older systems, just double click the "Reflash.exe" file. On Vista and Win7 systems, I'd recommend right clicking on "Reflash.exe" and selecting "Run as Administrator". While this may not be necessary, I know that some USB drivers get really mad if you try to access the USB port without admin privileges (sorry, I'm a coder so I run into that stuff and warn you so you don't have to) so I did it as a precaution.
(8) You should get a window with "Unrevoked 3" on it (on the computer of course). Just follow the instructions in smaller font below "Unrevoked 3" to finish rooting. Note that when it says "Waiting for device", it wants you to plug your Evo into the computer via the USB cable. Note that it wants the Evo to be fully booted normally (not in the Hboot or recovery menus). The prompts at this point are very specific so no need to repeat them. If all works as it is supposed to, the only thing you really have to do is scroll to an item on the phone and select it when instructed. The rest is automated and should result in a "Done" message. The whole thing at this point took maybe one minute so it isn't something you have to wait for or stare at for a long time so if something gets "stuck" for a while... there's likely a problem.
(9) Don't forget to turn your anti-virus software back ON.
Now, when I followed these steps on my Win7 x64 system, reflash.exe detected the phone and started working (we're in step 8 here) but about 4 messages into the process I got the "communications lost... try again" message that unrevoked refers to on today's Twitter. Some say that (contrary to step 1) installing HTC sync actually solves the problem. I didn't try that. After about 6 tries on my Win7 system and even pulling some "tricks" to try to pause reflash.exe at certain points, I gave up and simply booted my old XP laptop and repeated the above steps and it worked perfectly the first time. At the point of the failure, you hear the two tone usb-device-disconnected sound followed by a use-device-connected sound about 20 seconds later. Somewhere in between is where the "communications lost" message appears so it looks like some sort of USB ack/nack issue. Hopefully it'll be resolved soon. My best advice if you get that error: try a new machine. The XP machine that worked perfectly for me had never seen any HTC software. Maybe that helped. And maybe after I uninstalled the HTC software on my Win7 x64 system (the one that didn't work) I should have rebooted before continuing: I didn't because it didn't prompt for a restart and I couldn't find anything "HTC" running in task manager.
****Third set of instructions****
http://www.androidpolice.com/2010/0...tc-droid-incredible-explanation-instructions/
*******READ BELOW FIRST BEFORE GOING TO WEB SITE ABOVE********
Alright here is the web site that you need to follow. First of all make sure you have USB DEBUGGING checked on you phone and UNKNOWN SOURCES is checked as well.
To do this go to Settings-->Applications--> check UNKNOWN SOURCES, then right below that click development and check USB DEBUGGING.
Now this is just as important you HAVE to uninstall any program that automatically comes up when you plug in your android phone (HTC Sync, DoubleTwist or any other program). If you do not do this it will not work. Trust me it took me 3 hours to figure this out but once i uninstalled these two programs it worked the first time. So if you follow all of the directions on the web site it will work without a hitch.
Go ahead and go to the web site and read it over one good time without doing anything JUST READ IT! When you do that come back and read the rest.......Go on read it but just read it don't do anything else till you read the rest of this email
You will need to do the steps below to get the app for wireless tether so you can do it before or after you install the directions from the web site above.
1. Now go back to you internet browser on your phone and pull up google.
2. Type in "android wifi tether" and click search.
3. The first option that comes up after the search called "android wifi tether - Project Hosting..."
4. Select the first option and let it take you to the web site.
5. Now the page will pull up and look for where it says "HTC Evo" under device and just to the right of that
you will see a link that says "download" click download.
6. Now click the link that says "wireless tether for root users 2.0.2.apk.
7. Click on "wireless tether for root users 2.0.2.apk" again.
8. Now click "wireless_tether_2_0_5-pre2.apk" and let it install.
Those are the instructions for the actual app that will turn on the tethering.
When you go to the web site above you will need to follow the steps from where it says "instructions"
First download the software fromunrevoked.com for your hero or evo to your computers desktop, then make a new folder on your desktop and put the app that you downloaded from unrevoked.com and put it in there because that is where all of the files will extract too when you run the unrevoked program.
Second you will need to install the drivers, on the web site click on the install drivers hyper link and it will take you to the web site to download the drivers again just make a new folder on your desktop and extract the files into it, it is very simple if you just take it slow and follow the directions.
After you install the drivers you will run the reflash package inside the folder that you made on your desktop when you do that it will extract the files and you will finally run the application on your computer called ReFlash. Try plugging your phone in first and then running the program or vise versa. Let the app do its thing and follow instructions on the programs screen. When it finally says Done your phone will be on a screen that you have never seen before but you will want to click on the first option with the power button that says restart phone. (or whatever the first option is it should say restart). You will see in your apps on your phone a app called superuser permissions. That is what you want to see to know if it worked. Once that is there run the wifi tether app that i showed you how to install earlier.
The web site above has some very good help forums but to be honest this is very simple to do just take your time and if you have any computer skills at all and can follow instructions you can do this.
So, since it is root instructions, is he selling a method that would void the warranty?
Hi All,
We'll be sending out a newsletter shortly to anyone who registered with us when they were setting up their MOJO but I thought the community here on XDA would appreciate some early notice. The new firmware release is available now and can be downloaded from this link:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-signed-ota-MO0202-WW.zip
I recommend downloading directly on MOJO so it goes straight into your Downloads folder. It's then simply a case of running the Software Update app in your All Apps view, selecting the 0202 update and then clicking Upgrade.
As I've mentioned on a few other threads this will remove Paul's Modaco Root Mod, but you can then reapply the mod back once the update has finished.
The main feature this update adds is Over The Air update capability so manual updating won't be required in future. It also addresses the bug with Bluetooth keyboards where the onscreen keyboard keeps appearing, along with a couple of other Bluetooth tweaks.
Awesome. Will update mine tonight after work, then reapply the MoDaCo Mod. Let you know how it goes...
Mad Catz Rich said:
Hi All,
We'll be sending out a newsletter shortly to anyone who registered with us when they were setting up their MOJO but I thought the community here on XDA would appreciate some early notice. The new firmware release is available now and can be downloaded from this link:
ftp://86.54.116.234/pub/software/mojo/firmware/mojo-signed-ota-MO0202-WW.zip
I recommend downloading directly on MOJO so it goes straight into your Downloads folder. It's then simply a case of running the Software Update app in your All Apps view, selecting the 0202 update and then clicking Upgrade.
As I've mentioned on a few other threads this will remove Paul's Modaco Root Mod, but you can then reapply the mod back once the update has finished.
The main feature this update adds is Over The Air update capability so manual updating won't be required in future. It also addresses the bug with Bluetooth keyboards where the onscreen keyboard keeps appearing, along with a couple of other Bluetooth tweaks.
Click to expand...
Click to collapse
Any recommendation as to which FTP client to use? Not having any luck using the browsers.
Cool!
Domomojo said:
Any recommendation as to which FTP client to use? Not having any luck using the browsers.
Click to expand...
Click to collapse
From dolphin it goes to oprah classic for me and works
I'm updated. No issues with the download or software upgrade. Was able to re-apply MoDaCo mod for MOJO with no issues as well. +1 Madcatz
gwaldo said:
Cool!
From dolphin it goes to oprah classic for me and works
Click to expand...
Click to collapse
I don't understand what that means. Can you be more explicit? When, while using Dolphin, I click on the link provided, I get "page not found". Ditto when I use the stock browser. Have you downloaded an FTP client add on to Dolphin of ???
Did you install ES File Manager, as we recommend in our Getting Started section from the M.O.J.O. link on your homescreen? If not try it and then see if that can handle the download for you when you click the link.
Mad Catz Rich said:
Did you install ES File Manager, as we recommend in our Getting Started section from the M.O.J.O. link on your homescreen? If not try it and then see if that can handle the download for you when you click the link.
Click to expand...
Click to collapse
I did install ES File Manager when I initially set up my MOJO. At some point since then, I "updated" to version 2.4.9.8 (Aptoid notified me that an update was available if I recall correctly). Given your instructions, I went back and checked the version available from Google Play, which is 3.1.0.1. I uninstalled 2.4.9.8 and installed 3.1.0.1, and tried the URL you provided again, and now it is downloading (extremely slow download speed BTW - ~60Kb/s).
I read somewhere recently that Asian cultures enjoy ambiguity in their instructions. Whether that is true or not, I do not know. I however, detest ambiguity. If MCZ ever hopes to make MOJO ready for the masses, please be as explicit as possible with your instructions. Doing so will prevent a lot of frustration.
PS: Thanks for your help!
just use the link that is in the mojo setup app on your homepage it doesn't dl 110 its the link with new firmware
buggin0915 said:
just use the link that is in the mojo setup app on your homepage it doesn't dl 110 its the link with new firmware
Click to expand...
Click to collapse
Downloaded the update and installed it per the previous post, but knowing that the update can be accomplished using the update firmware link contained in the mojo setup app is good to know. Thanks!
The explanation from the entrance post may confuse some people.
It's not a must to download the firmware directly with the M.O.J.O.
You can download the update with your computer at the regular way and put the file on a sdcard.
It should be listed in the update tool, if you start it.
You only need to choose it and answer the dialogue box.
Hi
When i clik on upgrade, android shutdown and never restart.
Are you running the file off the MOJO internal memory?
If youre doing it via USB, plug the thumb drive into the USB 3.0 port (if you plug it into the USB 2.0, it won't work).
try to force, it s work
Thank you
OK, so there's a post nearly identical to this, with the CLEAR exception of it being specific to Android 6.x (Marshmallow). For that thread, go HERE.
DO NOT ATTEMPT ANY OF THE BELOW STEPS ON MARSHMALLOW. THIS IS FOR ANDROID 7.X (NOUGAT ONLY)
OK, quick backstory. Like the other link, none of this is my work and all the people whom I've worked with and confirmed each step of these instructions are working and validated are here:
spotting, clsA, Atarii, faizalotai, BonezMontana, schluk and Sheldd. This is NOT my work, this is the combination of all these guys help. Thank them! If you need any help, please post here. I'll help the best I can, but I've got a 15 month old and between changing diapers and RAGING FITS due to lack of Cheddar Goldfish, I spend my side time flashing like crazy. PLEASE assume all risk and responsibility when following the instructions below. If you mess up, ask for help. I'm not liable. Neither are the guys you should be thanking above for this!
Cheers!
This process assumes the following: You're on stock Android 7 (Nougat) with no modifications.
Basic steps are:
1. Unlock the bootloader
2. Flash TWRP
3. Flash SuperSU
4. Fix your BT/NFC (if you have issues)
5. There is extra instruction here as well for AdAway and V4A (Viper4Android)
Unlock the bootloader
Follow this link to unlock your bootloader.
1. Go to Huawei's EMUI site and log in. If you need to create a new account, do so. Link here: http://www.emui.com/en/plugin/hwdownload/download
2. Click on the DOWNLOAD link at the top of the site.
3. Underneath the search field you will see a green link that says "Unlock Bootloader". Click it and follow the instructions. You will be asked to enter in several pieces of information about your phone.
4. Once you've filled out all the information, you will receive your unlock code at the bottom of the screen. Write this down and save it. This number will NEVER change.
5. On your Honor 8, go to Settings > About and tap on the Build Number seven times until you unlock the Developer Settings.
6. In Developer Settings, check Enable OEM Unlock.
7. Scroll down a bit more and check USB Debugging.
8. Go to Huawei's site and download their HiSuite and install it. This installs the OFFICIAL Honor 8 USB driver. Link here: http://consumer.huawei.com/minisite/..._en/index.html Once the app is installed, you can unselect start with Windows under settings.
9. Plug in your Honor 8 with the provided USB cable. Give it about 45 seconds to install the driver and recognize it. You may need to go to your phone and tap on "Allow File Access". You will be presented with a question asking if you'd always like to trust the computer you just connected to. Select yes, if this is your primary computer you will be working with.
10. Now download the most up to date ADB drivers. A Google employee has created one link to get that and make it easy. Link here: https://developer.android.com/studio...orm-tools.html
11. Open the zip file you just downloaded and create a folder on your computer easy to get to (I recommend c:\ADB) and paste those files there so they are extracted.
12. Now open the folder up in Windows Explorer if you closed it and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
13. Type adb devices and hit enter. You should see a device ID as a response in the window.
14. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
15. Now type fastboot devices and hit enter. You should see your device ID appear again.
16. LAST CHANCE before it wipes everything and unlocks the booloader!!! Type fastboot oem unlock XXXXXXXXXX (where XXXXXXXXXX is the unlock code you received on step 4) and hit enter. It will ask if you're sure. Once this is done, the phone will wipe your data, unlock the phone and reboot. Your Honor 8's bootloader is now unlocked.
Click to expand...
Click to collapse
Flash TWRP
Grab a working copy of TWRP here.
1. Download TWRP into the same folder you used in the steps above (where you're keeping all your files)
2. Navigate in Windows Explorer to this location and hold down the Shift key and RIGHT click in the open area and click "Open command window here"
3. Type adb devices and hit enter. You should see a device ID as a response in the window.
4. Type adb reboot bootloader and hit enter. Give it a couple of seconds and the phone will load the bootloader.
5. Now type fastboot devices and hit enter. You should see your device ID appear again.
6. Type fastboot flash recovery frd-twrp.img and hit enter.
7. Once this is complete, unplug your phone.
8. Hold Volume UP and Power at the same time. Release ONLY the Power button after the blue Honor logo appears.
9. You now are booted into TWRP and it's been successfully flashed.
Click to expand...
Click to collapse
Flash SuperSU
Download the SuperSU SPECIFICALLY FOR NOUGAT here.
1. Boot into TWRP
2. Once there, when asked to keep system read only? - swipe to allow modifications
3. Tap Install
4. Tap Select Storage - Select your SD card
5. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
6. Swipe to confirm flash
7. Ignore the multiple errors: "Failed to mount '/data' (Invalid argument)
8. Go back to the main menu
9. Select Reboot to Recovery
10. When asked to keep system read only? - swiped to allow modifications (again)
11. Tap Wipe
12. Tap Format Data
13. Type YES then hit enter
14. It will format data using make_ext4fs..
15. When finished, tap Reboot System
16. Reboot back into TWRP
17. Swipe to allow modifications (You can check the box to never show this again)
18. Tap Install
19. Select storage
20. Select your SD card
21. Select the supersu file "SuperSU-v2.79-201612051815-EMUI5.0.zip"
22. Swipe to confirm flash
23. You should see NO ERRORS now when installing SuperSU
24. Wipe cache/dalvik
25. Swipe to wipe
26. Reboot system
Click to expand...
Click to collapse
Fix your BT/NFC (if you have issues)
Some people are stating that after flashing this fix that they lose their keyboard. I'm throwing up a link here to get the latest GBoard.apk file.
Follow these instructions to fix BT/NFC issues.
This file is for the FRD-L04 ONLY.
Instruction for AdAway
Follow these instructions to get AdAway working. This is only instruction, NOT where to download. I suggest F-Droid. Use Google.
Instruction for V4A (Viper4Android)
Follow these instructions to get Viper working on Nougat.
How multiple people have successfully gone back to MM if they have too many issues with Nougat.
Follow these instructions to get back to MM. Breathe.. it's actually not that bad at all.
You can find the OFFICIAL files to download on the Honor Support site located HERE.
Hi, i suggest removing the code tags and add the quote one instead so that people wont have to scroll down and scroll sideways too
Thanks for the sum-up! This thread gave me enough confidence to tweak my Honor8 on Nougat.
I'll try to get Adaway tonight, and will report any problems
EDIT: After flashing the update_data_full_hw_usa.zip to get BT and NFC, I only got NFC back. Can't turn on BT.
I reformated data to f2fs and reflashed supersu then update_data_full_hw_usa.zip but it's even worse, I don't have NFC. @joesee, any idea what went wrong?
=> considering a rollback now...
I already have 2 zips for viper which just needs to install and then set selinux to permissive and no struggle with installation if u have busy box
Sent from my NATASHA using Tapatalk
LastStandingDroid said:
I already have 2 zips for viper which just needs to install and then set selinux to permissive and no struggle with installation if u have busy box
Sent from my NATASHA using Tapatalk
Click to expand...
Click to collapse
Yeah, there were a lot of people including myself that had issues with that not working unless we renamed that audio_effects.conf file. To test, I even tried the standard apk file to try to install because I really hate the new EQ layout of the version 2.5. It is such a pain in the butt to scroll over just to adjust a frequency!
trainpunk said:
Hi, i suggest removing the code tags and add the quote one instead so that people wont have to scroll down and scroll sideways too
Click to expand...
Click to collapse
That's the one I was actually trying to do but I've never posted anything extravagant like that on here haha. Thanks!
takichiman said:
Thanks for the sum-up! This thread gave me enough confidence to tweak my Honor8 on Nougat.
I'll try to get Adaway tonight, and will report any problems
EDIT: After flashing the update_data_full_hw_usa.zip to get BT and NFC, I only got NFC back. Can't turn on BT.
I reformated data to f2fs and reflashed supersu then update_data_full_hw_usa.zip but it's even worse, I don't have NFC. @joesee, any idea what went wrong?
=> considering a rollback now...
Click to expand...
Click to collapse
Well I've went through this process three times myself back when I was trying to figure it out. There's at least two other threads that say the data partition needs formatted to f2fs. I don't know if the formatting of the data partition has anything to do with it or not to be honest because right now my data partition is ext4 and I don't have issues. Before you roll back, try doing a factory reset and just letting that process reformat on it's own and see if that resolves. If it does, I'll update the OP and just take that part out.
It was only put there because several people said that it was a better format and more efficient, so I'm not sure!
joesee said:
Well I've went through this process three times myself back when I was trying to figure it out. There's at least two other threads that say the data partition needs formatted to f2fs. I don't know if the formatting of the data partition has anything to do with it or not to be honest because right now my data partition is ext4 and I don't have issues. Before you roll back, try doing a factory reset and just letting that process reformat on it's own and see if that resolves. If it does, I'll update the OP and just take that part out.
It was only put there because several people said that it was a better format and more efficient, so I'm not sure!
Click to expand...
Click to collapse
After the factory reset, NFC is back, but BT cannot be turned on.
From what I understood, do I need to make sure to have an ext4 data partition to rollback to MM ?
Thanks for the answer
takichiman said:
After the factory reset, NFC is back, but BT cannot be turned on.
From what I understood, do I need to make sure to have an ext4 data partition to rollback to MM ?
Thanks for the answer
Click to expand...
Click to collapse
I had a conversation with the guy in this thread: https://forum.xda-developers.com/ho...ing-nougat-t3550015/post70859564#post70859564 While he says you really should - I didn't, and had no problems at all with it. Your mileage may vary.
joesee said:
I had a conversation with the guy in this thread: https://forum.xda-developers.com/ho...ing-nougat-t3550015/post70859564#post70859564 While he says you really should - I didn't, and had no problems at all with it. Your mileage may vary.
Click to expand...
Click to collapse
Okay thank you.
Just for information, it looks like my firmware version is now B320 while I had the B360 before. Probably due to the flashing of update_data_full_hw_usa.zip
Regarding the rollback procedure (which I'm doing for the 1st time), while everybody mention that i should put the dload folder in the sdcard, the huawei pdf document indicates that I should put it in the internal storage
Is huawei mistaken or am I mixing things?
takichiman said:
Okay thank you.
Just for information, it looks like my firmware version is now B320 while I had the B360 before. Probably due to the flashing of update_data_full_hw_usa.zip
Regarding the rollback procedure (which I'm doing for the 1st time), while everybody mention that i should put the dload folder in the sdcard, the huawei pdf document indicates that I should put it in the internal storage
Is huawei mistaken or am I mixing things?
Click to expand...
Click to collapse
Right now there's too many version of data full.zip, your's because of older version of full data.zip..
Just make sure its around 0.88mb for b360..
takichiman said:
Okay thank you.
Just for information, it looks like my firmware version is now B320 while I had the B360 before. Probably due to the flashing of update_data_full_hw_usa.zip
Regarding the rollback procedure (which I'm doing for the 1st time), while everybody mention that i should put the dload folder in the sdcard, the huawei pdf document indicates that I should put it in the internal storage
Is huawei mistaken or am I mixing things?
Click to expand...
Click to collapse
Either or will work for the dload folder. I've flashed both actually. Might be better to put it on the SD instead of internal so it's easier to format. Your choice, really.
Regarding the firmware versions, I think the OTA brought it up to 360 and that update data is a zip created from 320. Don't quote me on that, though.
joesee said:
Either or will work for the dload folder. I've flashed both actually. Might be better to put it on the SD instead of internal so it's easier to format. Your choice, really.
Regarding the firmware versions, I think the OTA brought it up to 360 and that update data is a zip created from 320. Don't quote me on that, though.
Click to expand...
Click to collapse
faizalotai said:
Right now there's too many version of data full.zip, your's because of older version of full data.zip..
Just make sure its around 0.88mb for b360..
Click to expand...
Click to collapse
Following what @faizalotai said, I will find a data update for the B360 and try and flash it and see what happens.
takichiman said:
Following what @faizalotai said, I will find a data update for the B360 and try and flash it and see what happens.
Click to expand...
Click to collapse
I'd be curious to know because I'm on b320 right now. I haven't tried making a backup of my current ROM yet. I hope it doesn't fail. I've never been able to backup MM.
joesee said:
I'd be curious to know because I'm on b320 right now. I haven't tried making a backup of my current ROM yet. I hope it doesn't fail. I've never been able to backup MM.
Click to expand...
Click to collapse
Sadly, it didn't work. I was in that case in which I have no keyboard, no apps and so on...
So I rollbacked to MM using Huawei's official packages.
If anyone needs the B360 data file, refer to this thread
takichiman said:
Sadly, it didn't work. I was in that case in which I have no keyboard, no apps and so on...
So I rollbacked to MM using Huawei's official packages.
If anyone needs the B360 data file, refer to this thread
Click to expand...
Click to collapse
Did you get BT back?
joesee said:
Did you get BT back?
Click to expand...
Click to collapse
Yes,
when rolling back to MM, I also noticed that TWRP was replaced by the stock recovery. I'm not yet certain but the bootloader is probably locked now.
I think I lost BT because i flashed a data zip prior to the firmware version I was using.
But I remain curious, I think i'll try to update to Nougat again and retry all of this again.
Please, link downloadable files directly. If You write a complete tutorial, the peoples won't need to read another one, to point a final link, where he at least download the suggested files.
Please, short this way.
For what it's worth, I only had to flash this file from TWRP to get the apps back and fix nfc and bt on my l04. It's the data file for the newest b360. http://update.hicloud.com:8180/TDS/...09/f1/full/hw/usa/update_data_full_hw_usa.zip
Oh, the keyboard wasn't working... So I texted myself my email and password from my lady's phone, copied and pasted that in to get into the Play Store, opened up my apps and installed my favorite keyboard. Now to mess it up some more...
Skeletor916 said:
For what it's worth, I only had to flash this file from TWRP to get the apps back and fix nfc and bt on my l04. It's the data file for the newest b360. http://update.hicloud.com:8180/TDS/...09/f1/full/hw/usa/update_data_full_hw_usa.zip
Oh, the keyboard wasn't working... So I texted myself my email and password from my lady's phone, copied and pasted that in to get into the Play Store, opened up my apps and installed my favorite keyboard. Now to mess it up some more...
Click to expand...
Click to collapse
Thanks for sharing this. I'll update the OP with the newer b360 data file. I'm curious what the difference is between b320 and b360. Wonder if it's worth the effort to try to upgrade.