Related
Hey ive been trying to root my evo all day it is on version 2.1-update1. I was able to root my brothers perfectly fine using the downloads and tutorial from the idiot-proof guide to rooting by thebiles. But on mine I get stuck right at the beginning, when i try to flash the PC36IMG my bootloader says main version older. I feel like ive tried everything if anyone can help I'd reallly appreciate it thanks.
Try simple root, and keep trying. I got that same error even with simple root on my buddies 3 times before it worked. Don't know why. Maybe try copying the pc36img to the sd card instead of letting simple root push it...gl!
I agree with the simple root approach. Not trying to highjack your post but I have a question back at you if I may. You say you have one root EVO and one not root? If so the the root has PRI 1.34 and the nonroot 1.40? Could you perhaps do a data speed comparison on these and post the results? I am real curious...
sorry man i saw your post like 2 minutes too late the simpleroot worked right before i refreshed this page thanks for the help though guys appreciate it
one more quick question while PC36IMG was flashing the 2nd "tp" file said bypassed next to it rather than OK like all the others and the first tp had a blank next to it...is this a problem i should look into before unlocking the nand and all that other good stuff?
No problem glad you got it working. This was kinda like going to the casino...getting up to go to the bathroom...coming back to see someone hit the jackpot on your machine....hahaha!!!
That is normal....mine did that.
thanks man appreciate it...one more question for anyone that can help, im using the idiot proof guide and im on step 56 but when i try to enter the adb shell i get an error from command prompt saying "error: more than one device and emulator" i entered the shell perfectly fine like 2 steps before that and used it to flash the new pc36img rom but now i get this error to enter shell again how do i fix this error?
Okay I came here thinking this might finally be it... but nope I tried all the solutions mentioned here but to no avail. I am frustrated and still getting the main version is older. Does anyone know what is causing this error. Please I'm using usb debugging I wiped and backed my SD and have ota that came out in June. I installed Microsoft net frame and htc drivers. I updated simple root and the update log said this was to fix the error but still getting the same error. Any suggestions
I have the same issue, pretty much have tried everything with no luck, kind bummed at the moment, hope someone can help
Thanks
I got to work FINALLY!!!!!
So finally i got the main version error older NO MORE. So i decided to share what i did in hopes that it will work for all of you frustrated out there.
1) Download simple root from xda forum, dont download it anywhere else. The first time i tried i downloaded it at another android forum and even though it may seem the same, this version for some reason was not pushing the files as it suppose to. So again download from forum. Search for it on XDA.
2) Be patient and prepare yourself.
3) Make sure you on the 147 ota version. Not froyo. or before any version before ota because you can use old simple root.
4) After you download it extract it to a folder. Choose whatever location suits you i like desktop so i can delete file after i use it and keep zip. Be sure to update the program. Open it and let it search for downlaod or go to root folder and search for the updater.
5) Before running the program check the obvious. Is usb debugging enable, Do i have microsoft netframe, Are my phone drivers correct. Is the usb cable correctly connected to my computer and phone. Did i choose charge only when connected to the computer.
6) Now on your phone, and this step did it for me, go to Settings>SDandPhoneStorage>FactoryDataReset. Brace yourself this will wipe data it will not change your version. But if you want do a backup the folder of your contacts and whatever you have in your SD card, this is the time to do so. Mount as disk drive, and remember to change back to CHARGE ONLY. I skipped this because rooting was more important than my girlfriends phone number.
7) Now youre noobiness is ready connect phone double check Step 5. In case you missed something.
8) Run the simple root downloaded from XDA forum. Wait for it to push files is wont take long but me patient. Think of it passing 180mb to sd card so it takes some time.
9) Phone will reboot in a screen with skating androids Push power button and WAIT. It will find file and you shouldnt be getting "main version older" reboot error you where getting if you paid close attention to detail. Now update push volume up.
10) Why so impatient wait for it to update files. Once its down just push volume up for reboot. First time it reboots after root or when u flash a rom it usually takes longer, enough to get u nervous but dont be WAIT.
11) Easy sailing now but youre not done yet. Hit recovery once your phone reboot. Choose the method you want i chose Clockwork it works just fine for flashing roms.
12) Congrats your fully root and can flash that cool rom youve been reading about. Suggestions: DamageControl or Cyanogen but go ahead and try whichever you like.
13) YOURE DONE WOOF
If for some reason, it happened to me with AvaFroyo, when you flash your rom it goes on a loop and keeps rebooting dont panic that is what the recovery is for just put your microSD on a card reader delete the rom that is giving you problem and place another one and Reflash. Read how to flash rom you have to wipe on Recovery menu everytime you flash a different rom.
I hope this helps...Its in plain english not Dev English so...
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
hortstu said:
Thanks for taking an interest in my problem and trying to help.
Here's what I've figured out. I tried doing Toast's root method for linux and the directions weren't idiot proof because I screwed them up. I've explained how far I've gotten in other threads. If that's relevant just ask and I'll explain exactly what I did.
Anyway my phone does the basics. It allows me to make phone calls, text, and look at the internet on the phone so this isn't an emergency but it I am worse off than I was before I tried to root because I can no longer use easytether.
I had no problem with easytether prior to the root attempt, and it still works when I hook it up with my wifes untampered evo. with my phone but with my wife's evo, I've never messed with that one, I have no trouble connecting with easy tether.
Some of the things I've noticed about the device since the attmept...
-I can't update to 2.2 via the OTA or any other method, my device says no updates are available.
-Simple root wasn't so simple, the phone never shut off and rebooted into boot screen like the red screen said it would in step 1.
How do I reset the device to the way it was the day it was purchased. I've got everything I need backed up. I'm ready to reset just tell me how.
Thanks.
Click to expand...
Click to collapse
I bet a friend told you about root without giving you all the details, right? Haha. Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
jadehawk said:
what ROM are you running? base on eclair 2.1 or froyo 2.2..
try this http://shipped-roms.com/index.php?category=android&model=Supersonic
They are the Stock Unmodified ROMs for your EVO 4G the first 3 are Eclair (2.1) and the last 2 are Froyo (2.2)
Just know that if you use any of this you will LOSE Root..
Hope it helps..
I recomend you try 1.47.651.1 first ...
Good Luck
Click to expand...
Click to collapse
I never got to the point where I could flash a ROM or got root. S was never off.
just in case it makes a difference.
firmware= 2.1-update1
baseband version= 1.39.00.04.26
kernel version= 2.6.29-a2443432
build#= 1.32.651.1 CL171253 test-keys
software#= 1.32.651.1
I think the rest is up to date.
I bet a friend told you about root without giving you all the details, right? Haha.
Click to expand...
Click to collapse
Actually I'm a bit of a forum junkie and as soon as I got this phone I found the android forums and have spent a ton of time there trying to maximize the utility of this device. I've done the opposite.
Ok, back to business. Rooting will make it impossible to receive ota updates. This is not a problem, because devs post rooted ota updates that you can flash manually. As far as I know, root is 100% permanent, but you don't know the goods. First of all, search wireless tether root in market it should have a green wifi icon. Second, try some custom roms and themes. I bet you will cry when you see yourself asking to go back to stock....
Click to expand...
Click to collapse
I only want to go back to stock so I can get rooted! I can't root because I can't get 2.2 so I can't use unrevoked 3.21. I can't use simple because of some problem I had with the toast linux method that seems to be screwing up everything since. I appreciate the input I hope I've explained myself better.
hortstu said:
Please?
I know it bothers people here when they think someone didn't research anything first but I really did. The problem was I'm on linux so most of the stuff I researched didn't seem to apply, not to mention I'm quite illiterate in the terminal... but working on it. I'd really like to get this phone back to stock so I can try again.
Can anyone help?
Click to expand...
Click to collapse
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
The problem is I don't think I'm rooted.I flashed pc36img.zip and never made it any further. Am I rooted. Do I need to undo this or can I do a hard reset?
grouse130 said:
Use this to go back to stock: http://forum.xda-developers.com/showthread.php?t=780141
Click to expand...
Click to collapse
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
Power off the phone and reboot into the recovery by holding VOL DOWN + POWER until it boots to the white screen. Then select RECOVERY.
Click to expand...
Click to collapse
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
hortstu said:
OK so here's why I think I'm not rooted, when I follow step one of the detailed directions,
I get a screen with an evo, a red triangle, and a red exclamation point.
Where do I go from here?
Any direction will be immensely appreciated.
Click to expand...
Click to collapse
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Have you flashed a recovery img?
Sent from my PC36100 using XDA App
rugedraw said:
From this screen, if you hold volume up and press the power key, it will take you to the hboot menu.
Click to expand...
Click to collapse
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
hortstu said:
OK so I'm at the "hboot" screen.
Code:
Android system recovery <2e>
Use volume...
click power key...
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Then in yellow, below the device picture, triangle, and exclamation I have
Code:
E: Can't open /cache/recovery/command
Not sure where you're steering me rugedraw but thanks for the help...
Click to expand...
Click to collapse
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
To find out if you're rooted, simply try to run an app that requires root access. Try downloading Titanium back up, and as soon as you install it, hit the "Problem?" button on the lower right and install busybox. One of the first lines on the main screen of the app says:
Root access => OK (Busybox 1.16.0 from app)
If it does not say "root access => OK" and you cannot use the app, then you don't have root.
Click to expand...
Click to collapse
Finally went back and checked on the titanium backup download. When I first opened it I got the message that it didn't have root access. So I clicked on "problems?" and installed busy box. Now it says,
Root access v=> OK (BusyBox 1.16.0 from app
Click to expand...
Click to collapse
Plus some other stuff... so I guess I have root but not S-off.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
Click to expand...
Click to collapse
Should I still do this or is the info from titanium backup enough?
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Yes I tried doing that but like I said I'm on a linux computer and had some trouble with the steps. What I'd really like to do is just go back to stock and try rooting with unrevoked 3.21.
My concern is that selecting factory reset from the hboot screen won't take me back there. If it did I could probably get the 2.2 update over the air, I suppose now I have to worry about getting this other update that everyone is talking about at the same time. Can I get 2.2 and avoid the update that came out last night? How.
Will a factory reset get me back to stock? I've already got everything backed up that matters.
Thanks for all the help.
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
hecklbrg said:
OK...I think this should work for you:
go here and download the file on the page:
WRONG FILE>>>WILL FIND THE CORRECT ONE.
rename it update.zip and put it on the root of your SD card.
Boot into HBOOT then into recovery and go to apply update.zip -- choose the file you put on there.
let it run and you should have the stock non-rooted version of the 1st software release from sprint. from there you can update it as far as you want to root it the method of your choice.
Click to expand...
Click to collapse
Thanks hecklbrg,
I assume since I'm half rooted a factory reset won't get me there?
I'll wait for the link to that file...
if you put this on your card and run it from HBOOT...you will get a rooted version of the latest sprint OTA with a custom recovery and the latest radios.
http://forum.xda-developers.com/showthread.php?t=791019
I'm still looking for a non-rooted version to run...but I would think this would work for you to get you the latest OTA in a rooted form.
Second thing is that I don't think you really screwed up your root process. You have only done part of the process and haven't installed a custom recovery. If this works for you, it will give you a custom recovery and you will have a fully rooted phone.
Hecklberg is right. I don't think you even need to rename it update.zip. If its a
pc36img.zip your hboot will automatically scan for it, find it and run it when you put it on your SD card and open hboot.
Also consider, I rooted my phone without any computer, all done from my Evo, using fastRX8 thread in here about how to root for newbies. It involves putting the files on your SD card, then installing terminal emulator from the market and typing a few commands to install flash_image, then custom recovery. You are root, just don't have flash image, custom recovery, and superuser yet. Basically toast part 2, it can be done with no computer, but same files.
Read real quick Whitslack thread on rooting, and fastrx8 thread, even just the 1st post, and it will make sense to you where you're at and what's left to do. You'll see how close you are.
Once root, and superuser installed, you won't need easy tether, Android wired tether is what I use (doesn't require installing any software on the host pc)
(Actually, if you use the threads I mentioned method, don't use the recovery amonra1.7.0.2, there's a newer one to download, its at 1.8 now, just Chang the recovery file name you type in terminal app accordingly-don't worry, it won't go thru if you do it wrong, but won't 'break' anything)
Hope any of this helps, but yeah, hecklberg is right too, just different methods. One requires no computer.
And yeah, with the devs around here, you don't need any Sprint OTAs, most of the time, they seem to have em available before Sprint releases them. These guys are good.
scottspa74 and hecklbrg,
Thanks for the help. I havent had time to look at this or act on it over the last 24 hours but I will try to get to it tonight and let you know how it works. Sounds like you've gotten me out of the woods.
Thanks again.
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
hecklbrg said:
To check if you are rooted. Download "Terminal Emulator" on the market. If it starts up and when it is done booting, you get a # prompt, you are rooted. If you get a $ prompt. You are not rooted.
You also do not have a custom recovery installed on your phone (the recovery screen you have is the stock one). Try finishing up the process by doing Toast part II -- http://forum.xda-developers.com/showthread.php?t=701835&highlight=Part-2
Click to expand...
Click to collapse
Sent from my netarchy_toast, froyo beast of a machine evo!
evohack99 said:
I think it is $ if you are rooted and# if you aren't because I know I'm rooted and it shows money signs, unless terminal emulator is messed up,i have nvr used it.
Sent from my netarchy_toast, froyo beast of a machine evo!
Click to expand...
Click to collapse
Nope you are incorrect my friend.. try typing " su " on the terminal emulator see if you get the "#" ... # ==> Root and $ ===> User(I Think) But I know for sure "#" is root access
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Do you have htc sync installed? It won't work unless you have the actual htc sync suite installed. Just google it won't cost you anything. I semi bricked my phone but I fixed it. Maybe some things I done in this thread could help you. Just skim through a few of my posts'.
http://forum.xda-developers.com/showthread.php?t=1100781
Sent from my PC36100 using Tapatalk
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
My last tip would be to put the phone in fastboot and then run the 3.29 ruu exe. It worked for me, here's the link. Just make sure you have htc sync installed and it's not running when u try to run the ruu (from fastboot in bootloader).
http://goo-inside.me/supersonic/sto...0.09.01_NV_1.77_CNV_release_150224_signed.exe
Sent from my PC36100 using Tapatalk
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
Was the phone rooted when he updated. In Hboot does it say s-off. If so try running the pc36img.zip of amon ra and see if you can get a recovery image back on the phone to work out of.
lokoalex said:
So my brother tried to update his Evo with the official update. For some reason his Evo is bricked. He went and decided to switch companies and get an iPhone and gave me his Evo.
When i turn it on its on an infinite reboot. Only thing i can get to is the bootloader menu (holding the power and up key or the other menu with the down key key). Im new to this and dont know if I should just tank it. Im pretty sure there is a way to make it come back to life so if someone can offer any help I would appreciate it.
Some technical notes.
1.) I installed the usb driver so my desktop recognizes it.
2.) I tried updating it in fastboot usb mode using the RUU Supersonic 1.32.651_Radio_1.39.00.04.26_release_171253.
It looked like it was working. It asked me if I wanted to update(better yet downgrade) from Image version 4.22.651.2 to Image version 1.32.651.1. It rebooted the device it said it was erasing the user data, then it said it was sending then updating signature........then it tanked and says ERROR[140]:BOOTLOADER VERSION ERROR The ROM Utility cannot update your Android phone. Please get the correct ROM Update Utility and try again.
I dont know how to root i dont know how to hack. I just want it to work. Please let me know how to get it fixed. Im tired of my blackberry.
3.)I tried to do the PC36IMG thing and I dont know what its supposed to do. But when it goes to read it I get a PC36DIAG.zip cannot be found or missing and a PC36Diag.n something missing.
Thanks
Click to expand...
Click to collapse
The RUU you used is pretty old, I would try a newer one, such as the 3.70 software. What version is your hboot, and is it S on or S off? Where is it bootlooping at? (the white HTC EVO 4G screen, or the actual boot animation?)
I selected the old one because that one never gives me issues, the 3.30 and 3.70 never work for me
Sent from my PC36100 using Tapatalk
k2buckley said:
The RUU you used is pretty old, I would try a newer one, such as the 3.70 software. What version is your hboot, and is it S on or S off? Where is it bootlooping at? (the white HTC EVO 4G screen, or the actual boot animation?)
Click to expand...
Click to collapse
My hboot is: HBOOT-2.16.0001
S-ON
Its bootlooping at the white HTC EVO4 screen.
Any ideas.
I have tried RUU:
3.26.651.6
3.29.651.5
3.29.651.6
3.29.651.5
3.70.651.1
The only one that actually does anything is 1.32.651.1 The rest just fail giving me an ERROR [170]: USB CONNECTION ERROR. Could be because HTC sync cant install the driver. How Can I get that driver installed. Could it be my OS?
lokoalex said:
My hboot is: HBOOT-2.16.0001
S-ON
Its bootlooping at the white HTC EVO4 screen.
Any ideas.
I have tried RUU:
3.26.651.6
3.29.651.5
3.29.651.6
3.29.651.5
3.70.651.1
The only one that actually does anything is 1.32.651.1 The rest just fail giving me an ERROR [170]: USB CONNECTION ERROR. Could be because HTC sync cant install the driver. How Can I get that driver installed. Could it be my OS?
Click to expand...
Click to collapse
I would try running the RUU as a PC36IMG, if you haven't already. Download PC36IMG of the RUU you wish to use, and put it on the main directory of your SD card. Then boot to the bootloader, and let it detect the PC36IMG. It should scan it, then ask you to update. Select volume up for yes, and let it run it's course. Perhaps that method will work out better for you.
Dirk, thats odd that you get errors on the new RUU's. Sometimes if the hboot and radios don't match up the RUU won't run.
EDIT: And yes, you definitely could be getting that error (most likely are) because HTC won't install the driver. You need to get that installed. I would still just try the PC36IMG though.
A1Lonestar said:
Was the phone rooted when he updated. In Hboot does it say s-off. If so try running the pc36img.zip of amon ra and see if you can get a recovery image back on the phone to work out of.
Click to expand...
Click to collapse
The phone was not rooted. I dont even know how to do that. LOL. I will try that pc36img file.
lokoalex said:
The phone was not rooted. I dont even know how to do that. LOL. I will try that pc36img file.
Click to expand...
Click to collapse
Just make sure that the file is named PC36IMG.zip (exactly that).
Sorry but I have to ask why your friend didn't bring it right to sprint and get them to fix it they would have replaced it in a second for a bad upgrade?
Sent from my PC36100 using XDA App
k2buckley said:
Just make sure that the file is named PC36IMG.zip (exactly that).
Click to expand...
Click to collapse
I ran it. It scanned it checked it and then nothing. Goes right back to the screen where it asks you to choose fastboot, recovery, ......
I did notice that my battery needs charging. Im gonna try again when the battery has some juice.
Also got HTC sync installed on my Windows & machine.Will give it a try too.
linsalata28 said:
Sorry but I have to ask why your friend didn't bring it right to sprint and get them to fix it they would have replaced it in a second for a bad upgrade?
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
My brother is impulsive and he didnt like the fact that it bricked on him. If it was me I would have definitely taken it to sprint.
You could try this don't know if they will or not but I'm kind of cool with some guys at one of those little stands in a mall now they are sprint but not really they helped me with an old phone I was having problems with that wasn't activated they don't really care and they have the tools to fix things but the one I go to like to show me just how much they know about androids witch isn't much LOL.
Might be worth a shot you might find a guy thats into moding and would like to show off.
Sent from my PC36100 using XDA App
linsalata28 said:
You could try this don't know if they will or not but I'm kind of cool with some guys at one of those little stands in a mall now they are sprint but not really they helped me with an old phone I was having problems with that wasn't activated they don't really care and they have the tools to fix things but the one I go to like to show me just how much they know about androids witch isn't much LOL.
Might be worth a shot you might find a guy thats into moding and would like to show off.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Not a bad idea. Might have to find some of those guys.
k2buckley said:
I would try running the RUU as a PC36IMG, if you haven't already. Download PC36IMG of the RUU you wish to use, and put it on the main directory of your SD card. Then boot to the bootloader, and let it detect the PC36IMG. It should scan it, then ask you to update. Select volume up for yes, and let it run it's course. Perhaps that method will work out better for you.
Dirk, thats odd that you get errors on the new RUU's. Sometimes if the hboot and radios don't match up the RUU won't run.
EDIT: And yes, you definitely could be getting that error (most likely are) because HTC won't install the driver. You need to get that installed. I would still just try the PC36IMG though.
Click to expand...
Click to collapse
I've been trying man. Im getting nowhere with this. I tried the RUU 3.70 and it just crashed asked me if I wanted to debug. So im gonna try one of the older versions. At least its seeing these with the HTC sync working.
lokoalex said:
I ran it. It scanned it checked it and then nothing. Goes right back to the screen where it asks you to choose fastboot, recovery, ......
I did notice that my battery needs charging. Im gonna try again when the battery has some juice.
Also got HTC sync installed on my Windows & machine.Will give it a try too.
Click to expand...
Click to collapse
Yea, I would either try an RUU again now that you've got HTC Sync installed, or format your SD card, and put ONLY the PC36IMG on there, then try it again. The only time I've seen a PC36IMG file not ask you to update is if the card needed to be formatted for one reason or another.
k2buckley said:
Yea, I would either try an RUU again now that you've got HTC Sync installed, or format your SD card, and put ONLY the PC36IMG on there, then try it again. The only time I've seen a PC36IMG file not ask you to update is if the card needed to be formatted for one reason or another.
Click to expand...
Click to collapse
I tried the RUU again and it gotas far as the signature and then it crapped out again.
Error [140] BOOTLOADER VERSION ERROR.
Have no idea what the problem could be. Gonna try reformatting the card one more time and see what happens. So frustrating!!!
Maybe try to update or downgrade your hboot version.
Sent from my PC36100 using XDA App
*Assuming you're working on a windows machine*
Go to this site http://shipped-roms.com/index.php?category=android&model=Supersonic
and download ruu 3.70.
Without your phone connected, run the ruu until it gets to the first dialog box (it should have a checkbox that says "I understand the caution..." blah blah).
With this dialog still open, go to start > run and type "%TEMP%" without quotes.
Inside this folder look for a file called "rom" or "rom.zip" (you are going to have to go through all subfolders) depending on your windows settings (Hide extensions for known file types).
When you find it move it to your desktop and rename it to "PC36IMG" or "PC36IMG.zip" accordingly.
Get a card reader and take your sdcard out of your phone and place it in the card reader. Place the PC36IMG file you renamed on the root of the sdcard. Install your sdcard back into the phone and boot into bootloader. This should scan the card and find the PC36IMG and reinstall a bone stock non-rooted 2.2 rom.
If this method fails, it's possible the nand may have been corrupted in the update process. I'm better at troubleshooting if I have the device with me so this is the best I can do.
lokoalex said:
I tried the RUU again and it gotas far as the signature and then it crapped out again.
Error [140] BOOTLOADER VERSION ERROR.
Have no idea what the problem could be. Gonna try reformatting the card one more time and see what happens. So frustrating!!!
Click to expand...
Click to collapse
That is frustrating. It sounds like there may be a problem with your current boot.img, and maybe that's why it won't let the RUU re-write the boot.img when it's trying. That would also explain you not being able to boot, because if your bootloader is corrupted somehow, then you won't be able to get anywhere at all. Unfortunately, the bootloader you're on (HBOOT-2.16)isn't downgradeable. I'm starting to suspect that you're getting the bootloader version error because when you run the older RUU, it will try to flash an older version of hboot. Since the version you're on is NOT able to be downgraded, it's probably erroring out when it tries to downgrade, but it can't. I would suspect that if the RUU for the 4.22 software was available and you were able to run that one, then it would succeed. The problem is that you're trying to downgrade, and you can't do that. I'm not sure what went wrong when the OTA was accepted, but it seems like something did, and now you're stuck. I would guess that the only way to fix it would be to reflash the OTA (which you can't because you can't boot), or run the RUU for 4.22, which isn't available yet. My speculations may not be accurate, but that's my guess!
I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil
vpporter said:
I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Not sure which technique you used to root. Did you also install the Google play store? If so, it sounds like you installed the wrong gapps.
I would boot to twrp and install the 1011 gapps.
Sent from my One X using xda app-developers app
NABI 2 Keyboard Problem
GuyIncognito721 said:
Not sure which technique you used to root. Did you also install the Google play store? If so, it sounds like you installed the wrong gapps.
I would boot to twrp and install the 1011 gapps.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi There,
Unfortunately I can only get to the Nabi Set-up screen. I can't get to the TWRP screen. I can't enable developers options (USB Debugging) as I cant get into the device (This I think is the biggest problem as I cant see the NABI through PDA net and can run any recovery apps from SD as developer option is not enabled). I seem to be stuck in a loop and not sure where to go from here!
Any help or thoughts much appreciated.
Thanks
Virgil
vpporter said:
Hi There,
Unfortunately I can only get to the Nabi Set-up screen. I can't get to the TWRP screen. I can't enable developers options (USB Debugging) as I cant get into the device (This I think is the biggest problem as I cant see the NABI through PDA net and can run any recovery apps from SD as developer option is not enabled). I seem to be stuck in a loop and not sure where to go from here!
Any help or thoughts much appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app
GuyIncognito721 said:
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi,
Thanks for that. I now have access to TWRP and though I would be OK. However when I try to install GAPPs or a Keyboard zip file it continuallys comes up with this error:
E: Unable to mount '/data' (tw_mount)
E: failed to mount /data (Invalid argument)
E: failed to mount /data (Invalid argument)
Any thoughts on this one? It seems to be related to SD card but I have tried a couple to no avail. Can the tablet reject SD cards?
THanks again for your help.
Virgil
vpporter said:
Hi,
Thanks for that. I now have access to TWRP and though I would be OK. However when I try to install GAPPs or a Keyboard zip file it continuallys comes up with this error:
E: Unable to mount '/data' (tw_mount)
E: failed to mount /data (Invalid argument)
E: failed to mount /data (Invalid argument)
Any thoughts on this one? It seems to be related to SD card but I have tried a couple to no avail. Can the tablet reject SD cards?
THanks again for your help.
Virgil
Click to expand...
Click to collapse
have you tried going into the MOUNT sub-menu and trying to mount the data partition?
Sent from my One X using xda app-developers app
GuyIncognito721 said:
have you tried going into the MOUNT sub-menu and trying to mount the data partition?
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Hi There,
That seemed to work and I now have GAPPS installed and the keyboard working. Unfortunately the only problem remaining is that Wi-Fi is not working. It previously seen my Wi-Fi connection point and now it will not turn on i.e. I try to switch on Wi-Fi but it keeps going back to the Off position? Very strange. I'm on Android 4.0.4 and have tried the change in Mammy and Daddy mode! I appreciate your help with this and don't want to take up your time so I may post this issue under a new heading.
Thanks again for all your help and giving me the solution.
V
vpporter said:
Hi There,
That seemed to work and I now have GAPPS installed and the keyboard working. Unfortunately the only problem remaining is that Wi-Fi is not working. It previously seen my Wi-Fi connection point and now it will not turn on i.e. I try to switch on Wi-Fi but it keeps going back to the Off position? Very strange. I'm on Android 4.0.4 and have tried the change in Mammy and Daddy mode! I appreciate your help with this and don't want to take up your time so I may post this issue under a new heading.
Thanks again for all your help and giving me the solution.
V
Click to expand...
Click to collapse
Hope you updated the tablet software to 1.9.37 before you did everything or you will be starting over from scratch
Sent from my cm_tenderloin using xda app-developers app
When I first rooted mine, probably some time in late Feb the consensus seemed to be to install the latest OTA software upgrade before rooting in order to avoid WiFi problems. I did this and I have not had WiFi problems. Just recently there has been yet another software and interestingly the bullet point summary of what has changed claims fixes for WiFi issues.
To install the upgrade from the rooted state you need to:
* Use the TWRP recovery to restore the backup you took when rooting to return the main OS to stock.
* Use adb fastboot flash to restore the original recovery.
* Boot normally, connect to WiFi, parent mode, settings/about/update and download/install the update.
[The OTA update works by downloading a file which is then installed by the stock recovery in a reboot cycle.]
* Use adb fastboot flash to flash TWRP recovery.
* Use TWRP recovery to backup the latest stock, install root.zip and gapps.zip.
There is more than one version of TWRP and I found the older one worked for me and the newer one had touch screen problems but you may find otherwise. The various versions are discussed here: http://forum.xda-developers.com/showthread.php?t=2074501
HELP
GuyIncognito721 said:
Hope you updated the tablet software to 1.9.37 before you did everything or you will be starting over from scratch
Sent from my cm_tenderloin using xda app-developers app
Click to expand...
Click to collapse
I see you helped this other person and hope you can me too. I like they did, followed the youtube video on how to root and install google play. It worked great when I did this last year on my kids nabi. I tried to do it again this year with a friends and kinda fell into a hole. My keyboard stopped work as well. I went back and tried to fix it by putting the gapps 1011. Well I didnt delete the old one (didnt know how) and now I cant get into TWRP. I have tried getting the recovery kernal and now when I push vol + it starts to load then gives me the dead android guy. Any suggestions on how to fix this. I sure hope so. Thanks
vpporter said:
I followed a utube instruction to route Nabi 2 however I ran into a problem with keyboard, the error message that came up is: "Unfortunately, Android keyboard has stopped". I could not enter any text. At this point I was in child mode and could not get access to Mommy mode to allow me to change settings. I decided to do a factory reset thinking it would clear keyboard error...it didn't. When you do a factory reset it brings you to set-up screen that needs text entry which I cant do. I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks
Virgil
Click to expand...
Click to collapse
Uncheck signature enforcement or whatever it's called in TWRP?
Rooted Nabi JR with wrong Root
I have been working on my step-sons nabi for a week now. I rooted three Tabeos fine but then i thought i could do the Nabi JR and it would go perfect...i was wrong. I accidently rooted it with the same package for the Tabeo and now when i boot it up the keyboard forces close and i cant do anything. I can not get to daddy mode, can not usb debug. there is no TPK or whatever installed to boot with. Im at a loss, all i can do is load from usb in the stock bootload menu but i cant seem to get it to work. I need help please...i voided the warranty and now he has no nabi! this is also the Nick JR version of the Nabi, i cant be sure what else is in it considering im stuck at the enter daddy password and no keyboad...
d.marie.1490 said:
I have been working on my step-sons nabi for a week now. I rooted three Tabeos fine but then i thought i could do the Nabi JR and it would go perfect...i was wrong. I accidently rooted it with the same package for the Tabeo and now when i boot it up the keyboard forces close and i cant do anything. I can not get to daddy mode, can not usb debug. there is no TPK or whatever installed to boot with. Im at a loss, all i can do is load from usb in the stock bootload menu but i cant seem to get it to work. I need help please...i voided the warranty and now he has no nabi! this is also the Nick JR version of the Nabi, i cant be sure what else is in it considering im stuck at the enter daddy password and no keyboad...
Click to expand...
Click to collapse
Which Nabi JR? There are 2 versions. 4GB with tegra 2, or 16GB with tegra 3. Makes a difference in how we can help you. Probably need to put TWRP on device and restore a stock ROM. Then use TWRP to root it.
are the ROMs out there? I didn't see anything on the wiki page
http://forum.xda-developers.com/wiki/Fuhu_nabi_Jr
I have to admit though, I don't follow the Jr very much, so for all I know the ROMs are all over the place.
need to fix nabi JR
how can i get twrp without entering debug mode..i cant even get into the nabi to get debug on...i can only access bootloader
aicjofs said:
Which Nabi JR? There are 2 versions. 4GB with tegra 2, or 16GB with tegra 3. Makes a difference in how we can help you. Probably need to put TWRP on device and restore a stock ROM. Then use TWRP to root it.
Click to expand...
Click to collapse
2girlzdad said:
are the ROMs out there? I didn't see anything on the wiki page
http://forum.xda-developers.com/wiki/Fuhu_nabi_Jr
I have to admit though, I don't follow the Jr very much, so for all I know the ROMs are all over the place.
Click to expand...
Click to collapse
I think the 16GB tegra 3 is posted. Maybe the TWRP thread? Can't remember. Mr. Karz usually helps people that need the Nabi JR 4GB tegra 2. I think I have both ROM's but they aren't my creation and I don't have the devices to test so I don't post them.
d.marie.1490 said:
how can i get twrp without entering debug mode..i cant even get into the nabi to get debug on...i can only access bootloader
Click to expand...
Click to collapse
You would use fastboot to flash TWRP from the bootloader. That's why I asked which Nabi you have. 2 different TWRP versions, and the tegra3 version has a locked bootloader, so you have to wipe the device to unlock the bootloader to install TWRP.
break it down for me
can you break that down on how i do that. i deleted everything out of it its in stock but keyboard does not work to access anything, i know its still rooted but i dont know how to fix it.
aicjofs said:
I think the 16GB tegra 3 is posted. Maybe the TWRP thread? Can't remember. Mr. Karz usually helps people that need the Nabi JR 4GB tegra 2. I think I have both ROM's but they aren't my creation and I don't have the devices to test so I don't post them.
You would use fastboot to flash TWRP from the bootloader. That's why I asked which Nabi you have. 2 different TWRP versions, and the tegra3 version has a locked bootloader, so you have to wipe the device to unlock the bootloader to install TWRP.
Click to expand...
Click to collapse
Hey guys, this is my last attempt to fix my sons nabi. It has the same issues as the original poster. I basically cant get anything to work on it.
GuyIncognito721 said:
Turn off the device. Power on the device by holding the power and volume up. At the option menu press volume down to get to recovery kernel and press volume up. This will get you to twrp.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
When I follow these steps it goes to the android with the red exclamation point. I can't access the Nabi with my laptop. only a sd card. Is there anything I can do to save this thing? Thanks to anyone with advice and sorry for the thread necro but it was relevant.
nitetimemc said:
Hey guys, this is my last attempt to fix my sons nabi. It has the same issues as the original poster. I basically cant get anything to work on it.
When I follow these steps it goes to the android with the red exclamation point. I can't access the Nabi with my laptop. only a sd card. Is there anything I can do to save this thing? Thanks to anyone with advice and sorry for the thread necro but it was relevant.
Click to expand...
Click to collapse
What version of the Nabi software were you on? Was the tablet stock or had you rooted it, gapps, etc? Can you boot Android but just the keyboard doesn't work? Or are there more issues besides the keyboard. Are your just trying to fix the one problem or are you trying to wipe the device and start fresh?
Likely you will need to get TWRP on the tablet, or at least be able to boot to TWRP. Answer those questions and I can have a better idea of what we can do.
aicjofs said:
What version of the Nabi software were you on? Was the tablet stock or had you rooted it, gapps, etc? Can you boot Android but just the keyboard doesn't work? Or are there more issues besides the keyboard. Are your just trying to fix the one problem or are you trying to wipe the device and start fresh?
Likely you will need to get TWRP on the tablet, or at least be able to boot to TWRP. Answer those questions and I can have a better idea of what we can do.
Click to expand...
Click to collapse
The Nabi wouldn't take the latest update and it was apparently rooted to gain access to the google play store. It now appears the OS and everything else has been erased. I told my wife I would take a look at it and I immediately regret that decision, this is beyond my scope.
The only thing i have been able to access is the android screen which gives me access to the sd card. My laptop does not recognize it. I found this thread after a lot of searching and reading, some of the nabi threads are insanely long, and when I googled 'signature verification failed' to see if I could find someone stuck at the same point I am,
"I've been advised to return it to stock but when I try run the return to stock zip file (filed is called fuhu_nabi2_back_to_stock_from_scratch) via SD card it comes up with this message:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:signature verification failed
Installation aborted
Any help with this would be appreciated.
Thanks"
Everything I have tried to run from the sd has returned this message. There's no keyboard, there's only the android screen. Anything else I try to do just freezes it. I was hoping to get it back to stock and let it update itself. So I guess the first thing I need to do I figure out how to get twrp on it.
hello
i have rooted the device using the "1 CLICK ROOT TOOL" and now i have the dead android bot with error when i enter recovery.
i have tried the "fastboot erase cache" command at fastboot mode but it did not help
is their a way to fix it?
Try pressing Volume + key and Power. Don't hold just press. It might take a few goes to get it right. I had the same problem. That means that the update you have downloaded (saved on your system) fails to install.
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
koby058 said:
hello and thanks
i can enter recovery by pressing the keys. this is not the issue
its just that i want to completely solve the problem
Click to expand...
Click to collapse
Awh sorry, I thought you can't get into recovery.
Try sideloading the stock Firmware. Go to official ASUS website and download it from there. It's about 1 GB. On this website you can find instructions on how to do it. http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 Section 3.2)
After that you can download OTA updates and install them using method described here http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835, "Steps to Apply OTA manually".
OTA can be downloaded from there (look at the later posts for newer OTA) http://forum.xda-developers.com/zenfone2/general/ota-links-stock-rom-t3093999
I had a very similar problem few days ago. That solved it. Had a similar problem a few days ago coz I messed up my build.prop
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
koby058 said:
hello
i have already did a "adb siedeload" for the stock rom downloaded from the asus web site but the issue remain.
also i downloaded the latest ota, and "adb sideloaded" them as well. it worked flawlessly .
but the small thing with the recovery is annoying.
i thinking about looking inside tmp directory and delete something called "last update"
what do you say?
Click to expand...
Click to collapse
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
rlaw said:
You're not understanding because the information he gave you is slightly wrong. When you try to enter stock recovery it will ALWAYS say installing update and pop up an error Android bot. It's not about having some update data somewhere that fails to install properly. It will ALWAYS do that. That's normal.
Click to expand...
Click to collapse
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
NiKiToS-04 said:
Owh, this is embarrassing. I was playing with it a lot and I was kind of sure that if you have a working installed update, which is the same as a zip of an OTA update you have on an SD card it will skip installing the update and go to recovery without an error, but I was very very wrong. I'm very sorry for missleading you, and I've learned something new. Thank you.
Click to expand...
Click to collapse
No worries, I've made the same mistake before. We've all been there, still learning new things about this phone after months of using it!
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
koby058 said:
ok let me tell why i begin asking about it.
when i just got the phone i update all of the ota updates and after that i rooted it with "1 CLICK ROOT TOOL" .
two days ago i receive tha 2.20.40.58 ota . i downloaded and install but the instalation failed .
so i unroot it with "1 CLICK ROOT TOOL" and then i checked for update . but there was no update.
so i assumed the problem is because of the recovery issue.
the qustion is why i cannot install ota automatically ?
Click to expand...
Click to collapse
The 2.20.40.58 OTA was bugged and pulled from release. Just flash the full stock 2.20.40.59 firmware available from ASUS site and stop modifying your phone if you want to remain trouble-free with OTA updates. Or if you choose to continue to root and tinker with your phone accept that some things might get broken.