sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
ok so i used this: themikmik dot com/showthread.php?11114-GUIDE-WIP-How-to-achieve-S-OFF-after-unlocking-2-18-HBOOT-with-HTCDev-com-No-More-Watermark
after using the HTCDEV to unlock.
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
i am stuck in between step 10 and 11.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
i downloaded su, root checker,and busy box. root checker says the phone is rooted. i know i need to get the h boot to a lower level inorder to do the unrevoked3 program.
tried flashing the recovery and says "cant open /sdcard/pc36img.zip (bad)"
made sure it wasn't zip.zip and it was so i fixed that and still wouldn't work.
the only thing i am not sure of is step 10 and wether i did it right :Once the misc partition has been updated, you can downgrade your Bootloader and HBOOT to a non-watermarked version rootable with unrevoked.
does the partition auto update or do i need to do something to make it update? i didn't see any option for this. eveything up to this point went exacty liek it should have so now i am lost. i have searched numerous forums and found similar problems but none that were exactly the same. and none of the solutions worked for me. i tried all the basics rebooting, etc and nothing. any info would be greatly appriciated.
the only other thing that i may have done wrong that i can tell is what file i am trying to make the pc36img. at the bottom of post # 1 it has 2 attachments listed as pc36img files those are the ones i am trying to use. when i try to click the hyperlinks thru the rest of the post i get an error message from that site thats says " This account's public links are generating too much traffic and have been temporarily disabled! " so i dont know if that site has the same zip files or i am completely using the wrong zip file.
sorry for the long winded post i know the noob video says make it brief but i figured the more info the better.
thank you.
sprint evo 4g, updated to the newest version before deciding to root. yes i now know that was my biggest mistake!
Click to expand...
Click to collapse
Oh brother was it!
basic info:
says unlocked at top of screen
hboot 2.18.0001
radio 2.15.00.12.19
s-on
version 2.3.5
kernel 2.6.35.10 g4b48446
software 4.67.651.3
pri2.33_003
prl 60683
hardware 0003
Click to expand...
Click to collapse
Your S-On,so your not rooted.
problem i am having is the pc36img.zip. i tried both that are listed and tried both from different computers to make sure it wasn't a pc issue. i get a message that says "no or wrong zip image" it never gives me the option to update in fastboot. and never goes to saying locked again as described in the tutorial.
Click to expand...
Click to collapse
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Diablo67 said:
Oh brother was it!
Your S-On,so your not rooted.
Make sure the PC36IMG is all in CAPS.
Sent from my Dell PC.
Click to expand...
Click to collapse
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
when i check with root checker it says i am rooted and have su. maybe it just means unlocked? busy box also says rooted?
pc36img is in all caps.
thanks for the quick response!
evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
evo4gnoob said:
Actually s-on or s-off status doesn't determine if your rooted or not. That indicates wether your NAND unlocked or not. To be rooted is to have busybox and superuser permissions
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
This. S-Off/S-On is basically root for bootloader only has no bearing on root of phone itself you can be s-on and still root your phone you just wont have or be able to have a custom recovery or flash unsigned zips thru bootloader so romming is almost impossible but root is completely possible
Click to expand...
Click to collapse
Ok,thanks for clearing that up,serious dudes i hate giving the wrong info when trying to help someone and i don't mind admitting when i'm wrong,lol.Your never to smart or old to learn something new.
Sent from my Dell computer.
I can probably help here.
If all you want is to be rooted, then you are. There's no reason to do the rest, especially if you're out of warranty. Since you already have a custom recovery installed, you can feel free to flash a custom ROM, and not even worry about the rest of the process.
The Dropbox links thing should be fixed now. I had to move them all to 4shared.
As far as the misc partition flashing, as long as you didn't get any errors when in the command prompt/adb shell, then I'm sure it flashed successfully. The only way to tell is if the Froyo PC36IMG.zip flashes successfully without a "main version fail."
I can assure you the PC36IMG works, as I've used it many times myself. Did you confirm the md5? Is it possible your SD card got corrupted somehow? Those are the only reasons it wouldn't pick it up.
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
98tib said:
thanks for coming in here i really appriciate it.
i still pay for the extended warranty if thats what you are asking for my phone.
my hboot is still 2.18 and because of that i can not run the unrevoked software either.
as far as the pc36img, i am just not sure if i am changing the name on the correct file. in your first post you have 2 attachments, those are the ones i tried to use to rename, was i correct in doing that? if i go back to where you say to use the 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
it goes to a dead site, so thats what makes me think i did something wrong. no main version ail messages and the top of my fastboot screen still says unlocked, not locked and not missing.
thank you again for your help and imput
how do i confirm if the md5 number is correct?
Click to expand...
Click to collapse
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Captain_Throwback said:
The two files attached to the first post are both recoveries. You only needed one of them, and I assume you were okay with that part. The link you speak of should be working now, and that file gets renamed the same way the recovery zip did. As far as checking the md5, you just need to find a program that will do that. I use HashTab.
Like I said before, the dead link has nothing to do with you; Dropbox just canned my account because of too many downloads. The link should now be pointing to 4shared if the md5 doesn't match and you need to redownload.
You don't necessarily need to worry about the watermark issue now; just wait until you need repairs, and then you can use that process to remove it. You'll probably know a lot more if/when that happens, and the process will be easy as pie .
Click to expand...
Click to collapse
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
98tib said:
i used only one and that was fine.
here is the link i am talking about, when i click on the hyperlink for pc36img.zip it still leads to drop box.and not a file i can download to drop/drag to the root of the sd card
PC36IMG.zip - 3.70 Froyo ROM with 2.10 HBOOT - md5: 7056D42812AA5DF03FCC8DDDC2B64E85
both attachments at the bottom of post # 1 start with pc36img, i am using one of them as the renamed file, i am sure if i am wrong in doing that at this point.
i understand about the water mark. thank you.
Click to expand...
Click to collapse
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
This is what's cool about this forum a noob asking a question and you get 4 big time contributors helping out!
Sent from my PC36100 using xda premium
Captain_Throwback said:
Thanks, you were right, that link wasn't updated. It is now .
You can remove the renamed recovery PC36IMG from your card and replace it with the Froyo PC36IMG, if you're going to continue trying to flash and NAND unlock with unrevoked.
Click to expand...
Click to collapse
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
98tib said:
thank you.
i downloaded the correct file, renamed, and moved to the sd card and i'm still having the same problem. never asks to update. still says unlocked and still can't run unrevoked.
i really do appriciate all your help and imput with solving my problem
Click to expand...
Click to collapse
What kind of sd card are you using? You might want to try a different card, or reformat the stock card, if that's what you're using. That's the only other reason it wouldn't pick up the file, provided it's named correctly. And I assume you verified the md5 and it's good? And you're certain the file is on the root of the sd card as well? I cant think of anything else that could be causing the problem. Let me make sure my bootloader reads the file just to make sure.
EDIT: Scratch everything I said above. If your phone still says "unlocked" at the top of the bootloader, the misc partition wasn't updated successfully. Did you already complete that part, with no errors? You need to reconnect the device while booted up, with USB Debugging enabled, and run those commands from the command prompt from the folder with adb in it. Make sure you have the files "flash_image" (extracted from zip file) and "mtd-eng.img" (extracted from zip file) on the root of your sd card. If you're using Windows 7, run Command Prompt as an administrator. Let me know the output of those commands before continuing. If you got any errors on that part, that would be why you can't flash the Froyo ROM.
I saw you mentioned that in your OP, but I guess I didn't realize you skipped that part. That'a really the most important part of the process. It's the part right before the sentence you mention about the misc partition being downgraded. That last command flashes the mtd-eng.img file to the misc partition.
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
98tib said:
both files are unziped and on the sd card, running windows vista. ran the cmd and it looked like just like it did in your post but now that i am thinking about it i dont remember the phone doing anything. i also have the zip file for both on the sd card, should i remove them? but then again it didn't give me any errors either.
using the stock sd card. sandisc 8gb class 4.
i will redo the cmd portion again when i get home, limited here at work.
i thank you again for your help.
Click to expand...
Click to collapse
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Captain_Throwback said:
It does sound like it worked okay. The phone isn't supposed to do anything. But there is a way to verify that it flashed successfully. And yes, you should delete the zip files for those off of the root of your sd, to be safe.
Before you re-run those commands, open a command prompt and navigate to the location of fastboot. Put your phone into fastboot mode, connect to the the computer, and run this command:
Code:
fastboot getvar mainver
and report back what it says. My guess will be it'll report "4.67.651.3". That means the main version hasn't been downgraded. Then, reboot the device and run the commands as listed in the guide to gain superuser access & flash the downgrade to the misc partition. Then reboot into the bootloader, and you'll know it worked if it now says "LOCKED (OOW)" at the top. If it doesn't, then I'm not really sure what to do next. But definitely do a screenshot of the command prompt commands and output, starting with "adb shell".
Click to expand...
Click to collapse
thank you, you are my savior! its always the dumb things that you think you did right that you did wrong! lol. thank you again!
now i'm off to screw something else up!
Related
How do I root this thing I've tried just about every tutorial I've seen they all fail either because of permission errors or update failed in the stock bootloader menu.
This is a brand new Evo that just came back into stock today.
Hardware 003
Software: 1.47.651.1
Build: 1.47.651.1
Baseband: 2.05.00.06.10
I just got this replacement due to my old phone being defective but no root methods seem to work correctly. Any ideas?
Just did it last night with my replacement.
Follow this guide: http://forum.xda-developers.com/showthread.php?t=706411
Download your favorite ROM to your SD card.
Then follow this guide under recovery instructions: http://forum.xda-developers.com/showthread.php?t=690762
When you load it up, flash your rom you downloaded on your SD card.
Enjoy!
UrbanMuppet said:
Just did it last night with my replacement.
Follow this guide: link removed since I can't post them.
Download your favorite ROM to your SD card.
When you load it up, flash your rom you downloaded on your SD card.
Enjoy!
Click to expand...
Click to collapse
Tried that multiple times, it was the first method I used it copies the PC36IMG file then when it goes to check it it gives me a "Main version is older Update failed!" error, if I try to manually copy and do it by hand like I'm used to I get the same problem.
I don't get it.... Redownload it again, maybe corrupt/old? Make sure your version matches?
Download Simple Root, run the .exe and make sure your phone is in USB Debugging. It does it all for you. Once it's done you have a half-ass rooted stock rom. At that point power down and boot into recovery and run recovery-windows.bat and it loads a temp recovery. Use that to install whatever rom (Wipe first) and then use rom manger to install clockwork and enjoy.
UrbanMuppet said:
I don't get it.... Redownload it again, maybe corrupt/old? Make sure your version matches?
Download Simple Root, run the .exe and make sure your phone is in USB Debugging. It does it all for you. Once it's done you have a half-ass rooted stock rom. At that point power down and boot into recovery and run recovery-windows.bat and it loads a temp recovery. Use that to install whatever rom (Wipe first) and then use rom manger to install clockwork and enjoy.
Click to expand...
Click to collapse
You can't get past part one in simple root again when it copies the zip file from the simple root folder in adb (this is done automatically) and it attempts to scan the file in the stock bootloader I end up with a "Main version is older, Update Fail" error message, you cannot get past that at this point my only options are to either reboot or shutdown. Again it does not install the zip file like it's suppose to,I've rooted my old Evo countless times without the need for this simple root GUI stuff I'm perfectly capable of root in adb but again both give me the same error.
My guess is that you're trying to use the same PC3IMG in both parts and that's why you're getting the "Main version is older" error. You have to use the engineering PC3IMG in the second part, not the PC3IMG used in the first part (of toast's tutorial). You have to remove that one and rename the engineering version to PC3IMG and then run that.
Basically, read the tutorial and follow it exactly.
ultron said:
My guess is that you're trying to use the same PC3IMG in both parts and that's why you're getting the "Main version is older" error. You have to use the engineering PC3IMG in the second part, not the PC3IMG used in the first part (of toast's tutorial). You have to remove that one and rename the engineering version to PC3IMG and then run that.
Basically, read the tutorial and follow it exactly.
Click to expand...
Click to collapse
Nope wrong, I never got to part two since I never got part one to finish how could I use it twice if I couldn't even use it once? I knew exactly what was wrong the problem is I didn't know how to fix it. At least until I found this gem:
http://ip208-100-42-21.static.xda-developers.com/showthread.php?p=7410421
The fix is in the link above in case anyone has the same problem, note that this only really happens with the newer batches of Evos that have been patched to 1.47 by Sprint and you'll have to trick the phone into downgrading from 1.47 back to 1.32 and then back to 1.47 rooted again.
I'M BEING VERY CLEAR HERE-THIS IS FOR CDMA DESIRE ONLY, NOT GSM!!!
You have to be S-OFF to do this.
Because the CDMA desire does not have extended fastboot yet, this is the only way to change the ( white with green HTC ) screen to a custom splash1 ( anything you want ) screen.
Giving credit where its due, I'd like to thank:
Team unrevoked for S_OFF
MRE-net for his guide with the .img converter tool and half of his how to that I was able to use, I will put his link in here.
ipfreelytech for his encouragement and unknowingly pointing me in a direction that made sense.
The only part I played in this is bringing these together and finding the right way to create the .txt file.
If I missed anyone, feel free to point it out.
I'm going to make this quick and simple but explain in detail so no one should have a problem but not to where you have zero legwork yourself; it took me 3 weeks to figure this out.
Requirements: my android-info.txt file
MRE-net's nbimg coverter tool
And whatever flavor archiver tool to make the .zip
Download this-[URL=http://www.4shared.com/document/ymcXsiz-/android-info.html]android-info.txt[/URL]
Go to this link http://forum.xda-developers.com/showthread.php?t=795132,
download NBIMG command-line splash<-->image converter tool for your platform, read how to use the nbimg tool in command prompt ( extremely easy ). Read his how to thoroughly but PAY NO ATTENTION TO THE FASTBOOT PORTION!!!!!!!!!! Basically don't bother past #8.
Now, after you have converted it with nbimg tool, you want to zip up the android-info.txt and the splash1.img you created together and name it PB99IMG.zip ( exactly how I have it underlined ) and place it on the root of your sdcard. Reboot into booloader ( which on my phone the screen goes straight to fastboot ) the fastboot screen has the word FASTBOOT highlighted in RED, and below it a little, BOOTLOADER is highlighted in BLUE. If thats what you see then hit the power button once and you should see HBOOT highlighted in BLUE under the phone info. Give it a few seconds ( 10-15 ) and you should see this:
Parsing...(SD ZIP)
(1) SPLASH1
Do you want to start update?
<VOL UP> Yes
<VOL DOWN> No
You want to hit vol up obviously and when you do it happens very quick, almost instant and then hit vol up again to reboot and BAM, you should see your new SPLASH!!!!!!
Now for those who this didn't work for, its NOT the .txt file. More than likely its a bad archive or you didn't do the image right, so I don't want a lot of negative feedback because people can't figure it out. I have changed mine a couple times before I wrote this up, WORKS GREAT!!!!!!!!!
Note: If your baseband differs from the mainver: in the .txt file then edit it to what yours is before you make the .zip or it wont work.
ENJOY GUYS!!!!!!!!!!!
why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?
Rastaman-FB said:
why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?
Click to expand...
Click to collapse
So far nothing else worked on cdma. The tool or manual commands. I'm going to try this out after work. Thanks for finding this!
Definatly going to give this a shot after work as well. Thanks for figuring this out.
Rastaman-FB said:
why this long and complicated way?
can you not just convert it to img and then do
fastboot flash splash imagename.img ?
also there is a one click tool that will convert 24bit bmp to image and auto flash your device here
http://forum.xda-developers.com/showthread.php?t=794638
i thought this worked on both gsm and cdma desires with s-off
EDIT: can you use extended fastboot commands with cdma unrevoked s-off?
Click to expand...
Click to collapse
Currently the CDMA Desire does not have extended fastboot commands, despite having s-off. The Alpharev team is working on getting it working so this is our only method available for now
It totally works! Thanks lohp75 for doubting me when I said it couldn't be done lol
Like I said bud, doubt creates possibilities .
Sent from my HTC Desire CDMA using XDA App
heavymetalmage said:
Currently the CDMA Desire does not have extended fastboot commands, despite having s-off. The Alpharev team is working on getting it working so this is our only method available for now
Click to expand...
Click to collapse
my bad mate, as you had s-off i assumed they would have included extended fastboot commands
AWESOME!!!! very easy to do just sounds difficult. thanks for getting it working and posting for us all!
You guys are very welcome :+). Its good that I am able to contribute back to the community instead of being a full time mooch . And like I said in the post, I detailed it so everyone should understand how to do it, but it will be so much easier when extended fastboot comes available to us!
Sent from my HTC Desire CDMA using XDA App
Ok I have followed this guide exactly.. I have done and re done the picture in Photoshop, tried converting it with several file converters, and they all get the same result...
That is the file I made.. I changed the baseband to coinside with my device (US Cellular HTC Desire)..
And it completely refuses to flash the zip. There are some error messages that pop up VERY quick, what I can see, says no image in zip.. but its there... converted with the tool...
Any ideas???
Well bud, the only problem I saw with it is you must not be s-off. If that's the case then go to unrevoked.com and get what you need for your phone. I looked in your zip and for ****s and giggles flashed it to my phone and it worked as smoothly as mine does. Of course I had to flash back to mine. So your zip is good.
Cythrawl said:
Ok I have followed this guide exactly.. I have done and re done the picture in Photoshop, tried converting it with several file converters, and they all get the same result...
That is the file I made.. I changed the baseband to coinside with my device (US Cellular HTC Desire)..
And it completely refuses to flash the zip. There are some error messages that pop up VERY quick, what I can see, says no image in zip.. but its there... converted with the tool...
Any ideas???
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App
good job! I knew this would work, glad you figured it out. Rocking a custom splash on my phone now
lohp75 said:
Well bud, the only problem I saw with it is you must not be s-off. If that's the case then go to unrevoked.com and get what you need for your phone. I looked in your zip and for ****s and giggles flashed it to my phone and it worked as smoothly as mine does. Of course I had to flash back to mine. So your zip is good.
Sent from my HTC Desire CDMA using XDA App
Click to expand...
Click to collapse
Yes its S-Off.... I have Cyanogen Mod on it... I can do everything else except change the boot splash...... I am at a loss why it's not working for me.... Followed the guide exactly...
EDIT::: Just tried the Unrevoked FOrever patch too.. still the same issue....
This is what the Bootloader says:
BRAVOC DVT2 SHIP S-OFF
HBOOT-0.98.0000
MICROP-051e
TOUCH PANEL-SYNW0101
RADIO-2.05.10.06.29
Jul 5 2010, 19:14:11
Everything seems right and correct... Oh well... I give up...
Does it give you the option to update, or does it flash a bunch of crap real quick then back to hboot? Maybe try and redownload my original. txt file and don't modify it at all, zip it up and try again. I was able to flash yours without changing the mainver: surprisingly.
And the unrevoked that you did was through recovery right?
Cythrawl said:
Yes its S-Off.... I have Cyanogen Mod on it... I can do everything else except change the boot splash...... I am at a loss why it's not working for me.... Followed the guide exactly...
EDIT::: Just tried the Unrevoked FOrever patch too.. still the same issue....
This is what the Bootloader says:
BRAVOC DVT2 SHIP S-OFF
HBOOT-0.98.0000
MICROP-051e
TOUCH PANEL-SYNW0101
RADIO-2.05.10.06.29
Jul 5 2010, 19:14:11
Everything seems right and correct... Oh well... I give up...
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App
lohp75 said:
Does it give you the option to update, or does it flash a bunch of crap real quick then back to hboot? Maybe try and redownload my original. txt file and don't modify it at all, zip it up and try again. I was able to flash yours without changing the mainver: surprisingly.
And the unrevoked that you did was through recovery right?
Click to expand...
Click to collapse
yes it does exactly that.. flashes up a bunch of crap real quick then back to HBoot.. And yes I applied the Unrevoked forever with recovery too (which told me I already had S-OFF). I have also tried it with your original text file (which is why I edited the baseband as I thought that was the issue)..
Its pretty odd that it doesnt work at all.... its got me totally scratching my head atm.... Im gonna try a couple of other things, but I think I wont be able to do it until the next release of Unrevoked that allows the Fastboot stuff like the GSM Desire...
EDIT:: Just tried removing all zips from the root of the SDCard and only have the PM99IMG.zip there.. Still the same result...
Ok, when I first started to play with this I got the same thing. I uploaded the zip to ipfreely who then told me it was corrupt, if he couldn't open it then phone can't right. So the next night I stopped using my windows environment and went back to using the mac osx archiver and tried it again. This time it showed flash errors, that told me the zip was good but info bad. So now I strictly use my mac and that's also where my cs5 is at.
Point being don't give up. Two more suggestions, try a different archiver, and as stupid as it sounds download your zip attachment from your post straight to your phone, again sounds stupid but exhaust all possibilities!
Cythrawl said:
yes it does exactly that.. flashes up a bunch of crap real quick then back to HBoot.. And yes I applied the Unrevoked forever with recovery too (which told me I already had S-OFF). I have also tried it with your original text file (which is why I edited the baseband as I thought that was the issue)..
Its pretty odd that it doesnt work at all.... its got me totally scratching my head atm.... Im gonna try a couple of other things, but I think I wont be able to do it until the next release of Unrevoked that allows the Fastboot stuff like the GSM Desire...
EDIT:: Just tried removing all zips from the root of the SDCard and only have the PM99IMG.zip there.. Still the same result...
Click to expand...
Click to collapse
Sent from my HTC Desire CDMA using XDA App
lohp75 said:
Ok, when I first started to play with this I got the same thing. I uploaded the zip to ipfreely who then told me it was corrupt, if he couldn't open it then phone can't right. So the next night I stopped using my windows environment and went back to using the mac osx archiver and tried it again. This time it showed flash errors, that told me the zip was good but info bad. So now I strictly use my mac and that's also where my cs5 is at.
Point being don't give up. Two more suggestions, try a different archiver, and as stupid as it sounds download your zip attachment from your post straight to your phone, again sounds stupid but exhaust all possibilities!
Click to expand...
Click to collapse
Tried 2 different archivers now.... WinRAR and 7zip... both same result.. I will get round to putting a Virtual Linux box with Virtualbox and try it with that... I all also try winzip just to be sure...... Not giving up just yet...
To be honest, thinking about it, if it was the archiver I was using then it should not have worked (my archive) on your phone either. The fact that it did, says its nothing to do with the Archiver otherwise you would have had the same result as me....
Cythrawl said:
To be honest, thinking about it, if it was the archiver I was using then it should not have worked (my archive) on your phone either. The fact that it did, says its nothing to do with the Archiver otherwise you would have had the same result as me....
Click to expand...
Click to collapse
I know I had an issue the first time around because I named the file PB99IMG.zip which really made it PB99IMG.zip.zip and it didn't show up. Probably not your issue but just a thought. Maybe you'd like to post the image, your baseband version, and we can make a file, test flash it and repost it for you to verify it works. Then, if it still doesn't work, we know it is your phone and possibly an issue with s-off that you may have to alert the unrevoked folks to. Try mounting /system to rw while booted and see if that works. That would be an indicator whether s-off is truly working.
Hey guys.
I've been attempting this all morning and so far I've had no luck. I have a VodafoneAU Legend which I updated to the official 2.2 yesterday. But now I want to try root.
I've been trying to follow the HBOOT 1.01 guide but there's a few problems. First, I cannot connect to the phone with adb unless it's in htc sync mode. No other mode will work. So when it's time to copy testimage.zip to the card I have to change from sync mode to disk mode, whereby adb loses it's connection. What do I do about this? Is it a driver problem (in Win7 here) or something else?
Thanks,
Dave.
Ok, the first problem were drivers.
Now I can't finish the second guide. When I try using clockwork to install the firmware.zip, the phone just boots to the red triangle. What do I have to do?
Dave.
So I pressed the up button/power combo at the red triangle and get the Android system recovery. Selecting "apply update.zip" says it can't verify. What do I do? Is this guide for my phone or do I need to follow something else?
I don't understand this guys. Anyone help? I'm thinking since this is a step to root the phone, I'm not actually rooted yet so I can't use the clockworkmod? Then what is the guide for? The guides at unlockr don't mention what firmware/hboot they work for so I'm not keen to try them yet.
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
whitetigerdk said:
Read the guide on fake flash. You need the recovery file named "update.zip" in the root of your sd to proceed..
Sent from my Legend using XDA App
Click to expand...
Click to collapse
But isn't that what Rom Manager does? Download the update.zip then run it? Man this is getting even harder to understand.
Edit: And this is left out of the HBOOT 1.01 guide because.....????? When I work this out I'll write a PROPPER guide, lol.
Just checked and update.zip is on the card.
So which part of the guide am I getting wrong?
Decided to reinstall phone with the official froyo release and am now ready to try this again. Is there anyone that will walk me through the process? I will write a complete guide if the "gotchas" are still there.
i feel for you ... hope you get it fixed... thats one of the reason i havent dared messing with the phone because i've seen a few post like yours where something didnt go quite as described... for whatever reason... and im sure the answer is out there but just not within the guide instructions... i guess there is no way to gather all gotchas because there are so many environment variables...
good luck
and please share your technique
Just saw gobczak's thread in the developer forum having similar troubles with Vodafone UK phone, getting the red triangle at reboot. I'll keep an eye on his thread and see how he goes with it.
Did you run the stage1 and stage2 bats while in recovery?
dezzadk said:
Did you run the stage1 and stage2 bats while in recovery?
Click to expand...
Click to collapse
No because the guide didn't say to.
The thing is it seems I'm only stuck on the part where the firmware.zip file has to be flashed. The guide says to use clockworkmod for this. But when I try installing the clockworkmod recovery it gives some file verification error. Isn't there ways to do this via the pc, either through those batch files, adb etc? Or will that fake-flash update.zip file work?
jabbado said:
No because the guide didn't say to.
Click to expand...
Click to collapse
As I just posted on the other forum, I think you need to skip that step in guide 2 and go straight onto guide 3 after you have flashed the LEGEIMG.zip, rebooted, and then removed LEGEIMG.zip from the SD card.
Guys I've got to the point of downgrading to 1.31. But when I run the first batch file it just hangs at the "Writing zip" part, with the htc logo on the screen. Is there any way to fix this?
Can someone please explain this part of the guide:
Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it. If you get CID error at this point, then you don't have goldcard.
Click to expand...
Click to collapse
Ok, so I don't get an error. I get nothing. The phone just boots to the fastboot screen. If I press the power button it goes to the hboot screen and I can see the messages of loading LEGEIMG.zip. But the guide doesn't say to press anything.
So should I or shouldn't I press the power button? Also, if I try making the goldcard again, at which point in the guide do I start from again? The entire process or just copying LEGEIMG.zip to card then rebooting phone? I mean, will all the other things like flashing misc1-2.img still be there?
Guys I finally got this working.
The first problem was with the goldcards. For whatever reason formatting them with the win7 format tool just wouldn't work. I had to use the command-line format tool, setting the block size etc manually.
The second problem was the unnecessary steps in the guide. A few people helped me out with this (namely blackbart at the Aus Whirlpool forum), but basically in the second step you can stop after flashing the LEGEIMG.zip. The updating froyo part isn't needed - for my phone anyway.
Then when running the batch files in the third part, for whatever reason the first batch would keep hanging at 'writing zip...' and I needed to remove the battery to unfreeze the phone. flannigan, also from the Aus Whirlpool forums suggested to just go on to the second batch file. This worked!
So my Legend is now finally a true Legend
Anyway, thanks for the help everyone - couldn't have done this by myself.
Dave
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 / Stock Froyo to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Sent from my HTC Legend using XDA App
EpicSauce said:
Great news, I think we need a new guide focused on rooting for HBOOT 1.01 to clear up the inconsistencies in the existing one. It's a minefield for a noob (or a rite of passage!), a revised guide will certainly save a lot of time and frustration for those taking this road in the future.
Click to expand...
Click to collapse
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Sounds good! Happy to help and add my 20c worth along the way. The existing guide has got the meaty bits, a new guide would cull the stuff not relevant, help fill in the gaps and alert to the pitfalls we've fallen into.
jabbado said:
I'll write one if ya's want. I wanted to include little tidbits like downloading the apps required (visionary, rom manager etc) from the market then backing them up to the card with Astro so if it goes all wrong and you have to start again, you can just install them all from the card Also on using adb to push the files (roms, img's etc) when the guides say "copy this blah blah". Much quicker than changing to disk mode and back. Sound good?
Click to expand...
Click to collapse
I agree... i've done my reading since june of last year but then didnt check for another 4 months... and so many how to's pop up with various ways of doing it depeding on the situation... a lot of those howtos were consolidated howtos which sometimes make intermediate steps unenecessary (may be in some cases causes more head aches since it didnt take into considerations on newer version of hboots...etc)... an updated how to will be much appreciated...
And you're right the most important pre requirement is to have a safety net ... so starting with how to create a back up in case you screw it up is a must!
but im glad it worked out for you!
i have read LOTS of forums on this, but have found no diffinative, working methods. has anyone actually ever done this, and if so what method did you use? links/guides would be much appreciated! thanks
I also have searched everywhere and apart from "get a pc" or "get parallels and windows 7 for your mac" I've heard nothing concrete.
Any advice on this would be hugely appreciated!
ishamm said:
i have read LOTS of forums on this, but have found no diffinative, working methods. has anyone actually ever done this, and if so what method did you use? links/guides would be much appreciated! thanks
Click to expand...
Click to collapse
No guys, all the methods posted are just theoretical blabber posted for the LULZ!...
.... NOT!!!
... all the methods mentioned on this forum work, unless stated otherwise...
only a handful require a Windows PC
yes, preinstall method works, CWM root package works, gingerbreak works,
1-click easy root also works
follow the link, go to post 3... and you have directions for Mac OS
sorry, i didnt mention, im not on gingerbread (thanks to tmobiles slow updating), and most of these rooting methods seem to require it. would going straight to unlocking the bootloader be easier on mac? (i realise the methods arent written for fun, but many require a lot of presumed knowledge of terminal commands, which unfortunately i lack XD )
thanks
Bootcamp or parallels with windows 7. That's how I did it.
xploited said:
No guys, all the methods posted are just theoretical blabber posted for the LULZ!...
.... NOT!!!
... all the methods mentioned on this forum work, unless stated otherwise...
only a handful require a Windows PC
yes, preinstall method works, CWM root package works, gingerbreak works,
1-click easy root also works
follow the link, go to post 3... and you have directions for Mac OS
Click to expand...
Click to collapse
Many thanks, I'll try one of the ones you mentioned.
I'd love to try the one click method for mac but I clocked on the link, went to third post and it's not as you suggested it might be.
If there is a simple oneclick method for mac dullards like me it would be great to tell me where to go for it. Thanks again!
i have tried using dorootv3.sh and doroot2, on terminal, but both always fail, is there any other .sh that has been shown to work?
---------- Post added at 06:19 PM ---------- Previous post was at 05:32 PM ----------
basically, after a load of different attempts, my main problem seems to be this: to root on mac, i need 2.3.4 (i have 2.2.2); to get 2.3.4 i need to unlock the bootloader; and to unlock the bootloader it must be rooted.
it seems im stuck in this cycle, and dont really know what i should do. any help would be great.
can i flash with the at&t 2.3.4 from this thread http://forum.xda-developers.com/showthread.php?t=1125944 ?
you dont need root to unlock bootloader....you unlock bootloader through an sbf flash
we seriously need a popup box on every freaking forum that will explain what ROOT actually is.
root is SYSTEM access within the OS. outside of the OS, root doesnt mean squat
you will wipe all your system when you unlock your bootloader which means:
contacts stored on phone (unless you export them to vcf on sdcard)
settings
text messages
user installed apps
it does NOT wipe internal or external sdcard (i always keep a backup of this stuff on my computer anyway when i start messing with my phone)
oh sorry, in that case i totally got the wrong end of the stick reading the noob intro howtos so to unlock the bootloader what sbf do i need to flash? that i can do now through terminal, which is very handy, but i havnt come across any howto on bootloader unlocking that just says flash an sbf
http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
i typed in google.com
'unlock motorola atrix bootloader'
a link lead me directly to that.....its the exact same tut listed here on xda....
sorry, im having a serious slow day, just gone on holiday so brain is totally out of gear XD thanks so much for clearing up the root/bootloader confusion, i have now unlocked successfuly, and will be installing my first rom!
ishamm said:
sorry, im having a serious slow day, just gone on holiday so brain is totally out of gear XD thanks so much for clearing up the root/bootloader confusion, i have now unlocked successfuly, and will be installing my first rom!
Click to expand...
Click to collapse
its not just you confused with root. its xda-wide.
for some reason sooooo many people have this notion that root=unlocking bl/s-off/rom-flashing
its frustrating to see people suggesting to others on some forums around here that they need to 're-root' their device when they are already on a rooted rom....its baffling that so much misinformation can be spread like wildfire.
my last confusion, for now XD, is this: the alien rom contains an image, which i can flash ok, but also a Meta Inf folder and System folder. if i follow this method
"
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
"
what should i do with the 2 folders, since as far as i know, i cant just flash folders right?
thanks
ishamm said:
my last confusion, for now XD, is this: the alien rom contains an image, which i can flash ok, but also a Meta Inf folder and System folder. if i follow this method
"
1. Extract all the files to the same directory and CD there in the terminal.
2. Put your phone in fastboot mode (turn it on holding volume down button then press volume up)
3. Type these commands in the terminal:
chmod +x moto-fastboot-osx64
./moto-fastboot-osx64 flash boot XXXXXX.boot.img (work out what Tegra part you need to flash and change the XXXXXX to that!)
./moto-fastboot-osx64 flash system ORFR234-system.img
./moto-fastboot-osx64 flash webtop webtop.img
./moto-fastboot-osx64 reboot
"
what should i do with the 2 folders, since as far as i know, i cant just flash folders right?
thanks
Click to expand...
Click to collapse
alien rom, as with any other custom rom, comes packaged for CLOCKWORK MOD RECOVERY
you dont extract rom zips
you need CWM installed on your unlocked atrix, then you boot to recovery, and flash the rom zip
oh man, just when i thought i'd started to understand everything! XD
if its not too much trouble, can you explain the method to go about installing alien on a mac, or if it exists, link a relevent thread? i can only find ones which confuse me even more
many thanks
ishamm said:
oh man, just when i thought i'd started to understand everything! XD
if its not too much trouble, can you explain the method to go about installing alien on a mac, or if it exists, link a relevent thread? i can only find ones which confuse me even more
many thanks
Click to expand...
Click to collapse
you dont install roms from your computer
you need to make sure you have CWM installed. you can do this with fastboot
fastboot this recovery on
http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.0-olympus.img
instructions can be found
http://forum.xda-developers.com/showthread.php?t=1204500
you download a rom to your phone and flash it through recovery. no computer needed at all after you have unlocked and flashed recovery on.
and is this do-able without an SD card installed? before i get halfway down the road and find im screwed XD also it seems i need to be rooted for CWM, though i still cant find a way to do it...
ishamm said:
and is this do-able without an SD card installed? before i get halfway down the road and find im screwed XD also it seems i need to be rooted for CWM, though i still cant find a way to do it...
Click to expand...
Click to collapse
did you actually read the post above????
you can fastboot the recovery image.
you DO NOT need root in order to do so.....
yes i did read it... while it might be obvious to you, some of us have no idea what were doing. loads of howtos include having to install the rom from a SD card. also CWM says "The SD Card needs to be mounted to use ROM Manager" so i dont think its too much of a stretch to think i need one
ishamm said:
yes i did read it... while it might be obvious to you, some of us have no idea what were doing. loads of howtos include having to install the rom from a SD card. also CWM says "The SD Card needs to be mounted to use ROM Manager" so i dont think its too much of a stretch to think i need one
Click to expand...
Click to collapse
you dont need rom manager....
you boot into recovery and install from there.......
A. download rom
B. transfer to phone's storage (if you download directly from phone, obviously skip this step)
C. boot into recovery
D. wipe data/factory reset (option in CWM recovery)
E. select option: install from sdcard
F. confirm
G. after flash is complete reboot your phone, you are now on a new rom.
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Neskobar said:
Hi there! I want to upgrade from android 6.0.1 to a newer, preferably the latest, version of android. I believe that is "A2017G-N-B09" as of the time of this post.
I downloaded A2017G-N-B09 (??) from the ZTE site, as linked in raystef66's thread. After putting it in the root of the SD card and running the update process, the phone rebooted as expected and said that the update was finished, but the android version is still showing as "6.0.1" (MiFavor is 4.0). The update shows in the update history but, as far as I know, nothing has changed at all.
After that, I looked around on the forums some more and saw someone mentioning that you might need to have Marshmallow B10+ before jumping into Nougat. So I downloaded MM-B11 from raystef66's thread, but the exact same thing happened.
Am I missing a step? Or am I using the wrong files to update? This guide mentions downloading the firmware (a separate file, apparently) before downloading and installing the update package. Is that what's missing for me?
I spent the last two days, since my new A2017G arrived, searching this forum (and google) for help with my issue, but haven't found any relevant solutions.
Many thanks in advance of any advice and help you might be able to offer me!
edit - I'm in the UK, if that makes any difference.
Click to expand...
Click to collapse
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Choose an username... said:
Can you try to install it again and read what the installation text on the recovery mode says? There's probably an error there.
Otherwise get an SD card, put the zip there, and go to the recovery (turn the phone off, and turn it on while holding volume up and power), then select to update from SD card and select the zip. If it fails or something, you'll have the text there, and you'll be able to write it down or whatever.
Also, what does the phone say on the back? Tell me what's the model as seen on the back. It might be an A2017 instead of an A2017G.
Click to expand...
Click to collapse
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Neskobar said:
Thanks for the quick reply. The model says A2017G on the back.
I just tried to install through the recovery mode, as suggested. It says, "Sorry, you can't sdcard upgrade".
Is this something I can work around?
Click to expand...
Click to collapse
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
raystef66 said:
For the record, the zip file from ZTE support has an update.zip in it. So once you've downloaded it, extract it and put the update.zip onto your intSD/extSD.
I didn't uploaded the "ready" A2017 N-B09 yet on DownloadCenter.
As for the MM-B11 from Downloadcenter : this is a zip you can use directly. Rename it to update.zip, put on SD and update within settings.
Hope that helps you out.
Click to expand...
Click to collapse
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Neskobar said:
Yep, that's what I did. Any idea why that didn't work then? I mean, it detected the "update.zip" when I had it on the SD card, and the 'update' appears in the history, but it clearly didn't install.
Click to expand...
Click to collapse
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
raystef66 said:
Strange.
Try to ADB sideload.
Also try to wipe cache in recovery. You'll never know.
Also try to rename to update.up and try again.
But then again, as you said the update was applying but nothing installed is at least weird. And also, when you tried to update through recovery and apply from SD, you couldn't is at least strange.
So try again with above steps.
BTW, where did you buy the phone ?
Click to expand...
Click to collapse
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
edit - I renamed the zip to "update.up" and couldn't get that to work either. It's not detected in the update section of settings, and I still get the same "Sorry, you can't sdcard upgrade" message.
edit #2 - I tried naming it to "update.up.zip" and it detected it this time, trying to run the update now.
Neskobar said:
I got the phone from Gearbest.
I'm trying to figure out how to do all this. I'm brand new to ADB, so I don't really know what I'm doing. I downloaded the android SDK, and the universal ADB drivers. The device is showing up, when I type "adb devices" and is responding to the "adb reboot bootloader" command, so it seems like it's set up ok.
So, the next step is to get TWRP on to the phone, right? I'm trying to follow the steps here, under the Fastboot Install Method (No Root Required) section, but it seems to be stalling at the "fastboot oem unlock" command. Just gets stuck at "waiting for device".
Sorry if this is all baby-steps. As I said, I'm really new to this and feel like I'm in a bit over my head. I'm happy to keep learning, though, as long as I'm not in real danger of destroying the phone.
Click to expand...
Click to collapse
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
raystef66 said:
No you dont require TWRP for that.
Put the update.zip in adb folder.
Just type adb reboot recovery ( in ADB) . It boots into your stock recovery. There you can apply adb sideload (dont know the actual text : "apply update from adb").
Check that on your phone. Then phone is waiting to your command.
Then type : adb sideload update.zip (or ota.zip)
Click to expand...
Click to collapse
Ah, I should have mentioned that. This is the message I'm getting when I try that:
C:\adb>adb sideload update.zip
loading: 'update.zip'
* cannot read 'update.zip' *
Click to expand...
Click to collapse
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Neskobar said:
Ah, I should have mentioned that. This is the message I'm getting when I try that:
Which is what made me think perhaps I needed TWRP on the phone. But, if that's all it should be, then I'm doing something else wrong...
Perhaps a driver is missing/not installed correctly? If that was the case though, how could I check? All the basic adb commands seem to be working fine and the phone is clearly responding to them.
Click to expand...
Click to collapse
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
raystef66 said:
You're doing ok.
When you can see adb devices with your phone's number you're ok.
So, adb devices / adb reboot recovery / adb sideload update.zip
Did you try to rename it to ota.zip ?
Btw, what version of MM are you running ?
Btw2, did you wipe cache/dalvik in recovery too ?
Perhaps you could root/bootloader unlock your phone (but you loose ota readiness ). And apply those system updates or install custom roms.
But again that's up to you.
There are threads about root/unlock your phone when on MM. Just look for it. If help needed just let us know.
Click to expand...
Click to collapse
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
raystef66 said:
Can you take a screenshot of your build number?
Go into settings /about phone and scroll down to bottom. Then take screen and upload it pls in attachment. Want to be sure what phone that you're on.
Click to expand...
Click to collapse
Ok, I attached it to this post, hope it works.
Neskobar said:
Ok, I attached it to this post, hope it works.
Click to expand...
Click to collapse
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Neskobar said:
Same problem when calling it ota.zip, " cannot read 'ota.zip' ". I'm trying to put A2017G-MM-B11 on there (although ultimately I want to get to A2017G-N-B09 if possible). My phone is on 6.0.1 currently.
Yea, I wiped the cache in recovery. Didn't seem to make any difference.
I'm not against rooting the phone or anything, but it just doesn't really seem necessary for my requirements, afaik.
Click to expand...
Click to collapse
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
raystef66 said:
AFAIK, you're on B11 right? Also security patches are from that date imo. So perhaps download the first nougat B01 and see what happens and report back.
But it remains strange that the nougat b09 is in your update history, right?
If this nougat B01 as a test does not work, you may consider to wipe your phone. First backup though.
Click to expand...
Click to collapse
Yes, that's what I was concerned about. The very first update i tried to install was N-B09, and everything else has been an older update after that, so maybe it won't overwrite the newer files, or something? Or possibly something else went wrong in the first update, so everything else just wouldn't work because of that?
I'm putting N-B01 onto my SD card right now, so I'll test that, and if it doesn't work I'll wipe the phone and start again. If I do need to wipe the phone, however, which update would you recommend trying first? N-B09? That might confirm if it was just bad luck on the first try, or whatever.
RobboW said:
Is it possible it was flashed in incorrect order of update and messed up partitionioning a little bit, leaving some data screwed up?
Click to expand...
Click to collapse
Agreed, that sounds like a possibility to me. I'll probably end up wiping and starting over.
Choose an username... said:
Are you sure you are putting the file where you are in cmd? If you write 'adb sideload o' and hit tab, does the name appear? If not, put the zip on C:/, then write 'cd..' with 2 dots on CMD until you get to C:/, and try again
Usually the problem is that adb will get out of memory or crash because of some random thing. But try that nonetheless
Click to expand...
Click to collapse
Yes the tab autocomplete works on the "u" of update.zip and "o" of ota.zip, when I tried both. I have to admit, I was quite excited to see your suggestion there, as I thought that would be a really easy way to confirm if something isn't right with adb, but never mind.
I still don't understand why it gives me this error then, though: * cannot read 'update.zip' *.
ramnkc said:
lol.... just check 1 more thing... the zip file you have downloaded should be extracted first... and its normally contains 2 files... one zip and pdf file... and if the that zip files is not name as update.zip then just rename it and copy to your root internal memory... then check updates and install the update... it should be running then.
Sometimes i have this silly mistake as well until i open the zip files and saw another zip file in the downloaded rom and realized it.
Click to expand...
Click to collapse
Thanks for the suggestion, and yes, I did confirm that I renamed the right zip file. That would have been easy thing to fix though, sadly.
edit - I tried the same adb commands with windows powershell too, and got exactly the same error messages.
What ROM was on it before you flashed B09?
Updating to N-B01 worked! I've no idea why this happened the way it did, nor why adb didn't work for sideloading, but I'm really glad that it finally worked.
The order of events:
1) Installed N-B09 via transfer to SD using the android updater, no difference in android version, but appeared in update history.
2) Installed MM-B11, same as above.
3) Tried various methods of installing MM-B11, including:
- SD transfer
- recovery mode SD update (which the phone wouldn't let me do, saying, "Sorry, you can't sdcard upgrade").
- ADB sideload (which never worked even slightly. I always got the message, * cannot read 'update.zip'/'ota.zip'/'update.up.zip' *)
- Tried the above methods with variously named zip files, including "update, ota, and update.up".
- Tried the above methods, but wiping the cache in between processes.4) Installed N-B01 via transfer to SD using the android updater. This time the process took a lot longer and after rebooting the phone, went through the process of optimizing apps, which it had never done before.
Ok, I think that's everything.
The only theory I can come up with is that: Something (I have no idea what, though) went wrong with the first update attempt and every subsequent attempt to update to an older version didn't work because it didn't want to overwrite newer android version files? That doesn't seem quite right to me, though, as I would assume that whatever is in the update.zip would just overwrite everything as standard, because the assumption would always be that these files are newer than the existing ones.
What would you recommend that I do next? Should I try to push through the latest N update now, then? Has this outcome helped you figure out what the problem was/is?
Whatever the case, I'm happy to finally get an update working. Thanks very much for all your help and suggestions, guys. It was much appreciated!