So I'm very new to all of the rooting stuff. I got an HTC 4G LTE off Ebay just to use as sort of like a tablet. The firmware on the phone kinda sucks so I wanted to root it and go with a better version of Android that the bloatware-inflated version HTC provides. Not to mention updates are no longer supported.
I successfully rooted the phone with TWRP and followed the instructions to wipe the phone and such. This is where the instructions I found were kinda "off" and started using way too much lingo so I decided to wing-it a bit, thinking I had sort of understood it. I went to install, installed the BeanStalk and Gapps zip folders that are available in the the other section.
Rebooted my phone and it wouldn't go past the HTC boot logo... So I tried again. No luck.
I managed to get back in TWRP and I'm wondering what I need to do in order to get this bad boy to work. I checked the troubleshooting threads and found the section on boot-looping, but so I did the cache wipes it stated, selected "Factory Restore" and it rebooted back into TWRP. I'm not really sure what to do. Do I re-install the BeanStalk and Gapps zips, or am I missing something?
Thanks for any help.
If the phone is S-on you'll have to flash the kernel separately from the ROM itself. Hit the top link in my sig and read the entire guide. I think it will be quite useful to you:thumbup:
Related
I've searched the forums, and maybe I've just not searched correctly, or for the right thing, but I've not been able to find any information specific to my problem.
Anyways, here's what's happening.
Just picked up a new Sprint HTC Hero, followed step by step instructions to root the phone, no problems whatsoever. Made my nandroid backup, saved to the root of my sdcard, no issues there.
Immediately afterward, I downloaded the Black Sense skin, stuck it in the root of the sdcard, renamed to update.zip like instructions said, turned the phone off and rebooted in recovery, installed the update from the sdcard, rebooted, and now is stuck in a boot loop.
I get the sprint animation, the hero logo with the little android guy, and the HTC splash screen, and then just goes back and does it again.... forever. I have not loaded any other ROM or done anything else with the phone, just rooted the phone, dl'd the theme. Now I have heard about loading a different ROM on the phone, but is this required for the Themes to work? If it is, how would I be able to tell which ROM's are compatible with my phone? Sorry guys, I'm new to this, just trying to pick up info as I go.
Most all of the other threads I have found are directed to other phone users who have installed a Hero ROM on a Tmobile G1 or something like that. I haven't been able to find anything specific for my device, so I'd appreciate any help you all can give. I'm sure its a pretty simple fix, any help?
I had the boot-looping problem on my rooted T-Mobile G2 Hero, and I fixed it by wiping everything from the recovery menu. I dunno if this will help you, since I'm not sure what the differences between Sprint, HTC and T-Mobile's version are, but it might be a good start. :S
thanks
thanks for the quick reply. As usual, I found a boatload of info right after I posted the original thread. I think what I needed to do was to download find and download a rom that is compatible with my version of Hero and android, then find a theme that I like, and then try to update with the theme.
That's about as far as I've got, I'm poring over every bit of info I can find, but its confusing as hell, and poor grammar makes it even harder to understand.
nuformzdesign said:
thanks for the quick reply. As usual, I found a boatload of info right after I posted the original thread. I think what I needed to do was to download find and download a rom that is compatible with my version of Hero and android, then find a theme that I like, and then try to update with the theme.
That's about as far as I've got, I'm poring over every bit of info I can find, but its confusing as hell, and poor grammar makes it even harder to understand.
Click to expand...
Click to collapse
If you did a nandroid backup? boot into recovery and restore the backup, that should reset everything unless you flashed the skin and then did the backup? in that case download a rom for the cdma hero (guessing thats what you have?) rename it update.zip and put it onto your sdcard, boot into recovery and wipe EVERYTHING!, then flash your update.zip. only install themes for specific roms.
yea, had no problem with making the nandroid backup, and after the boot-loop, I pulled the battery and then booted in recovery to restore. No problems there.
I guess I just didn't get enough info before I started messing with the device. Thanks for the help tho.
So, after owning my Transformer Prime for about a month now, I decided to take the plunge and root it. I followed the instructions for ViperMod and had it rooted in no time. I then followed the instructions of unlocking the bootloader and finally installing OTA Rootkeeper.
I've had rooted devices in the past (Droid Incredible) and am familiar with RomManager. So I installed RomManager on the Transformer Prime. I then attempted to create a backup of my "current Rom", which is just stock ICS. RomManager prompted me to update Clockworkmod Recovery, which I did (I now have 5.8.2.0 installed). It then rebooted...acting like it was backing up my current Rom, but when I got back into RM, and clicked "Manage Backups" and there was nothing there. I tried once more with the same result, and ultimately gave up on backing up my current config.
I then downloaded Cyanogenmod 9 (nightly). I selected Google Apps and it proceeded to download. I got an error that the Google Apps portion had an error, but it seemed to work when I attempted to download it again.
I then proceeded to attempt to install the new Rom. The menu came up, asking if I wanted to wipe data and cache, wipe dalvik and backup current rom. I selected all three and hit ok.
My tablet rebooted...quickly, and did not show any signs of installing Cyanogenmod. Sure enough, I got my stock ICS...no Cyanogenmod. I tried again...same thing. I tried a third time, and RomManager hung when I tried to select Ok after the options of backing up, etc. Ultimately I got the error popup, asking if i wanted to wait/report/ok. I hit ok.
I then...very stupidly in retrospect...performed a factory reset from within the phone's settings menu (something I've later read is a big no no). This time, when my phone rebooted, it went straight into Clockworkmod Recovery, which is where I am now. Stuck. I've read a ton and tried everything but had no success.
Strangely, I can find the cyanogenmod file by navigating through "install zip from sdcard", then "choose zip from sdcard", then "clockworkmod", then "download", then "get.cm", then "get" and finally "update-cm-9-20120301-NIGHTLY-tf201-signed.zip". And it allows me to update using this file...even giving me the message "Install from sdcard complete"...but nothing happens. I'm still stuck in Clockworkmod.
If anyone has any advice, I'm begging for your help. Really hoping I didn't ruin my brand new tablet...
Thanks.
only thing rom manager is gold for on the prime at the moment is getting the latest CWM version. other than that, trying to flash a rom, reboot into recovery, or backup doesn't work in rom manager for prime. everything needs to be done through CWM itself. whether flashing a rom or making a nandroid backup. so you have to manually go into CWM and try flashing from there. did you make sure the roms were stored on internal memory to flash(I believe it can only be done on prime this way at the moment)? try a different rom as the CM9 has alot of bugs n issues at the moment. try flashing virtuous rom or a stock modified rom from developement.
also check out developement section for a thread called the Di's n Donts of unlocking and thread called how to or not unbrick your prime. answers you seek are in there.
See my unbricking thread
http://forum.xda-developers.com/showthread.php?t=1514088
Thanks so much for your help guys!
to demandarin: Unfortunately the only ROM I downloaded before everything went haywire was the nightly cyanogenmod 9 from yesterday. And as I explained, that ROM doesn't seem to be flashing for me... I've tried downloading other ROMs onto my SD card, but I can't seem to get my Prime to recognize the SD card in CWM, and I can't figure out any way to get ROMs onto my prime...now that its stuck in recovery. Do you know if I can load ROMs onto my Prime at this point?
to Diamondback: I read your unbricking thread and its given me some hope. It sounds like I'm falling into the "1a" category. I'll have to bunker down tonight and see if I can work through those instructions (I have no familiarity with ADB at this point, which is my main concern). Anyway, I very much appreciate you pointing me in the right direction.
I am curious though, is there some place I can look for clarification on what works in RomManager and what does not? None of that was made clear in the app itself, so I just assumed it was fully functional, like it was on my Dinc. Now I'm paying the price...
Thanks again.
original old thread on CWM on Prime...look through page and people state what works n what doesn't.
http://forum.xda-developers.com/showthread.php?t=1510983
new thread created today on a new updated CWM that should be used. has alot of issues that didn't mesh well with Prime and CWM fixed. seems like you might have jumped the gun a lil early. this is latest version thread. you can also get the latest version through rom manager.
http://forum.xda-developers.com/showthread.php?t=1533697
good luck!
demandarin said:
original old thread on CWM on Prime...look through page and people state what works n what doesn't.
http://forum.xda-developers.com/showthread.php?t=1510983
new thread created today on a new updated CWM that should be used. has alot of issues that didn't mesh well with Prime and CWM fixed. seems like you might have jumped the gun a lil early. this is latest version thread. you can also get the latest version through rom manager.
http://forum.xda-developers.com/showthread.php?t=1533697
good luck!
Click to expand...
Click to collapse
Thanks, but I actually do have the latest version of CWM (5.8.2.0), according to the link you provided. The thing is, I'm just very unfamiliar with CWM, or really any recovery software. The link you posted notes the following improvements:
-Possibly fixes bricks (by properly restoring boot.img)
-Correctly comes with Staging/System unmounted
-Nandroid Restores properly the boot.img (of backups created with this CWM). This means no more issues when restoring a Rom if you are coming from another from (for example, if you are restoring Virtuous after wiping cm9)
Which all sounds great, but I have no idea how to really use any of that... Does "possibly fixes bricks" apply to my situation? I've tried selecting restore and advanced restore through CWM, but in both situations it says "cannot find files", which I'm assuming are the "boot.img" being referenced. So again, it seems like I'm hosed...
I'm just really hoping that Diamondback's unbricking method works for me. Though, I'm having a hell of a time finding instructions on how to setup ADB on my PC (Windows 7). Do you know where I can find good and current instructions?
you can Google it but plenty of YouTube view on how to set up adb.
there's a thread here on it though. take a look: http://forum.xda-developers.com/showthread.php?t=1427008
demandarin said:
you can Google it but plenty of YouTube view on how to set up adb.
there's a thread here on it though. take a look: http://forum.xda-developers.com/showthread.php?t=1427008
Click to expand...
Click to collapse
Thanks again! I think I need a tutorial on how to search XDA more effectively
SUCCESS!
Well, it took some jumping through hoops, but once I got ADB set up successfully, Diamondback's instructions worked like a charm!
For anyone encountering this thread with the same issues as me, I've included links to all of the sources of data I ultimately used.
Thanks so much for everyone's help!
Installing ADB
http://forum.xda-developers.com/showthread.php?t=1427008
http://www.youtube.com/watch?v=ZY4KSrgi-rE
I had to use the PDANet method, referenced in the Youtube video
http://junefabrics.com/android/download.php
Diamondback's Instructions for Unbricking the Prime
http://forum.xda-developers.com/showthread.php?t=1514088
Perhaps I spoke too soon...
My device is no longer bricked, but now I can't access CWM, can't factory reset...can't do anything. I'm stuck with a very broken build of Cyanogenmod 9
Here's the link to my new thread:
http://forum.xda-developers.com/showthread.php?p=23349041#post23349041
Back Story: Just rooted my phone (after a factory reset). I also checked the root. Thought why not flash a ROM to get rid of all this bloatware. So I chose Cyanogenmod. Downloaded it to my phone through ROM Manager. It thought my phone storage was my phones internal memory. I looked up how to fix this but all I could find was this thread which just said use a different installer.(the thread http://forum.xda-developers.com/showthread.php?t=1957600) Being to much of a noob to fix the problem I had no choice but to switch. I downloaded ROM installer. ROM installer recognized my SD card and downloaded CM (10.2) and google apps (4.3). Flashed a recovery, which I cant find for you because for some reason I cant look at the that menu in ROM installer(but it was the top one of the second set of files). Then I went into the installer and clicked both CM and google apps and turned on wipe data and cache but NOT backup existing ROM. It rebooted and I got the green android with installing under it. Some text in the top left I don't remember. Then under installer there was something like don't turn this device off. It stood on that menu for at least 30minutes and I knew something was up. So I looked it up and found this thread (http://forum.xda-developers.com/showthread.php?t=1957600). They said to factory reset it, which I did, so I thought whatever Ill do it again. I went into boot recovery canceled the installation and tried to factory reset.
Actual problem: The actual problem is it seems I am stuck in some kind of limbo. My phone works perfectly fine when I boot into recovery but when I try to factory reset or try to install CM again it just sits on that green android screen instead of going back to stock. Since I foolishly didn't back up my ROM as far as I know I can go back. I tried to look up what to do but I am truly stumped. I just want CM on my phone and I don't know what to do from here. Any ideas? If there is a thread that goes over this im sorry for reposting and please refer me to that thread. Otherwise thank you for any help.
Phone Device number SCH-I545
Android 4.3
Kernel version: 3.4.0
Build Number: JSS15J.I545VRUEMK2
If there is any other Info you need Ill post asap.
Again thank you for any help.
Thaumaz said:
Back Story: Just rooted my phone (after a factory reset). I also checked the root. Thought why not flash a ROM to get rid of all this bloatware. So I chose Cyanogenmod. Downloaded it to my phone through ROM Manager. It thought my phone storage was my phones internal memory. I looked up how to fix this but all I could find was this thread which just said use a different installer.(the thread http://forum.xda-developers.com/showthread.php?t=1957600) Being to much of a noob to fix the problem I had no choice but to switch. I downloaded ROM installer. ROM installer recognized my SD card and downloaded CM (10.2) and google apps (4.3). Flashed a recovery, which I cant find for you because for some reason I cant look at the that menu in ROM installer(but it was the top one of the second set of files). Then I went into the installer and clicked both CM and google apps and turned on wipe data and cache but NOT backup existing ROM. It rebooted and I got the green android with installing under it. Some text in the top left I don't remember. Then under installer there was something like don't turn this device off. It stood on that menu for at least 30minutes and I knew something was up. So I looked it up and found this thread (http://forum.xda-developers.com/showthread.php?t=1957600). They said to factory reset it, which I did, so I thought whatever Ill do it again. I went into boot recovery canceled the installation and tried to factory reset.
Actual problem: The actual problem is it seems I am stuck in some kind of limbo. My phone works perfectly fine when I boot into recovery but when I try to factory reset or try to install CM again it just sits on that green android screen instead of going back to stock. Since I foolishly didn't back up my ROM as far as I know I can go back. I tried to look up what to do but I am truly stumped. I just want CM on my phone and I don't know what to do from here. Any ideas? If there is a thread that goes over this im sorry for reposting and please refer me to that thread. Otherwise thank you for any help.
Phone Device number SCH-I545
Android 4.3
Kernel version: 3.4.0
Build Number: JSS15J.I545VRUEMK2
If there is any other Info you need Ill post asap.
Again thank you for any help.
Click to expand...
Click to collapse
You're going to have to use Odin to get back to stock MK2. Research how to do it. Then go to this thread http://forum.xda-developers.com/showthread.php?t=2606501 and read the WHOLE thing. Pay special attention to the stuff typed in RED.
I can't believe you tried to do any of this with a mk2 phone...countless discussions on what you can and can't do with a S4 based on phone's firmware build number.
Sent from my SCH-I545 using XDA Premium 4 mobile app
So im fairly new to unlocking, flashing, etc. I have a HTC One M8 for AT&T that im trying to unlock to use with different carriers. After reading a bit I realized that I had to unlock my bootloader, root, install s-off before I could achieve my goal. I used htc-one.wonderhowto. com/how-to/unlock-bootloader-root-your-htc-one-m8-0154444 to root and unlock my bootloader. Followed the guide to a T and all was fine. Then I was going for S-Off and here's where I encounters my problems. I used htc-one.wonderhowto. com/how-to/get-s-off-your-htc-one-m8-install-custom-firmware-mods-0154461 guide and this is where I believe I fudged up bad. Step one says to download InsertCoin from insertcoin-roms. org/category/devices/onem8 this link. I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM and that's why im having this problem but im not sure. I followed each step with the exception to Step 3 which is also where I fudged up. I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything. At step 5 my life changed forever..lol.. but when I flashed it , it said failure. I tried to follow the steps again but it kept failing to flash. So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. Which says ***unnlocked*** and ***tampered*** at the top and im stuck. Please someone help me and tell me what to do.
I recently deleted my OS by my stupidity. I fixed the issue by side loading a stock Rom via adb/twrp sideload. Saved me. There are tutorials on how to do this. Just Google search. You could also put a stock Rom on an external sd and flash that way. Don't have a link to the stock Rom I used, but it's in the resources thread in general section. Hope this works for ya
Sent from my HTC One_M8 using XDA Free mobile app
vansslamcityjam said:
I downloaded the OTA 4.0.6 to 4.0.7 and saved it onto my phone I think maybe I should of downloaded the link for the full ROM
Click to expand...
Click to collapse
The file you downloaded is if you were already on InsertCoin 4.0.6, and updating to version 4.0.7, which was not the case for you. You should have downloaded the full ROM, and that is likely why the flash failed.
If you ever have any doubt about what you are flashing, this should be a red flag to STOP and either read and research some more, or come on here and ask.
vansslamcityjam said:
I didnt back up because I didnt think it was needed since the phone was just wiped clean of everything.
Click to expand...
Click to collapse
That is why you make a TWRP backup before wiping anything.
vansslamcityjam said:
So I went back and tried to re-flash SuperSU which was successful but when I go to reboot it from TWRP it says I have no OS installed and it gets stuck on the HTC boot screen unless I put my phone into fastboot mode. .
Click to expand...
Click to collapse
Did you specifically wipe system in TWRP? If so, that is where the OS is stored, so of course wiping it means you have no OS.
I do not advocate wiping system when flashing ROM, especially if you are new to this. Reason being, it already gets wiped when you flash a ROM anyway (so its redundant). Also, if the ROM fails to flash, you will still have a working OS if you did not wipe system manually. As stated on the wipe screen in TWRP, the default wipe (data, cache, and Dalvik) is all that is usually needed. It says this for good reason.
All you need to do is download a ROM to your computer, and either adb push to the phone, sideload flash, or copy it to a removeable MicroSD card using a USB card reader. Then flash in TWRP.
I thought you guys might find this amusing, and hopefully it will help some people that get into a similar situation as myself. First, a little background - I rooted and installed Alliance Rom years ago back before the bootloader was unlocked. This worked amazing for me for a long time but I've recently had some weird issues with my phone so I decided to do a factory reset.
I went into settings, clicked factory reset, and then my phone got into a boot loop on recovery. I remember from before I had to do a regular boot then click recovery at the prompt instead of doing the factory recovery so I did that.
Instead of doing a normal wipe, I wanted to wipe everything on my phone and start from scratch so I did the full wipe (in what I think was TWRP or safestrap or whatever). When I went to reboot my phone it had a message like "are you sure? there's no OS installed" and I clicked ok. Well now I couldn't get the phone to boot into anything except download mode so at least I can use Odin.
I'm frantically searching google to try and find ways to install some sort of recovery so I could load AllianceRom again since I still had the zip file for it. Eureka, I found TWRP for my phone! I tried to flash TWRP through Odin but that doesn't work because my bootloader wasn't unlocked.... I remember this from last time ... all of the places I found online to install any sort of recovery required the phone to be booted into android.
So I'm clicking around and someone has a recovery randomly posted in a thread so I install it thinking, what the hell, what's the worst that could go wrong. So I install it through Odin and boot into normal recovery and I get this message saying my phone has been tampered with and to go to a verizon store immediately! Oops... upon further investigation (looking at the download screen), I tripped the knox flag... oh well, it's not like my phone is in warranty anymore (I got it on release day).
I search around looking for what I should do next and I found a thread that talked about being on complete stock, rooting, then unlocking the bootloader. I download all the files I need (newest firmware here - https://www.sammobile.com/firmwares/galaxy-note3/SM-N900V/ and thread here - https://forum.xda-developers.com/ve...guide-ob6-of1-root-bootloader-unlock-t3439010) to go back to stock and flash in Odin. Actually I didn't download from sammobile.com because it was downloading too slow so I just googled the file name and found it somewhere else faster, go figure.
Everything seems to be going ok then all of a sudden FAIL in Odin... Ahhh what the heck do I do now? Try again obviously! Second try works woo hoo! Phone start booting up, things are looking good!!! hooray!! But wait... it's taking forever to start and it's stuck on the Verizon logo... uh oh... taking way too long to boot up so I pull the battery and try again. Boots right in saying that android is upgrading so I think I'm finally in the home stretch here.
I try to run the ArabicToolApp for Root but I installed the latest firmware which isn't supported DAMN IT! Downloaded the correct firmware (OB6!), flashed in Odin, same problem before where it was stuck on the red verizon screen, pulled battery, rebooted, finally time to get root!
Phone finally boots into OS and I get a popup "unfortunatley com.google.process.gapps has stopped" great... and it keeps coming up over and over again after I hit ok... just my luck! Reboot again to see if that fixes the issue. Seems weird that I didn't have to go through all the initial setup stuff I did on the other version I installed... hmm... or maybe it was because I pulled the battery on the red verizon screen? Whatever. I somehow manage to get to options to do a factory reset and I let the verizon screen stay on a while this time. I'll go take my contacts out and give my wife some love while I wait
Come back and the phone is at the setup wizard, this is good news. Enabled USB debugging, installed root, done! Thank god!
Next I want to unlock the bootloader. I follow the steps here which aren't very clear (I'm guessing on purpose for novice computer users) - https://forum.xda-developers.com/ve...l/official-note-3-verizon-bootloader-t3359370
1. I installed eMMC from the play store to make sure my CID started with a 15, it does so I know I'm good to use the hack.
2. I installed both files in the unlock kit (adb and driver setup)
3. Fired up adb, navigated to where I had unlock_n3, and ran through the first part of the code once, reboot my phone, checked that the CID was the developer CID, and then ran the second part of the code three times before it worked
I verified the bootloader was installed correctly by trying to install TWRP through Odin, which worked!
I'm going to try out Jasmine Rom since it's a popular one that is on 5.0. My SD card only showed 30 megs free or something like that, so I formatted it from within android and copied the zip file over and installed the Rom through TWRP. Rom installed just fine, so I did one last factory reset which worked great and I think I'm finally good to go!
If you have any questions or run into any issues feel free to reply here and I'll try to help as much as I can.
Glad it worked out for you in the end.
From making a few mistakes I know that sinking feeling "oh no, what have I done?"
FWIW, the bootloader unlock method (in principle) works from nearly ANY ROM which is rooted - so, you would have saved yourself a bunch of time if you had started with that before you wiped the Alliance ROM. So long as you have root and a CID value that starts with 0x15, you just need root privileges - no need to return to stock and re-root.
(The "in principle" part is that there were several bugs in the "safety checks" portion of the unlocker binary that were sensitive to the OS revision, so you might have to search through the unlock thread to find a version of the unlock binary that is compatible with whatever rooted ROM is on the phone when the unlocking is attempted.)
good luck
PS The AryaMod ROM (w/ phantomOne kernel) is pretty solid - Marshmallow w/ S-Pen apps, too! As with any other dev ROM, there are a few sharp edges, but mostly everything works (except NFC).
.