So I just switched from a hero to an evo today. Hero was rooted with cm6. I really gotta get this thing rooted. I love how fast and responsive the phone, but cant stand having it stock unrooted. The reason I didn't just go use one of the methods already posted is because I believe that with recent OTA updates I may have to do something different? I'm not super knowledgeable when it comes to all of this, but I understand the basics and did fine with lots of flashing on the hero.
The EVO is 2.2
Baseband 2.15.00.09.1
Build and Sofware number 3.30.651.2
PRI 1.77_003
Any advice on which method I can safely use would be greatly appreciated. Thanks for your time.
I believe that you have the upgraded hboot version so be care full on using some of the methods.. ill post a link in a sec
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
Right on. I was looking through this
http://forum.xda-developers.com/showthread.php?t=829045
but I'm having sort of a hard time understanding the prerequisites if it even is the correct and only option I have
That's exactly the link I was gonna post. Look at what you hboot v is. Turn your phone off and turn it back on while holding the lower button down. The hboot version should be round
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
2.02.0000
So if I go with that method, do I have to do the whole S-off thing beforehand? That's where I'm confused. I only have the phone's drivers installed on my pc that come htc sync or whatever. I installed them for my hero a while back
There. Tell me what you don't get and I will try my best
Prerequsites:
Extract to a folder of your choice. I recommend the root of C:\ into a folder of your choice or on the desktop. Make sure you have the drivers installed for your phone (recommend: SDK Drivers, unrevoked hboot drivers) and USB debugging is on. If possible master reset your phone. At the least reboot the damn thing. This was setup for people running windows, if you have access to it do it on a 32bit version. Use the adb.exe included with the package Oh and Read the FAQ and Warnings for f-sakes
1) Make sure usb debugging is on, and plug in your phone, DO NOT MOUNT USB
2) Open a command prompt and change to where ever you extracted the files to.
3) Type the following (this must be excuted from the folder you extracted to)
4) No Errors hopefully. Now lets change some permissions
5) You shouldnt see any confirmations or any messages. You should still be in the shell. Now its times for the magic....lets root that shell
6) It should kick you out and display some messages on the screen...just not errors. Lets double check that root! Type the following:
7)You Should see a "#". This means you have root if you see a "$" or some other error message. Reboot your phone, check your drivers, usb debugging and cable and start over. If you got a "#" You can Proceed. You should still be in the shell at a "#" If not start over...Otherwise
8) Now we are going to reboot your phone into the boot loader to flash the first PC36IMG.zip. You should still be in the shell So Type:
9) Once your phone is in the boot loader highlight bootloader, and press the power button. It will load the PC36IMG File...When it ask you to flash press VOL-UP. You will notice that it says bootloader bypassed and maybe some other errors. Dont worry this is normal. Once the flash of the file is done it will ask to reboot, Select NO by Pressing VOL-DOWN. Now some people have gotten some errors here and there during the flashing just continue as normal.
10) You should still be in the boot loader at this point. Scroll down to recovery and press the power button. When you see the red triangle. Type the following:
With any luck you should be at a recovery (green screen with text)
11) Select enable USB-MS. This will mount your sdcard. Look in the root of your sdcard and you should have two files. One named PC36IMG.zip and one named PC36IMG-MR.zip. Rename the file named PC36IMG.zip to PC36IMG-ENG.zip and then rename PC36IMG-MR.zip to PC36IMG.zip when your done follow the instructions on your phone to disable usb (press power) then proceed to step 12
12) Now Select flash zip from the menu and choose unrevoked-forever.zip. Wait for it to complete. Select Reboot from the menu.
Now pay attention. It might kick you back into:
BOOT LOADER: See 12A
ROM: See 12B
WHITE HTC SCREEN: See 12C
12A) Ok so you got kicked to the boot loader. It should scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12B) Ok so the phone booted into a rom. Power the phone off. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
12C) Ok so the phone is stuck at a white htc screen. Power the phone off by pulling the battery. Then repower the phone on pressing power and vol-down at the same time. It should take you into the bootloader and scan your card and find the PC36IMG.zip chose yes to flash this file and when it ask you to reboot....reboot by pressing vol-up....Proceed to step 13
13) Ok your phone is rooted now, and you should be inside the rom. The rom you just flashed is the stock unrooted rom with the modified recovery. Download a rom of your choice copy it to the root of your sd card and flash it. But type the following first
14) You Should be in the recovery menu now (green text screen). Do a backup by navigating the menu. Once thats done, follow the on screen instructions and reboot or flash a rom of your choice. Reboot. If you flashed a custom rom cool. If not no big deal eitherway. Do a PRL/Profile update while in the rom after the phone is done rebooting. Your Done.
15) Read the FAQ for questions
Click to expand...
Click to collapse
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
This is going to give you s off and root which is nandroid unlock I believe
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
that is correct. if you have a mac, i am building a full 3-command root kit for mac. i still need 1 more tester. if you have a mac, this will be the easiest way. will build one for pc as soon as the mac one is ready.
dkdude36 said:
that is correct. if you have a mac, i am building a full 3-command root kit for mac. i still need 1 more tester. if you have a mac, this will be the easiest way. will build one for pc as soon as the mac one is ready.
Click to expand...
Click to collapse
I'm not sure if you should use him since he is a novice at this.
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
that is the exact reason i want him as a tester. all it requires is adb. then type part1. hit vol up. then type part2. flash unrevoked-forever. type part3. hit vol up. fully rooted and s-off. done.
Okay.. its his choice. Lol you don't even know if he has a Mac
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
The part about unrevoked hboot drivers. Do I need to get something other than just the standard HTC drivers that I have then? Also I ran unrevoked3 on the phone a little earlier and I'm not sure if that will affect anything with this process. Do I need to someone do unrevoked forever in order to use this root method before I start typing the commands or does it just automatically do it through the zip file I download from the thread? Also, not a mac user, so I don't need to worry about that.
not many unrooted 2.02 hboot evo owners do. i'm taking every one i can get. i just need 1 conformation, and i will start on the pc version. mac is much easier to write than pc.
amoosavi said:
The part about unrevoked hboot drivers. Do I need to get something other than just the standard HTC drivers that I have then? Also I ran unrevoked3 on the phone a little earlier and I'm not sure if that will affect anything with this process. Do I need to someone do unrevoked forever in order to use this root method before I start typing the commands or does it just automatically do it through the zip file I download from the thread? Also, not a mac user, so I don't need to worry about that.
Click to expand...
Click to collapse
ok well i tried. so i dont think u need hboot drivers. you never actually do any hboot commands. it is a really easy tutorial. that is what i'm building my kit off of.
dkdude36 said:
ok well i tried. so i dont think u need hboot drivers. you never actually do any hboot commands. it is a really easy tutorial. that is what i'm building my kit off of.
Click to expand...
Click to collapse
So if I use this and it works, I cannot flash roms with different kernels right? I have to be careful with what I use I assume. And once rooted, is it pretty similar to clockwork as far as flashing goes?
btw thanks to the both of you. the help is much appreciated
I do not know the recovery that's used. No offense but it sucks that you have the new hboot. Ha.ha. okay sorry. Lol
Edit you can flash kernels but don't. Because most if not all are for hardware 003 so if you see specific new hardware kernels you could flash those. And remember, read that the Tom you want is for 004 before flashing or else things like your cam wont work.
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
Hey I can test for you if you'd like, I'm running snoweopard and already have the sdk. I'm also rooted already but I can undo the root. Feel free to let me know.
i have one tester right now. if my beta works and he gains root, i will need a new tester. i cant upgrade to 2.02 myself because i have the old hw 0003. i'm not sure if you want to unroot for something that might or might not work though. thanks for the generous offer.
Crossrocker said:
I do not know the recovery that's used. No offense but it sucks that you have the new hboot. Ha.ha. okay sorry. Lol
Edit you can flash kernels but don't. Because most if not all are for hardware 003 so if you see specific new hardware kernels you could flash those. And remember, read that the Tom you want is for 004 before flashing or else things like your cam wont work.
A drop of Chuck Norris's semen was placed on the IPhone. We now have the Htc Evo
Click to expand...
Click to collapse
He can flash kernels if he wants. It's up to him to see which work and which don't. For example I'm on 0003 but most roms don't work fully without flashing kernels.
dkdude36 said:
i have one tester right now. if my beta works and he gains root, i will need a new tester. i cant upgrade to 2.02 myself because i have the old hw 0003. i'm not sure if you want to unroot for something that might or might not work though. thanks for the generous offer.
Click to expand...
Click to collapse
Lol I'm on 0003 with the latest hboot. It's pretty weird.
Related
Is there any guide or instructions how to root and flash the Desire with a new custom ROM?
Im so confused right now, rooted my Hero and flashed it dozen times but now its different with Desire. Plz someone help?
Take this guide
http://forum.xda-developers.com/showthread.php?t=672770
Do i have to make a goldcard if i have a unlocked and unbranded Desire in sweden? 0.80 bootloader...
I think you have to.
I've done it with a goldcard, have also a unclocked device.
Unbranded devices generally don't need gold cards.
cedeel said:
Unbranded devices generally don't need gold cards.
Click to expand...
Click to collapse
Yep totally correct! If the handset was unbranded when new then no goldcard is needed. I didn't need one on mine.
socktug said:
Yep totally correct! If the handset was unbranded when new then no goldcard is needed. I didn't need one on mine.
Click to expand...
Click to collapse
thx for the info, didn't know that
cedeel said:
Unbranded devices generally don't need gold cards.
Click to expand...
Click to collapse
Thank you
So practicly what i have to do is this:
if you have a bootloader version 0.80.xxxx or below AND a current ROM of 1.21.xxx.x or below -
Part 1
Part 2
*- Copy the 'rooted update' you downloaded above to the root of your SD card, before replacing it into your device
*- Turn off your HTC desire, then turn it back on with the 'back' button held down. You'll see 'FASTBOOT' written on the screen in a red box.
*- Connect the phone to your computer, then run the 'test ruu' that you downloaded above (it may take a short while to start). Let the update complete and turn your device off as soon as it reaches the configuration wizard. If you need USB drivers, you can find them as part of the HTC Sync install.
*- Your device should now be off. Unplug the device from your computer. Turn it on again while holding down the 'volume down' button this time. The screen will look similar to before, but will say 'HBOOT' instead of 'FASTBOOT'. Use the volume buttons and the power button to select the 'RECOVERY' option. You should then see a screen with a red triangle - at this point, plug it into your Linux or OSX computer.
*- Now you need to unzip the 'push files' zip that you downloaded above. When you have done so, you'll see a file called 'recovery-linux.sh' or 'recovery-mac.sh'. Run the one appropriate to your operating system and the screen of your device should change to display the green recovery image menu.
*- In the recovery image (moving around using the optical trackball), select 'Wipe -> Wipe data /factory reset' then 'Flash zip from sdcard' and choose the rooted update. Confirm with the trackball and the update process will begin. It'll take a little while, so go make a nice cup of tea.
---------------------------------------------------
I hope i havent forgot anything? Im pretty nervous right now :/
I don't want to confuse issues, but that one looks a bit out of date. it will work fine, but there is a newer slightly easier method now.
Are you confident in following basic instructions on using linux? I wasn't but it is so easy that anyone can do it!
Take a look here and see which one you prefer.
http://android.modaco.com/content/htc-desire-desire-modaco-com/308542/r4-htc-desire-easy-rooting-guide-with-tiny-core-linux/
All you need to do with this one is download the appropriate file, burn it to disc and type 4 commands in linux.
Or just use r5. The scripts are good and shouldn't cause any trouble. If you are on linux/mac you might need to change permissions on some files though.
socktug said:
I don't want to confuse issues, but that one looks a bit out of date. it will work fine, but there is a newer slightly easier method now.
Are you confident in following basic instructions on using linux? I wasn't but it is so easy that anyone can do it!
Take a look here and see which one you prefer.
http://android.modaco.com/content/htc-desire-desire-modaco-com/308542/r4-htc-desire-easy-rooting-guide-with-tiny-core-linux/
All you need to do with this one is download the appropriate file, burn it to disc and type 4 commands in linux.
Click to expand...
Click to collapse
Without a doubt that seems easy, i just wonder if i can do it the same way with Ubuntu 9.10 ? Its because i have a livecd with Ubuntu but no empty cd to burn on
infexis said:
Without a doubt that seems easy, i just wonder if i can do it the same way with Ubuntu 9.10 ? Its because i have a livecd with Ubuntu but no empty cd to burn on
Click to expand...
Click to collapse
Try this one then! http://android.modaco.com/content/htc-desire-desire-modaco-com/307365/24-may-r5-htc-desire-rooting-guide-now-with-hboot-0-80-and-os-to-1-21-support/
socktug said:
Try this one then! http://android.modaco.com/content/htc-desire-desire-modaco-com/307365/24-may-r5-htc-desire-rooting-guide-now-with-hboot-0-80-and-os-to-1-21-support/
Click to expand...
Click to collapse
That is the guide i read first, but now it seems there is a better solution with linux.
I'm not sure what newer method you mean?
At the end of the day, any of the methods posted here will work for you. The first one I pointed to with tiny core linux was for me the easiest.
Just give one of them a try and post back if you encounter any problems, if the worst happens and you make a mistake and cause the usb to be bricked, it can now be easilly fixed.
As far as I am aware there are no other issued you can run into if you follow the guides.
Yeay, i just found a cd-rw at home
I will now erase the disc, burn the .iso file on it and start rooting
Wish me luck!
Lol. Good luck. Once you start flashing custom roms, you will never be happy and want to keep trying more!
socktug said:
Lol. Good luck. Once you start flashing custom roms, you will never be happy and want to keep trying more!
Click to expand...
Click to collapse
I know Ive had a Hero for about a year now
you dont need to use linux anymore there is a windows method
all you need is to download the pushfiles and extract them in the desire root files click on recovery windows.bat when you get to the triangle on the desire it will take you to the recovery options
also ur device has to be connected with usb and dont remove the usb when you updating the rom
tori007 said:
you dont need to use linux anymore there is a windows method
all you need is to download the pushfiles and extract them in the desire root files click on recovery windows.bat when you get to the triangle on the desire it will take you to the recovery options
also ur device has to be connected with usb and dont remove the usb when you updating the rom
Click to expand...
Click to collapse
That is the method to go to recovery after rooting. You still need to root first. Also, the windows method may be easier, but a lot of people are commenting on driver problems. The linux method is by far the least problematic.
Just my opinon of course!
i did not have any issue while rooting go to the hero section and use those drivers they worked fine for me
Okay i have a big problem...
I have rooted my device, however didn't run the ENG build, so my recovery is dependent on the pushing of the update.zip...
I flashed the myfroyo5 after pushing the update.zip... and ADB worked great, found the device in HBOOT and recovery.
Now after flashing this ROM, when i try and reboot back HBOOT no devices found.. however when i'm at the home screen with Myfroyo5 booted up, it sees the device..
Now i can't run any update, or get into clockwork recovery because i can't push the update.zip, because ADB can't see my device....
Please help! Any idea how i can get it to see my device with Myfroyo5? Otherwise i'm stuck with Myfroyo5 and can't reverse or do anything with it
Before all i did was change the option from device storage, to charge only, and that's how it worked...
again any ideas are appreciated!
wow 58 views and no one has any ideas? Please help!
Try turning on USB debugging mode?
Yes its always on, always check marked
I feel like I did have a similar problem at one point, but I don't remember how I resolved it. Sorry.
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
tubaking182 said:
gee maybe you should have flashed the eng build as everyone was told to do when they rooted their slide. try a dozen different large and small SD cards, i don't really think that is what makes it work but others seem to disagree and maybe once you swap them out you'll get lucky. but first i would try flashing the eng build
Click to expand...
Click to collapse
Must your replies always, ALWAYS have some snarky bit about how the person asking the question screwed up?
Humans are prone to error. You have valuable insight but beating someone's ego up before you give it really offsets your kindness.
Sent from my T-Mobile myTouch 3G Slide using XDA App
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
I see your point but, as I recall, the ENG build came after root had been put out there for a day or so. I'm also pretty sure it came after SlideMeRoot1.
Things like this, along with simple mistakes, can cause these errors. You are helpful but I just find the "hey, dummy" tone to be overkill.
Not everyone who screws up is out to **** up your day, ya know? I've been having my own ENG build problems because I made a mistake. It doesn't mean I don't know how to follow directions, it just means I made a mistake, the way every human on the planet does.
I apologize, as well, because my own real life smiley fun tone doesn't translate well to the forum. IE: you good kid.
tubaking182 said:
They don't always have snarky bits, but when 90% of problems are caused by not following directions then it apparently needs to be retold, I help a lot and I gave ideas to try here. Odds are he can still flash the eng build and then get into clockwork, but not following directions causes issues like this.
Sent from my T-Mobile myTouch 3G Slide using XDA App
Click to expand...
Click to collapse
Sent from my T-Mobile myTouch 3G Slide using XDA App
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
Just use CR new root method for the ota update and then follow the steps to flash ENG build. wouldnt that work? cause its unneccessary for the device to be recognized in hboot in adb that way =\ just guesing
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
javolin13 said:
i would do all that too.... you know i think the issue is the copying the files over... none of them are actually moving where they need to go!...
And when i try to do it manually the folder says "read only file system" and when i try to push files it says "1188 KB/s <0 bytes in XXXX.000s>
so none of the image files are moving over to allow me to flash ENG build... i swapped different SD cards and now i can flash the ENG build, but i cant move the files to /data/local before i do that, so right now its pointless to flash it...
Click to expand...
Click to collapse
do u have root in the shell script when u try to push the files over?
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
javolin13 said:
yes i do, that's whats really weird... i do adb shell, and i get #
when i do it the cat way, it does what it needs to, yet when i go search for the files using linda file manager they're still not there...
i dont want to flash eng build and it not work...
Click to expand...
Click to collapse
i mean u could always just unroot and start from square one
can't unroot if my device is not seen with adb in hboot / recovery
javolin13 said:
well first off.. i did follow directions... and it didn't work... and i've flashed multiple roms by just re-doing the ota.zip then the update.zip push, to get me into clockwork, until i flashed myfroyo5
which does not allow me to "charge only" which is why ADB doesn't allow to recognize my device in HBOOT/Recovery.
On the contra-ire i do know what i'm doing however a little bit of "knowledge" to point out maybe something that will fix an issue i have would be great.
Now i'm running myfroyo5, the device is seen by adb when the phones booted up, however upon reset to HBOOT/Recovery no devices are found. I've tried putting ENG build on my Sdcard, and HBOOT doesn't see it, also, i've tried pushing flash_image to /data/local, and mtd0.img to /data/local, and the files will not move.
That is part of my problem i'm assuming, i'll try another SD card to see if it will fix it, but i'm not sure its something that simple... but who knows, right?
Click to expand...
Click to collapse
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Suntar said:
I had the same problem just about and used the following thread. http://forum.xda-developers.com/showthread.php?t=710056 <-- BIG THANKS to Beartard for taking the time to type this all out. It worked just fine. I picked it up from - Installing the Engineering ROM - I kept my old update.zip file on the root of my sd card, and I got everthing back to normal, and everything works like new. Hope this helps
Click to expand...
Click to collapse
Thanks for the idea, but flashing the ENG build is pointless unless i can push the flash_image, and mtd0.img to /data/local... which for some reason my phone will not allow me to do this part;
Code:
type "adb push flash_image /data/local" and hit enter.
2. Type "adb push mtd0.img /data/local" and hit enter.
[Edit: I've now resolved this issue. Thanks to all who helped. Please see end of thread for my solution. I've made some edits below too. When things looked bad, the solution was to remove the microSD card, copy and load a more reliable PC36IMG.zip (there are a huge number out there), and only then could I use adb when the red triangle was present. Note that just renaming stuff randomly or worrying about the USB cable isn't a proper way to come up with a solution even though I did it also (and that may be the case for some units but it can't be the general problem or solution). I'd guess there's a huge amount of misinformation out there and some people may have tried random stuff but it looks like from playing with all this, there is a method to the madness of how phone and the adb communicate, as well as how the phone loads, and once you UNDERSTAND HOW that process, all this stops being so much of a black magic.
Note that the problem I had was because I used an outdated set of instructions. Here are the ones that worked for me in the end:
http://forum.xda-developers.com/showthread.php?t=829045
Thanks to all who did reply to my message.
]
--------
I've tried literally everything I've read to get out of my red triangle situation so please help if you can. This is not your standard "hold volume up and power button" response.
I was trying to get to root using the method at evo4g.me.
And I got a red triangle after the first application of the PC36IMG.ZIP. I then held the volume up and power button and, I get a blue lettered screen with 4 options:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Well, I've seemingly tried everything but I can't seem to get past this screen. I've pulled the battery out and rebooted, I go back to the above screen. Option 1 above gets me back to the same spot. Option 2 says it can't find sdcard/update.zip. I did option 3 but it does that and turns off and on and comes back to this same position. Even when I try to hold the volume button down. When I try to access this using adb, I get "device offline".
I can take the battery out, hold the volume down button, and then power on, and it takes me the through the same steps as before and I don't seem to have control over the choice of whether it should load the PC36IMG.ZIP file or not (i.e., the menu I see before it doesn't to be controllable by me).
So I'm at a loss. I really would like to finish this process and get to root, which shouldn't be too hard in my view but here I am.
I could move the SD card elsewhere and put an update.zip file on there but I'm not sure what to do here exactly so I can recover (and hopefully with root). Is this the correct thing to be thinking about? Move the SD card to another device, replace the .ZIP file, and then go from there? Is there a way to do this without moving the SD card?
[Edit: this is indeed what I did in the end. I found the correct PCIMG.zip file by trial and error.]
Thanks a lot!
BTW, I backed up all my apps on my sdcard so I should be fine right? I'm not sure what I'd need to do reinstall them.
[Edit: I lost some public keys, etc. with app reinstalls but I just had too many apps doing backups in different places and wasn't matching the right app restore to the right location in part.]
--
Backgrround: I'm new to the Evo 4G and in general new to doing stuff like rooting phones and the like, so please forgive me if my questions (or actions) or too naive. I have been using Unix systems all my life and Linux when there were fewer than 100,000 users of it (back in 1992-1993) and am extremely comfortable with it and do all my science (work) exclusively with Linux.
ramdom said:
I've tried literally everything I've read to get out of my red triangle situation so please help if you can. This is not your standard "hold volume up and power button" response.
I was trying to get to root using the method at evo4g.me.
And I got a red triangle after the first application of the PC36IMG.ZIP. I then held the volume up and power button and, I get a blue lettered screen with 4 options:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
Well, I've seemingly tried everything but I can't seem to get past this screen. I've pulled the battery out and rebooted, I go back to the above screen. Option 1 above gets me back to the same spot. Option 2 says it can't find sdcard/update.zip. I did option 3 but it does that and turns off and on and comes back to this same position. Even when I try to hold the volume button down. When I try to access this using adb, I get "device offline".
I can take the battery out, hold the volume down button, and then power on, and it takes me the through the same steps as before and I don't seem to have control over the choice of whether it should load the PC36IMG.ZIP file or not (i.e., the menu I see before it doesn't to be controllable by me).
So I'm at a loss. I really would like to finish this process and get to root, which shouldn't be too hard in my view but here I am.
I could move the SD card elsewhere and put an update.zip file on there but I'm not sure what to do here exactly so I can recover (and hopefully with root). Is this the correct thing to be thinking about? Move the SD card to another device, replace the .ZIP file, and then go from there? Is there a way to do this without moving the SD card?
Thanks a lot!
BTW, I backed up all my apps on my sdcard so I should be fine right? I'm not sure what I'd need to do reinstall them.
--
Edits based on trying to fix this: when I do `adb devices`, I get:
List of devices attached
HT0B6HL05287 offline
--
Backgrround: I'm new to the Evo 4G and in general new to doing stuff like rooting phones and the like, so please forgive me if my questions (or actions) or too naive. I have been using Unix systems all my life and Linux when there were fewer than 100,000 users of it (back in 1992-1993) and am extremely comfortable with it and do all my science (work) exclusively with Linux.
Click to expand...
Click to collapse
That is the stock recovery you are seeing there, does it let you do anything at all in the bootloader? If you can get it into fastboot mode you can fix it from there.
I rooted using regaw's instructions also, and also got that damn triangle, lol. Pretty sure all I did was reboot to bootloader and let it update the PC36.img again to get out of it.
xHausx said:
That is the stock recovery you are seeing there, does it let you do anything at all in the bootloader? If you can get it into fastboot mode you can fix it from there.
Click to expand...
Click to collapse
Yes, I believe so. I can let the PC36IMG.ZIP reload again and then AFTER that I can say "no" to the update and then "no" to reboot devices and I can get into a menu that says:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HSB USB
From there I can select FASTBOOT and head into another menu that says:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
Trying BOOTLOADER gets me through the same HBOOT cycle where the PC36IMG.ZIP is reloaded and asked to be applied. Trying REBOOT gives me a white HTC screen (unless I need to wait a while).
Thanks! I assume I need to pull the SD card out, load it on my computer through another source, and then remove the PC36IMG.ZIP file and then replace it with something else that I can use to get rooted? Or will just removing the PC36IMG.ZIP file do it?
I'm also looking to achieve root so if I am going to the trouble of removing the SD card and putting it back, I'd like to know if if there's another PC36IMG.ZIP that'll let me have a nice version of the HTC evo that is rooted.
--Ram
I know a few people who have recently purchased EVOs and they still have Hardware version 3 and Hboot .97
what versions do you guys have on your phones?
If the hboot is still .97 you can used unrevoked forever for a full root and nand unlock.
if higher there is a tutorial on these forums for Hboot 2.02.
chris66 said:
I rooted using regaw's instructions also, and also got that damn triangle, lol. Pretty sure all I did was reboot to bootloader and let it update the PC36.img again to get out of it.
Click to expand...
Click to collapse
How did you do it?
Tuffgong4 said:
I know a few people who have recently purchased EVOs and they still have Hardware version 3 and Hboot .97
what versions do you guys have on your phones?
If the hboot is still .97 you can used unrevoked forever for a full root and nand unlock.
if higher there is a tutorial on these forums for Hboot 2.02.
Click to expand...
Click to collapse
I have:
SUPERSONIC EVT2-3 SHIP S-ON
HBOOT-2.02-0000
TOUCH-PANEL-ATMELC-03_16ac
RADIO-2.15.00.09.01
Oct 14 2010, 19:14:47
I assume the tutorial you're referring to is here:
http://forum.xda-developers.com/showthread.php?t=829045
But I'm not sure how to get out of this particular PC36IMG.ZIP (gotten from evo4g.me) and replace it with the PC36IMG.ZIP posted in the above URL above easily, since I can no longer access this device using adb. Unless I am missing something obvious.
Well, I'm learning a lot! Thanks!
I do agree having root on these systems will be fantastic. I don't understand why it's not just a ready option. Things like tethering, etc. should be a given and built into the $10 cost or something else of the network. I'd like to port things like csh on there, and have a powerful terminal like I can get in the Mac OS X. Is there any way this is possible at all? We can get bigger and bigger microSD cards right? An entire stripped down Linux system can fit in a few gigs (but I want to be able to use it as a phone too).
--Ram
Went backward in the directions.
This the whole post that I used, pretty sure I just went backward and started again, it did take a seemingly HUGE amount of time the first time thru flashing the PC36.img
http://forum.xda-developers.com/showthread.php?t=765496
PULL THE SD CARD and put the image on the root? , lol
chris66 said:
Went backward in the directions.
This the whole post that I used, pretty sure I just went backward and started again, it did take a seemingly HUGE amount of time the first time thru flashing the PC36.img
http://forum.xda-developers.com/showthread.php?t=765496
PULL THE SD CARD and put the image on the root? , lol
Click to expand...
Click to collapse
The instructions at the above URL are what I used to get to this place with the red triangle that I can't seem to get out of. I can no longer access the phone using adb so I can't push anything. I can't access the phone through my computer right now once it has become stuck at the red triangle, this is my main issue. No access. Nothing. It just says "error: device offline" no matter what I try.
You don't think the SD CARD strategy will work?
This is where I scared the **** outta myself.....
"If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue."
It worked for me, but I don't know what hardware version and all you have.
ramdom said:
The instructions are the URL are what I used to get to this place with the red triangle that I can't seem to get out of. I can no longer access the phone using adb so I can't push anything. I can't access the phone through my computer right now once it has become stuck at the red triangle, this is my main issue. No access. Nothing. It just says "error: device offline" no matter what I try.
You don't think the SD CARD strategy will work?
Click to expand...
Click to collapse
just pull the sd card out of the evo (behind the battery) and put the new img on the root of the card.
chris66 said:
This is where I scaref the **** outta myself.....
"If this doesn't work (ie the PC36IMG.zip does NOT load) backup all of your sdcard contents onto your computer, reformat your sdcard to FAT32, redownload the PC36IMG.zip, and drag and drop it onto the sdcard, then reboot into the bootloader and try again. This should fix the issue."
It worked for me, but I don't know what hardware version and all you have.
Click to expand...
Click to collapse
Me too, but I pay for the extra warranty that's supposed to cover nearly everything, which I think should cover this.
So from the above instructions, am I to understand that I remove the sdcard out and clean it out in my computer and install a new PC36IMG?
Should I try the one from here? Even here, there are like 3 versions:
http://forum.xda-developers.com/showthread.php?t=829045
Sorry for all the questions. Normally I'd hack and figure this out without even googling it but after googling it, the amount of stuff out there is enormous which is throwing me off. I think I have like 10 versions of the PC36IMG and not sure which to go with next that'll not destroy everything and give me root! Crazy.
Tuffgong4 said:
just pull the sd card out of the evo (behind the battery) and put the new img on the root of the card.
Click to expand...
Click to collapse
Thanks a lot. Pulling the evo card was easier than I thought it would be. Which particular one? I'm looking here:
http://forum.xda-developers.com/showthread.php?t=829045
Should I just manually copy all these files over to the sdcard and then reboot and see what happens? I guess I'll try that. Thanks.
Thanks guys!
--Ram
Well, I solved this problem and am now enjoying root. Thanks to all who helped. I followed the instructions here:
http://forum.xda-developers.com/showthread.php?t=829045
But I still couldn't get past step 10. I even read the FAQ and followed the renaming suggestions (this wasn't the issue but I did it anyway) and it still didn't work. Basically the problem was that I wasn't even able to get to the shell even though I was able to use adb to push files (weird?).
So I was playing around with the EVO-recovery.zip (http://www.knowyourcell.com/htc/htc-evo-4g/evo-4g-guides/463925/how_to_root_the_htc_evo_4g.html) and ran the recovery-linux.sh script, which then put me into the green recovery screen. The rest was straight forward after that (as per the instructions at the URL above). So perhaps the difference of which adb to use was what it was, since that zip file comes with its own adb.
I am now rooted. Now what?
My wi fi doesn't seem to work, and neither does the google wireless tethering app, which is one of the reasons I wanted to root. When I run "adb shell" I now get a "#" instead of a "$" so I assume this (among other things, including the S-OFF) means I am rooted. So no wi-fi, did I trash something?
[Edit: I fixed this by installing the fresh ROM; thanks chris66 and others who helped!]
I'm just using the stock ROM provided from the URL above. Not sure what the best one to use is and how to use it.
[Edit: Stil no idea. Way too many ROMs out there. It's crazy. Fresh seems to have a good rep. It works pretty well, after one week.]
I also backed up all my apps on my sdcard, is there a way to restore them in one quick fell swoop instead of opening them one by one?
[Edit: I figured out how to do the multiselection option and apply it apps. A good file manager will do the backups for you. I went from ASTRO to ES File Explorer. Latter looks slightly cleaner. Probably better ones out there.]
Thanks to all who helped! I am excited about playing around with all this further. Only PITA is reconfiguring everything again the way I like it.
[Edit: Favourite apps are ConnectBot; Android Wireless Tether; AndroidVNC; DropBox; ES File Explorer; System Panel; --- from Ubuntu, I ADB to access stuff at the prompt which when having a # is really really powerful. Maybe I was wrong but before I put the new ROM on I didn't think the "more" command was available.]
Cool, try superuser and the wifi app from the market. Flash almost any of the newer roms, and they're already both usable, wifi and usb.
Sent from my PC36100 using XDA App
Thanks in advance to/for any and all help, long story short: I need a genius workaround to Root my Evo 4G
What's Wrong: (Keep in mind I've tried and am aware of the necessary settings/steps)
1. PC doesn't detect USB connected/debug enabled Evo
2. USB selection on Evo seems broken. Only the 'Debug Enabled' notification alerts of activity
3. All update.zips fail Signature Verification in Recovery
4. HBOOT 'SD Whatever' it said doesn't say it anymore when HBOOT loads and scans the SD card
5. HBOOT USB does nothing when the Evo and PC are connected. There's more, but minor I think.
What Works:
1.This fast ass processor, hells yeah! If you haven't, try 'My Paper Plane2' from the Market. Stellar.
Assumed/Possible Solution Routes: (Cue the Elite, at least one of these could work, right?)
1. Fix Signature Verification(s) for Recovery update.zips
- About this, I got error 'E: Error in cache/recovery/command' in Recovery, so with Root Explorer I made recovery and command folders with their respective permissions and now get 'Error in CACHE: recovery/command (Bad file number). Was my guess at all close to fixing that?
2. Somehow reflash HBOOT with S-ON in Recovery
3. Android executed 1-click/auto/apk permanent Rooter
4. S-OFF during z4Root's temporary Root
5. Manual missing/broken system file replacement in Root Explorer
6. Terminal Emulator - USB Debug or .img flash?
Thanks again for the help, I'm not new but I did break some of this myself. Using a rooted Huawei Ascend (I've done 4, everyone around me has this stupid phone), I guess I just assumed I was a developer and jumped right in. Lesson Learned=D
No rooted roms will work until you're rooted "s-off" but im assuming you're on the comp right now right? If so maybe this could help you!
http://noobgui.de/wiki/index.php?title=Main_Page
No usb or hboot, ouch.....
Usb fix :-(
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100
Yeah, Im on now. i have seen both pages, but the Evo Root Wiki i had lost in the sea of links earlier, so thanks.
log3an said:
Yeah, Im on now. i have seen both pages, but the Evo Root Wiki i had lost in the sea of links earlier, so thanks.
Click to expand...
Click to collapse
Last I saw the EVO root wiki was way outdated.
Sent from my PC36100 using XDA Premium App
go to unrevoked.com and download the unrevoked forever tool and make sure you have the adb & hboot usb drivers installed on you pc. Everything you need can be found at unrevoked site for usb drivers, etc. Boot into Hboot on your evo. Connect to your pc with usb cable and choose charge only. Then select Fastboot or Hboot on your evo and press power button. Then run the unrevoked reflash package you have already downloaded. Let it do it's thing and you will have a new Clockwork custom recovery.
Thanks, but Ive tried all the easy options, im going to need to command line some crap. Im going to generalize my problem and edit this post.
Alright, so, I guess I'm not the only person having issues with the current versions of ICS, which is kinda comforting. If you can't update your SU binary in an ICS rom because your SU app tell you you're not S-Off, that means the bootloader partition was somehow damaged and forgot you're S-Off, so here's a detailed guide of what I did to get my phone up and running again.
This is also a great guide to help fix any stability problems your phone is having in general.
If you just need to unroot to send the phone back to Verizon or to sell it to someone, stop after step 17 and reading everything after it, but before step 18.
***WARNING***
If you do not follow these directions perfectly, you have a chance of damaging your phone. Part of this process involves flashing hboot manually through ADB, which is dangerous. PLEASE PAY SPECIFIC ATTENTION TO THAT SECTION OF THIS GUIDE. If you don't, your phone is going to be a very depressing paperweight.
IF AT ANY TIME YOUR PHONE TRIES TO ACCEPT AN OTA YOU NEED TO DENY IT! Because of how the Revolutionary Team's S-Off Tool works, we need to be in Froyo to flash hboot manually. An OTA will only get in the way!
Make sure your phone has a decent amount of battery (More than 50%) and keep it plugged in whenever you boot to hboot to be safe. If your phone powers off or dies when flashing a PG32IMG.zip, BAD BAD BAD things will happen!
I am also not responsible for anything that happens to your phone. If you're rooted and S-Off, you already know the dangers, so be smart!
Before I get started though, I have some people to credit, as their tools are used in this guide.
Thanks to:
notluK for his Unroot Guide on Android Central. Pretty much all of this guide is a direct kang/plagiarization from him, with minor changes due to file hosting fiascos.
CLSShortFuse for his SuperOneClick tool
The Revolutionary Team for their S-Off Tool
The unrEVOked Team for hosting the HTC Fastboot drivers
I think that's it... now, for your bacon.
NOTE: I do not have the original md5 sums for these files, so don't ask. Just download over a reliable connection (NOT ON YOUR PHONE!).
Pre-Requisites:
HTC Fastboot Drivers
Android SDK
Froyo (2.2.1) PG32IMG.zip
Gingerbread (2.3.3) PG32IMG.zip
Super SU ZIP from here
And a significant amount of time and patience
Okay... here goes. Please make sure to keep all of the above files on your PC to be safe. They are always good to have in case your phone goes screwy.
1. Download and install the Android SDK, install the HTC drivers and then reboot your PC. (If your SDK is fully functional and you already have the Fastboot drivers installed, just skip this step.)
2. Put the Froyo RUU zip on the root of your SD card and rename it to PG32IMG.zip (if Windows is hiding your file extensions, don't add the .zip to the end).
3. Boot your phone into the Bootloader (Vol Down + Power while off)
4. Press Vol Up to accept the update
5. Reboot phone when done (It may power off to a black screen instead of actually rebooting. Don't panic, just turn the phone on like you normally would ) When it's done booting, delete the PG32IMG.zip from the SD.
6. Check your OS version under Menu>Settings>About Phone>Software Information. Verify your OS version as 2.2.1.
7. Enable USB Debugging under Menu>Settings>Applications>Development
8. Plug in your phone and run the SuperOneClick root tool. When it asks if you want Busybox installed, say Yes. This is important, as you will need Busybox to verify the md5 of the hboot image you are about to flash to your phone manually.
9. Reboot your phone
10. Find the Froyo PG32IMG.zip on your computer and find the hboot_0.97.0000_336906.nb0 file inside. Extract it and put it in the platform-tools folder of your SDK.
11. Make sure your phone is still plugged in and then open your Command Prompt/Terminal and cd to your SDK's platform-tools folder, and follow the adb commands below, with your phone still plugged in, of course!
EXAMPLE: This is where mine is, yours may be different, so check!
Code:
cd C:\android\platform-tools\
Once that's done, continue:
Code:
adb devices (make sure ADB sees your phone if not, this is an appropriate time to ask for help :))
adb root
adb remount
adb push hboot_0.97.0000_336906.nb0 /data/local/
STOP HERE! If you're a dummy and didn't install Busybox with your SuperOneClick, download a Busybox Installer app from the Market and install it to /system/xbin/.
12. Now, do:
Code:
adb shell
su
/system/xbin/busybox md5sum /data/local/hboot_0.97.0000_336906.nb0
If your answer is not affe3dc9abe9d3a8c8bb3ba0ee5176ac, stop now and reboot your phone, then start over again at step 11.
***WARNING***
If you skip this step, you're a big, dumb idiot. This next step involves flashing something to what is probably the most important partition on your phone. If you mess this up, no one can help you, and your phone is permanent brick.
13. If the md5sums match, continue:
Code:
adb shell dd if=/data/local/hboot_0.97.0000_336906.nb0 of=/dev/block/mmcblk0p18
14. Verify the partition's md5sum to be extra-safe. If it's not exactly the same as the original md5 above, DO NOT REBOOT YOUR PHONE! Just start at step 11 again.
Code:
adb shell /system/xbin/busybox md5sum /dev/block/mmcblk0p18
15. Go into your Settings and disable Fast Boot (I don't remember where this is on the 2.2.1 firmware, so look around until you find it). Now, put the 2.3.3 PG32IMG.zip on the root of your SD and boot into hboot like you did before (Vol Down + Power while off).
16. Press Vol Up to accept the update.
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
18. Run Revolutionary like you did before and accept the installation of ClockworkMod recovery (It'll be an old version, but that's okay).
19. Put the SuperUser zip from earlier on your SD and flash it like normal. (Backup first if you want to have a backup of factory stock unrooted)
20. Profit!
At this point, your phone is now at root 2.3.3 stock and S-Off again! Update your ClockworkMod recovery (or use 4ext, which I like a lot), make a backup (PLEASE, MAKE A BACKUP!) and then flash the rom of your choice, probably an ICS one.
Feel free to update your radio and stuff too. Things should be working much better than before.
And, to be safe, never OC past 1.3ghz. You shouldn't ever need to anyway, and it can break things, which means you'll have to do this all over again. Overclocking too high and my phone overheating is how I got into this situation in the first place, so I'm not just blowing hot air here. (Haha, get it? )
If anybody has any questions (please, don't bombard me with them ), feel free to post here and I'll do my best to respond in a helpful and timely manner.
If this helped you, click the "Thanks" button, or I'ma find you!
Happy flashing!
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
RegnierD said:
I'm glad this is useful! I have all the RUU files saved on my pc too, so if the links do go bad at some point, I still have them and can re-upload.
Click to expand...
Click to collapse
Links are definitely bad. Any chance you still have the files?
I found the Froyo RUU, but I still need the latest Gingerbread RUU.
This helps a lot thanks
Reg, could update the links for the Froyo and GB RUU's? Thanks!
I'll post new links sometime today, guys.
RegnierD said:
I'll post new links sometime today, guys.
Click to expand...
Click to collapse
Thanks you!!
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Does anyone have the 2.3.3 stock kernel? I tried another and now wifi won't enable
nevermind!... lol
my phone isn't charging (read that many users have had problems with the charging port on this phone), i just unrooted and s-off'ed. i'm on froyo now. should i download 2.3.3? where can i get it and would that be enough to get a new phone under warranty? or do i need to have the latest OTA 2.3.4? thanks in advance and i apologize for all the questions
ballisticn8 said:
^^ should be stickied
thx for the legwork gathering and re-uploading all the files to new sharing sites.
Click to expand...
Click to collapse
Now stickied
If I helped, give thanks, if you please.
........Death before dishonor........
hokieputter said:
the RUU files can be found here:
http://goo-inside.me/vivow/ruu
Click to expand...
Click to collapse
which one should i download if i just want the stock 2.3.3 so that i can return my phone for warranty? thanks.
The links are bad. I need the two PG32IMG files... My phone is not fairing well =/
S-On
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
smayer85 said:
Where in the guide should I stop if i want to go from s-off back to s-on so i can get a replacement phone?
Click to expand...
Click to collapse
RegnierD said:
17. Reboot into GB when done.
***WARNING***
If you accept the 2.3.4 OTA before going S-Off, you will have no way of reverting and back and re-rooting, SO DON'T DO IT!
The above may not be true, but I'm pretty sure it is, so PLEASE, for your own good, DON'T ACCEPT THE OTA!
If you needed to unroot to send the phone back to Verizon/wherever you got it from, or to sell it, this is the place to stop. If you're selling the phone to someone and they know what rooting is, they'll thank you for not updating to 2.3.4.
Click to expand...
Click to collapse
Reading helps.
I cannot get android SDK to install, it says "Java SE Development Kit (JDK) not found. Error: Failed to find Java version for 'C:\Windows\system32\java.exe': [2] The system cannot find the file specified." I have went and tried to install the java it says to but that won't work either. Should I uninstall any java I have installed and try then? My phone bootloops everytime i restart causing me to factory reset it so I need to get a replacement. Thank you.
Edit: Got the java to install after deleting and also have android SDK installing all the stuff now.
New issue, sorry for so many questions im kind of a noob, but when i try to adb root it says something about not able to in production. Does it affect me that my sdk folder in on a seperate HDD from c:\? I'm gonna try to redo it now and hopefully have this working this afternoon. Also, cmd will not let me cd to my SDK folder.
Mount error
When I enter the remount command an error is returned stating: adb remount failed: unknown error: 0
Anyone have any ideas how to resolve this?
Thanks