Related
I just rooted my first android, obviously the TBolt.
I am very new to this. I may have touched 'Command' maybe once before this. I rooted manually with the help of everyone on this site and others. Everyone has been very helpful with this whole process, but now I'm stuck.
I want to flash a rom and kernel from Das BAMF 1.1
I download the rom and kernel, put the rom on my sd root and open with Rom Manager but it does not seem to take.
So i tried to open the kernel but putting that on the sd and hboot, right? The bootloader seems to read it but does not do anything with it. I'm assuming I'm suppose to be seeing what was going on when i rooted my phone.
If you need any other info, i'll be more than happy to provide that for you.
I would have posted in the development part of the forum but this is my first post on this site.
Thanks in advance. Would really appreciate the help. What's the point of root if i can't put a custom rom onto my TBolt?
I just loaded the ROM and went about it the same way you're trying.
Make sure you have PG05IMG.zip on the root of your SD (with that exact name). When you load into hboot, it *should* automatically detect it and start running through the process, you shouldn't have to hit anything. After it checks some files you should see something along the lines of "Do you want to start update? <vol up> yes <vol down> no".
If it hangs at any point you might want to try downloading it again. After you get the kernel loaded you can flash the rom file via RomManager from your SD Card.
Also, maybe throw a picture up of what you're seeing if the above doesn't seem to help.
Thank for the response!
Actually, after being so fed up with trying to get the zip to load with hboot, i decided to take another dive the manual way and fastboot the boot.img kernel through adb. It worked great! I checked the kernel after rebooting and it said that match 1st date that was in the file.
So, now I need to find a way to get the rim zip file on the phone. I downloaded the 1.2 version and I still get the same thing as before. I open clockwork recovery and install from sd and it says installation aborted.
Any ideas?
gfro9191 said:
Thank for the response!
Actually, after being so fed up with trying to get the zip to load with hboot, i decided to take another dive the manual way and fastboot the boot.img kernel through adb. It worked great! I checked the kernel after rebooting and it said that match 1st date that was in the file.
So, now I need to find a way to get the rim zip file on the phone. I downloaded the 1.2 version and I still get the same thing as before. I open clockwork recovery and install from sd and it says installation aborted.
Any ideas?
Click to expand...
Click to collapse
What do you mean by that? How are you selecting install from sd but you don't have the file on the SD?
g00s3y said:
What do you mean by that? How are you selecting install from sd but you don't have the file on the SD?
Click to expand...
Click to collapse
Sorry! I typed all of that on my phone on my break. I mean to flash the rom zip file. It is on my sd card and I can see it when I boot into recovery but the installation aborts.
This is what I'm talking about...
I have a feeling this is not the first time someone has run into this.
There's probably some simple fix but since this is a new phone, there really isn't too much info on ROMs yet.
If anyone cares... i did it!
I used the one click root the first time and either i missed a step or there was a corrupted file somewhere because it's better now with the manual root.
I whiped the whole phone, rooted completely manually and all is well.
Also, the Das ROM installed properly.
thanks for everyone's help!
I was attempting to use the method found here: http://forum.xda-developers.com/showthread.php?t=1690919 to root my EVO 4G LTE, but am unable to post in that thread with questions, as I have less than 10 posts, apparently. My issue is that I go all the way through the process, install ROM manager, and then try to flash the latest ClockworkMod (Superuser 3.0.7 efghi), but it gives me the following error:
"You must root your phone for ROM Manager to function. Superuser was not found at "/system/bin/su" or "/system/xbin/su". Use Google Search on your computer to find instructions to root your phone"
I rebooted into recovery mode, and it does say "UNLOCKED" and "TAMPERED" at the top... in case that's helpful. Does anyone know where I might go to figure this out? I've been combing through the original post by regaw_leinad but haven't spotted anything yet. Any help is appreciated.
CWM doesn't work on our phone. You have to flash TWRP via terminal emulator.
Sent from my EVO using XDA
Yeah they really should put a disclaimer on that cwm thread. You would never know looking at the op that it doesn't work.
Evo_Shift said:
Yeah they really should put a disclaimer on that cwm thread. You would never know looking at the op that it doesn't work.
Click to expand...
Click to collapse
There is a disclaimer and the download was removed from the thread ages ago. This is only an issue for people who don't research first and try to use rom manager to install cwm (no offense to op). ROM manager should have a disclaimer also.
hmm... okay, well thanks for the info. maybe i've hosed something, as after installing the GooManager app as directed on the teamwin site and then initiating the download of the OpenRecoveryScript, it does not seem to do anything after the download, though the app says that it would reboot to install.
i'm still up against a wall with using either the GooManager, or trying to copy the openrecovery script directly onto the internal SD card and using terminal emulator... is there another method? or another way to approach this or start all over or something? it just seems like i can't get anything to work like it's supposed to at this point... even the terminal emulator is telling me that "su" isn't a recognized command... any help is appreciated.
mckraut79 said:
i'm still up against a wall with using either the GooManager, or trying to copy the openrecovery script directly onto the internal SD card and using terminal emulator... is there another method? or another way to approach this or start all over or something? it just seems like i can't get anything to work like it's supposed to at this point... even the terminal emulator is telling me that "su" isn't a recognized command... any help is appreciated.
Click to expand...
Click to collapse
I used the same root process and flashed cwm via rom manager and then had to go to goomanager. Goomanager works since I got twrp working, but I haven't flashed anything since I wanna wait to see if the new roms break lte (if lte comes to Seattle).
i tryed flashing twrp through goo manger also and it didnt work after it downloaded it woulndt reboot.. so i had to flash twrp using terminal emulator.. worked like a charm
Won't break lte like the Wimax issues. Lte info OS stored on the simcard unlike Wimax in a separate partition
sent from my EVO LTE
any advice on the su command not found in terminal emulator? i searched on google and saw other people having similar problems and mentioned making sure that SuperSU was running first which I have installed unbeknownst to me... though if I try to launch SuperSU, it tells me that there is no SU binary installed and SuperSU cannot install it, and all I can do is quit.
Try the flashable in the supersu thread
just to add another note... I also went through the process to install the Android SDK, so that I could connect via adb... after doing that, I can access my device via adb, but after doing "adb shell", I then try to use the su command, and get the same error,
su
/system/bin/sh: not found
what am I missing here? is my phone not truly rooted then?
i rebooted into recovery and verified that the boot loader shows UNLOCKED and TAMPERED (that's desired, right?) and that TWRP was my new recovery image, if that's the term for it. i had already downloaded the latest viperboy image, and booted into twrp and went through the install process for that image..... and the weird thing was everything seemed like it took and it installed. but nothing was different on a reboot. any ideas?
Unlocked and tampered don't necessarily mean you have root. At the risk of sounding stupid I have one question. Have you tried re-running Regaw one click then flashing your desired ROM of choice?
Seems re-running the script has fixed other people's issues.
sent from my LTEvo
believe me, if anything I'm the one that sounds stupid here I'm sure. at any rate, I did run regaw twice, but that was a while ago, and it was because it seemed like the first time through it didn't complete the process successfully for some reason. i can run it again today. after i do that, is the best way to tell if you're rooted to run the terminal emulator and try an su command and see if it's successful or not?
An app that requires root will work, if you get a prompt you should be golden. I would recommend re-running you should be fine, if there is an additional problem there is a fix for what clockwork would have messed up in the twrp thread (on my phone can't find it now), but I think you should be fine.
Edit: I lied, if you have the misc partition issue from trying cwm the fix is in viper Rom thread here. http://forum.xda-developers.com/showthread.php?p=26663638
sent from my LTEvo
well i ran the root method from regaw again and it looks like i'm now good to go as far as i can tell.... i'm running viperboy's ROM... i saw one from flex360 (the super stable/fast one), but not sure which ZIP package to download... so not sure if i will try any others since i'm not sure what to do there (and i can't post in those threads to ask for advice). i see the charmeleon one looks popular also...but then i would have to flash that boot file also? maybe i should just let good enough alone and be happy with the ROM i have.. thanks for all the help and suggestions here, you guys are helpful
No problem, viper Rom is good (running it until cm9 is official) you can flash another Rom but heed any OP warnings. Also, don't be flash happy, it could prove harmful in the end. :beer:
sent from my LTEvo
excellent! thanks for the info... that's really exactly what i wanted to hear... the validation that the rom i have is perfectly fine and just be happy
Also, as for the charmeleon ROM, I believe you SONT need to flash a boot.img. I believe that info is deprecated. Within the first few pages you'll find out for sure.
I believe when joelz first posted the ROM he thought that'd be necessary, but was able to include boot.img in ROM zip.
sent from my Jewel via xda premium.
First let me apologize for knowingly posting in the wrong section. I'm a noob I am not allowed to post this in the appropriate thread found here:
http://forum.xda-developers.com/showthread.php?t=1690919
I took the plunge today and finally rooted my EVO 4G LTE. RegawMOD worked great and I'm now rooted. The hiccup I ran into was even covered in the thread, but not mentioned in the original instructions.
Possibly relevant info:
- completely stock phone running 1.22.651.3 with hboot 1.15.0000.
- Win7 64 bit
- installed .NET
- installed HTC drivers
- DL'd x64 version of RegawMOD
When running the RegawMOD exe for the first time I got the "Necessary HTC driver files are missing. Please get drivers by installing HTC Sync, or directly with the driver zip (advanced)" error message.
The fix that was posted worked. I installed HTC Sync and had to connect my phone with HTC Sync running. Once it found my phone I was good to go with the rest. No further problems at all.
Side Note: regaw_leinad posted to the person who ran into the same problem to check for "C:\Windows\system32\drivers\ANDROIDUSB.sys or C:\Windows\syswow64\drivers\ANDROIDUSB.sys"
After installing .NET, HTC drivers and HTC Sync I didn't have either of those. After HTC Sync found my phone it installed I have the .sys file in my system32\drivers folder but not the syswow64 directory.
So, what are u asking? Are u on a x86 (32 bit) or 64 bit version of windows?
I remember only downloading one or the other when I rooted using that method. Can't remember which because I use so many different computers at work.
Try uninstalling what you have and download it all again to the same folder. The root zip, drivers, etc all in the same place with no subfolders. I.E.: C:/(all downloads here)
Ask me about my ability to annoy complete strangers!
So.......... it worked.......?
Yup, it worked and I've since flashed Viper4G and so far I'm loving it. I suppose you guys don't get too many noobs signing up to thank you and offering a suggestion as opposed to asking for help.
It appears that in my writing and editing I accidentally removed the suggestion that I wanted to offer. That is, that it may be beneficial to add a clause about that hitch in the original instructions in that thread. While I didn't read all 90+ pages, it seems I'm not the first or last to have experienced that issue.
I also thought it might be beneficial to report my experience (this may be the noob in me coming out). As the last few pages of the thread are all problems that people are running into I thought it may be beneficial for the regawMOD makers to know that the latest version worked almost perfectly with my setup.
the reason it doesnt find the drivers after you install them is because they get unpacked, they still havent been installed, if you turn on debugging and plug phone into pc it will install drivers, then when you start regawmod and the phone reboots then at the bootloader it will install yet another driver and youre good to go, no need to install htc sync
I used the RegawMOD and all it did was unlock my evo 4g lte, now I can't root, I tried everything I can find, I can't put in root nor put in twrp recovery I don't know what to do pls help
Sent from my Nexus 7 using xda app-developers app
miamiboi995 said:
I used the RegawMOD and all it did was unlock my evo 4g lte, now I can't root, I tried everything I can find, I can't put in root nor put in twrp recovery I don't know what to do pls help
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Have you tried flashing supersu through fastboot cmd?
Sent from my EVO using xda premium
I might need that... how do I do it ? Where is supersu ?
k000 said:
I might need that... how do I do it ? Where is supersu ?
Click to expand...
Click to collapse
Google Playstore maybe?
Ok guys...here it goes.
I've had a long night of feeling like the biggest idiot to walk the Android planet. I just bought this phone off someone, and have done rooting/custom ROM installing before. But I messed up, and now I feel like I'm an idiot & screwed because I'm just so lost now. I love learning, but I feel like I'm in such a hole. Here's what happened:
I used "All In One Kit" to install "TWRP 2.6.0.0", and like anybody, I wanted to install a custom ROM after getting all the rooting done. So I went searching for CW10.1, and tried to install it. Kept getting "Failed" every time I tried to install CW10.1 with "TWRP", so I started googling why. Well, it said I had to install the boot.img with the whole "fastboot" process where I use the command "fastboot flash boot boot.img". So I did that...and man was that a mistake.
My phone after, would just stay stuck at the boot screen. So I didn't panic, and I went into "TWRP" and tried to restore from the backup I did, before I started trying to install a custom ROM...but the same thing happened. Fast forward 2 hours and now I feel like I've screwed myself. I thought "TWRP" backed everything up, but for all I know, my moronic self might have unchecked "Boot". So I believe I need to "fastboot" the correct/original boot.img, so the phone will boot normally, but I have no idea where to find it. I've tried looking, but I'm more finding the issue is solved by using RUU. Which I REALLY don't mind doing at all, but I'm scared now since there are so many different ones, and I can't figure out which one is the right one to use. My night has taken such a crappy turn, I'm afraid if I RUU once wrong, I will be in an even bigger mess, than trying to reach out to you guys first. It's crazy how comfortable I was doing all this, and now I feel like I shouldn't have ever tried.
Here is the phone info I can provide that is hopefully helpful:
The phone is an HTC One X+ AT&T USA
EVITARE_UL PVT SHIP S-ON RL
HBOOT: 1.40.0000
CPLD-None
MICROP-None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012, 22:18:14
And I believe it was at 4.2.1 software...but I'm not 100% on that and don't know how to make sure.
Please guys, if anybody can help, I need it. I appreciate your time in reading this, even if you cannot help. I believe I either just need a stock boot.img for my phone, or linked the correct RUU (assuming I'm right in that will fix it and revert me back to having a phone again). Any questions feel free to ask me. I'm going to try to sleep now.
krayzed896 said:
Ok guys...here it goes.
I've had a long night of feeling like the biggest idiot to walk the Android planet. I just bought this phone off someone, and have done rooting/custom ROM installing before. But I messed up, and now I feel like I'm an idiot & screwed because I'm just so lost now. I love learning, but I feel like I'm in such a hole. Here's what happened:
I used "All In One Kit" to install "TWRP 2.6.0.0", and like anybody, I wanted to install a custom ROM after getting all the rooting done. So I went searching for CW10.1, and tried to install it. Kept getting "Failed" every time I tried to install CW10.1 with "TWRP", so I started googling why. Well, it said I had to install the boot.img with the whole "fastboot" process where I use the command "fastboot flash boot boot.img". So I did that...and man was that a mistake.
My phone after, would just stay stuck at the boot screen. So I didn't panic, and I went into "TWRP" and tried to restore from the backup I did, before I started trying to install a custom ROM...but the same thing happened. Fast forward 2 hours and now I feel like I've screwed myself. I thought "TWRP" backed everything up, but for all I know, my moronic self might have unchecked "Boot". So I believe I need to "fastboot" the correct/original boot.img, so the phone will boot normally, but I have no idea where to find it. I've tried looking, but I'm more finding the issue is solved by using RUU. Which I REALLY don't mind doing at all, but I'm scared now since there are so many different ones, and I can't figure out which one is the right one to use. My night has taken such a crappy turn, I'm afraid if I RUU once wrong, I will be in an even bigger mess, than trying to reach out to you guys first. It's crazy how comfortable I was doing all this, and now I feel like I shouldn't have ever tried.
Here is the phone info I can provide that is hopefully helpful:
The phone is an HTC One X+ AT&T USA
EVITARE_UL PVT SHIP S-ON RL
HBOOT: 1.40.0000
CPLD-None
MICROP-None
RADIO-SSD: 2.14.55.01
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure boot: enabled
MODEM TYPE: MDM9215M
Dec 28 2012, 22:18:14
And I believe it was at 4.2.1 software...but I'm not 100% on that and don't know how to make sure.
Please guys, if anybody can help, I need it. I appreciate your time in reading this, even if you cannot help. I believe I either just need a stock boot.img for my phone, or linked the correct RUU (assuming I'm right in that will fix it and revert me back to having a phone again). Any questions feel free to ask me. I'm going to try to sleep now.
Click to expand...
Click to collapse
i think installing an international ROM on an AT&T device was the downfall here
you need to install a ROM here for an example, by following the instructions given:
http://forum.xda-developers.com/showthread.php?t=2098218
leefear said:
i think installing an international ROM on an AT&T device was the downfall here
you need to install a ROM here for an example, by following the instructions given:
http://forum.xda-developers.com/showthread.php?t=2098218
Click to expand...
Click to collapse
No you are completely right. This is where I messed up, and everything went bad. My only problem is I'm not sure how to get the ROM on my device. Every time I try "ADB Sideload", it says it's starting...and then...that's it. I can cancel it, but it never actually goes through with the side load. What should I try to do in this case, so I can get the ROM loaded?
And thank you for your quick response, it's greatly appreciated!
krayzed896 said:
No you are completely right. This is where I messed up, and everything went bad. My only problem is I'm not sure how to get the ROM on my device. Every time I try "ADB Sideload", it says it's starting...and then...that's it. I can cancel it, but it never actually goes through with the side load. What should I try to do in this case, so I can get the ROM loaded?
And thank you for your quick response, it's greatly appreciated!
Click to expand...
Click to collapse
assuming you have the htc driver installed for your device, adb commands should work, can you test with adb devices that should list your phone, if not get your htc drivers installed and make sure you have latest adb on your pc
move NAMEOFROM.zip to adb folder and use the sideload option in twrp and sideload rom and should work
and don't forget to flash the boot.img provided
question rolermi
leefear said:
assuming you have the htc driver installed for your device, adb commands should work, can you test with adb devices that should list your phone, if not get your htc drivers installed and make sure you have latest adb on your pc
move NAMEOFROM.zip to adb folder and use the sideload option in twrp and sideload rom and should work
and don't forget to flash the boot.img provided
Click to expand...
Click to collapse
I definitely have the drivers installed, mostly because they were required as part of rooting with "All in One" tool. I never installed anything for ADB, I simply assumed it was just used as an option in "TWRP", so I'll go download that. Thank you, and I will update with my results!
Ok, posting an update!
Thank you for your response, as this fixed my problem! I will sum up my problem/fix in this reply, in case anybody is also trying to fix the same problem.
I have at HTC One X+ for AT&T
I was in a boot loop, after I had successfully rooted my phone with TWRP. I used "fastboot" method to change the boot.img, and lost my original in the process. Stuck only being able to boot to the system, or recovery, I needed a way to fix my boot problem. The suggested method worked flawlessy. I downloaded Android SDK, installed Platoform-Tools from the SDK Manager. Opened up ADB in ADT>SDK>Platform-Tools and followed the necessary steps for "pushing a ROM with ADB" I had found. I used the recommend link above for ViperXL+. I was able to push the ROM in, boot into recovery, and finally install a proper ROM. I then did the "fastboot" method to install the ROM ViperXL+'s boot.img (As a side note your .zip might show up as "sideload" and not the ROM title for the .zip I didn't know this, and thought it somehow lied to me is 100% completion, until I tried selecting "sideload" to install, which I didn't believe to have seen before. And sure enough it was the ROM)
Now my phone boots sucessfully, and I have a custom ROM. THANK YOU so much for your help, big kudos to leefear for explaining what I needed to do, and linking me the ROM. I appreciate it so much man!!!
krayzed896 said:
Ok, posting an update!
Thank you for your response, as this fixed my problem! I will sum up my problem/fix in this reply, in case anybody is also trying to fix the same problem.
I have at HTC One X+ for AT&T
I was in a boot loop, after I had successfully rooted my phone with TWRP. I used "fastboot" method to change the boot.img, and lost my original in the process. Stuck only being able to boot to the system, or recovery, I needed a way to fix my boot problem. The suggested method worked flawlessy. I downloaded Android SDK, installed Platoform-Tools from the SDK Manager. Opened up ADB in ADT>SDK>Platform-Tools and followed the necessary steps for "pushing a ROM with ADB" I had found. I used the recommend link above for ViperXL+. I was able to push the ROM in, boot into recovery, and finally install a proper ROM. I then did the "fastboot" method to install the ROM ViperXL+'s boot.img (As a side note your .zip might show up as "sideload" and not the ROM title for the .zip I didn't know this, and thought it somehow lied to me is 100% completion, until I tried selecting "sideload" to install, which I didn't believe to have seen before. And sure enough it was the ROM)
Now my phone boots sucessfully, and I have a custom ROM. THANK YOU so much for your help, big kudos to leefear for explaining what I needed to do, and linking me the ROM. I appreciate it so much man!!!
Click to expand...
Click to collapse
hey buddy, glad you got it working, nothing worse than a broken phone! glad i could help! now, hit that thanks button!
ooh, my 200th post!
leefear said:
hey buddy, glad you got it working, nothing worse than a broken phone! glad i could help! now, hit that thanks button!
ooh, my 200th post!
Click to expand...
Click to collapse
Congrats on the 200th post! Sorry, very new to using the forums. I hit thanks on all your posts in the topic! :good:
Hi,
i have the same problem but it's a non LTE version HOX+ can someone advise on another ROM that will work in the same way?
Hi there and thanks for looking.
I have an HTC one x+ hboot 1.72 O2 Uk O2__001
The bootloader is unlocked via the htcdev site. If I lock the bootloader, I cannot boot the phone at all.
I tried to install android revolution but cannot get it to install.
I did however install the bootloader but I lost wifi and radio when the normal rom booted. Which is 4.2.2
I have tried installing endeavoru recovery and clockwordmod recovery but neither give me an install from sdcard option. (if they have indeed loaded as I am getting no difference in boot menu and nothing happens when I click recovery.
I keep following links to ruu files etc but they seem to be broken links and I really have no idea what to do now. Or which files to use.
So I think the main problem is I have a custom bootloader but stock rom.
Hope you can help.
Thanks
Managed to sort it by following Lloir's post here http://forum.xda-developers.com/htc-one-x2/help/radio-zip-enrc2bu-please-t2882380
I had been using the wrong clockwordmod so that explains why recovery wouldn't work.
Although I couldn't seem to get the 2014 folder to load across, I did manage to flash the supplied boot.img which turns out was all I needed after all.
I am just posting this in case anyone has the same issue and looks in the wrong places and gets more confused as I did.
So I would like to say a heartfelt thank you to him for posting the files I also needed.
Thank you.
richardaustin said:
Managed to sort it by following Lloir's post here http://forum.xda-developers.com/htc-one-x2/help/radio-zip-enrc2bu-please-t2882380
I had been using the wrong clockwordmod so that explains why recovery wouldn't work.
Although I couldn't seem to get the 2014 folder to load across, I did manage to flash the supplied boot.img which turns out was all I needed after all.
I am just posting this in case anyone has the same issue and looks in the wrong places and gets more confused as I did.
So I would like to say a heartfelt thank you to him for posting the files I also needed.
Thank you.
Click to expand...
Click to collapse
Glad to have helped. I'm assuming it was this post?
http://forum.xda-developers.com/showpost.php?p=55562048&postcount=14
Yes it was that one, followed by your uploads of the files required.