hello everyone,
noob here as this is my first post
i'm sorry for the book in advance, i just wanna give everyone the whole story.
i'm having problems with my at&t htc one m8. i've rooted it and installed twrp and supersu on it no problem(first time rooting) and made several nandroid backups. i made a stock back up and flashed to viperone rom played around on that for a while.
couple days later i still wanted to try other roms and explore what other roms had to offer, so i installed cyanogen mod 11, had some fun on that one. so i made a back up of this as well.
i then decided to try the google play edition [gpe] for the m8.(am i a flashaholic yet?) after this i wanted to compare the stock rom to the gpe rom sense i haven't used it in about a week.
heres where the problem begins:
so i tired to restore my stock backup and it gets past the at&t boot animation then goes to the htc one boot animation and freezes (or boot loops i guess). i figured maybe its loading or something but after 20 mins i got worried so i plugged it into my computer and rebooted it using the command line and command adb reboot boot loader. (thankfully it worked and i remembered this from the root video i used to guide me through the rooting process) it does this every time i restore that backup. so now i have three different roms backup and they work fine i can flash to and from any of them but the stock rom.
i did some digging and found that on cwm it might not backup the the boot.img or something about a partition?(figured it might does this on twrp as well) i know nothing of either. this is my only stock rom backup. i've looked for a stock rom to flash and can't find one so i'm hoping you guys can help me fix this backup so i can get stock sense 6 back.
as i said i'm a noob if someone could tell me what to do step by step to fix this or show me my mistake so i don't do this again. if it's fixable or give me a different solution or thread to get this problem fixed
i have sd card on the way if that matters. i am running low on memory on my internal sd.
any help will be greatly appreciated again sorry for the book.
i am assuming that you flashed the GPE RUU, if so here is how to get back to stock from that. http://forum.xda-developers.com/showthread.php?t=2721435
Thanks is there a way I can just flash between all of them or does the ruu stop me from doing so?
Until there is a RUU.zip for Stock unlocked or dev edition, it is a bit more complicated going from one to another
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Related
My last HTC Thunderbolt, I had used the [ALL IN ONE] The HTC Thunderbolt Tool! to root my phone. This went well.
I then did a backup of the phone using clockwork mod. Then I flashed leanKernel: minimalistic kernel, which now I realize is a CM7 kernel?
The problem fallowed the kernel flashing. It would boot through the HTC boot image, then through the Thunderbolt logo and straight to a black screen. After that I decided to restore the factory backup before the kernel after wiping data and the system. The problem was after restoring the backup of the original rom the phone bricked. I couldn't get it to boot past the white screen with the HTC screen. Thing is before this phone I had a Nexus S 4G so my first official task on that phone was rooting and flashing custom kernels and roms. At this point I'm not sure if the phone was faulty or if I botched the job somewhere.
If you flashed the wrong kernel for the rom the fix was as easy as wiping cache / dalvik and flashing the correct kernel. As far as you backup you might have a corrupted backup which could be why it bricked. Your SD card may be corrupted too and could be why the backup was corrupted. Maybe try backing the SD card up and reformatting it just to be sure.
Sent from my ADR6400L using Tapatalk 2
Thanks for the response. I thought as much actually. I had already had the phone replaced. It had other issues since the first day I had it. I literally had it 4 days and in those 4 days it would just randomly restart and that was all factory. Lucky for me the Manager of the Verizon store sold us the phones. He just replaced it, but mainly because we had a lot of other issues. I'm actually feeling brave enough to try it again. The only thing that bugs me is the RUU thing. On my old phone it was way simpler.. well.. I had it for a year so it was probably just simpler to me. Either way, I guess the question now is what would be a good kernel for the factory rom? Until I find another rom I want to try? I wanted to hold out for the ICS update but I doubt it will happen after all the reading I've done.
Edit: Yes, I understand that asking for a good kernel for the stock rom is asking for opinions, but that's what I'm looking for.
Imos leankernel for gb sense would be the best. You should still think about reformatting your SD card though.
Sent from my ADR6400L using Tapatalk 2
I checked my SD card's download section and guess what I found. imoseyon_leankernel_v5.1.0GBS.zip This is what I flashed to my last phone. From what I gather this should work with sense 2.1 Android 2.3.4, Software number 2.11.605.19 710RD Now I've got to figure out why this bricked my last phone. I should also mention that I did 2 backups. One with Clockwork mod and another after flashing to EXT4. I tried restoring both in EXT4 and no such luck. Keep in mind, this is an old issue but I'm just baffled as to what happened. The SD card seems fine from what testing I've put it through though.
http://forum.xda-developers.com/showthread.php?t=1260185
the thread I got said kernel from.
You need to use 6.2 for 605.19. That shouldn't have bricked you though. From what you've stated though all I can gather is that the backup is bad.
Sent from my ADR6400L using Tapatalk 2
When you say 6.2 are you talking about a kernel version? If so then I thought 5.1.0 was the most recent, as noted by that thread. Am I missing something?
Well... scratch that question.. I did a quick google and noticed that it's not on these forums. >.>
Edit: Ok. Before I get too far into this. I've rooted, and did a backup with revolutionary CWM. I decided to check out the files in the backup on the phone and some files I can open while others throw back a "Cannot Open File: it does not appear to be a valid archive." with winzip and they also give me an error with 7zip. Should the boot.img file give this error? I can't go off of the MD5 as it was generated by these files.
I could see that happening with a windows computer. I don't know which ones it can open honestly. The only way that you will really be able to tell is from the md5 or just by assuming that is bad because of the first unsuccessful restore.
Sent from my ADR6400L using Tapatalk 2
Yeah, I completely scrapped everything from the last phone's rooting process.
I think I'll do another backup just to be on the safe side.
Edit: thank you for your help. I am now rooted and custom kerneled. I think this is pretty much what I wanted. I'll worry about custom ROMs later on down the road.
Sent from my ADR6400L
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
NoClemency said:
I just rooted my new HTC EVO LTE phone recently because I had to get a new one. Any way, after rooting it, I imminently made a nandroid back up. Then I flashed a few different roms and recoverys. However, what I found out is after I flash a new rom, my wifi says error and won't turn on. I'm not sure what the problem is. And yes, I cleared everything out before flashing a new rom. However, what is even more interesting is I can use my recovery that I made after rooting my phone to go back to the stock rom and it has no trouble with the wifi. I'm not sure why I'm getting this error or how to fix it.
I've thought about flashing some new radios, but I've had issues in the past with this phone trying to make it S-Off, so as a result it is currently S-On. I would like it to be S-off, but after having a lot of experience with it, I've learned it is very time consuming to do and it is a pain to get it to work, it almost always bricks my phone and then I have to go unbrick it in Linux.
I'm planning on running through the rooting method again to see if that does anything, but I'm doubtful. I've also tried updating the prl, profile, firmware and HTC software with no luck. Let me know if anyone has any suggestions. Thanks.
Click to expand...
Click to collapse
S-OFF is really the way to go if it's still an option for you it's the only way to get the new firmware without relocking and taking the OTA then unlocking and rooting again read post 2 in the lazypanda thread found here http://forum.xda-developers.com/showthread.php?t=1737123 just go down the list and verify everything works before running lazypanda there are plenty of members that subscribe to that thread so there is plenty of help availiable
Also, rerooting won't do anything. You're already rooted? Think the problem is in the rom u installed. Possibly a bad download. Try downloading from a good connection and install it again. If it is close to stock like flex's stock w goodies just clear cache and dalvik in recovery.
And what do u mean u tried a few recoveries? Cwm doesnt work well with the evo LTE. Try twrp 2.2 and leave it alone until its updated again.
What is your hboot? What rom did you try flashing?
Sent from my lair.
Im also getting this issue and i know its not anything to do with rooting and all that since ive been rooted since i picked this up from best buy on preorder release day and ive been flashing and running the same rom and mods forever now also i was using wifi yesterday soooo yea lol
Recognized Hooker Killer
First, I don't believe I can make my phone S-off, because it has software version 2.13.651.1 710Rd on it and even though I do have a nandroid back on 1.13 hboot, for the default rom from a long time ago with my old HTC EVO LTE, I can't flash back a hboot to 1.13 so I believe I'm stuck S-On for now. Let me know if I'm wrong.
I've attempted several different roms including fresh rom 5.1.1, viper4G_1.0.0, and a jelly bean rom (cm-cfX-20120904-OFFICIAL-jewel all with the same problem. As for recoverys, I should have said I've tried restoring back to several different nandroid backups that I created in the past that were working just find with my old HTC EVO LTE.
Right now my phone is unlocked and rooted. I am running H Boot-1.19.000, I am S-On, and Radio-1.12.11.0809.
I know this problem has something to do with flashing new roms, because when I do a nandroid back up to the default rom, I don't have this problem, and the wifi is working great, I only have this problem if I try to flash any custom rom or use a nandroid backup that I made with my old HTC EVO LTE.
Again, this is not my first time around the track with an HTC EVO LTE, this just happens to be a new phone that I recently got from Sprint when they were thinking my dropped calls were caused by my phone when in fact they figured out they had a tower down. Since then, the tower is back up, so that is why I just rooted this new phone they gave me.
Let me know if you have any suggestions or if you need anymore information.
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Please Help
NoClemency said:
It's been while now, and I haven't gotten a real response back yet, and I was wondering if anyone knows anything that will help me out? Thanks.
Edit: Found out that I simply needed to flash the boot.img manually of what ever custom rom that I want to switch to in order to get around being S-On.
Click to expand...
Click to collapse
Hey im having the same exact issue I however went back to my stock backup from right after I rooted. The issue I had was I flashed a CMX nightly. I had been running them fine and suddenly everything went haywire i was bootlooping but only after about 30 seconds after the rom would load up. I'd have just under a minute to fish around and the it would reboot again. it was in this short window that I saw the wifi error and that it would not connect to the sprint network at all for voice or data. Im S-On Hboot 1.15 Evo LTE. I used Flash GUI to go from Stock sense to CMX as im sure youve figured out you have to do. Since i had backups of previous CMX nightlies I tried to just restore But none of my nandroids would fix the looping issue I managed to flash the boot img from the CMX rom i was previously on through adb/fastboot and it took but still my device kept looping. Finally i found this http://forum.xda-developers.com/showthread.php?t=1917106 but I didn't have any Sense Based Roms only my Stock Nandroid back up. So i used the Boot Image Flasher Tool, it took, then Instead of rebooting the system I went straight to my custom recovery and restored my Stock Sense BackUp since the tool flashes the stock sense kernel. To my relief the phone booted right up no problem connected to the network and all but to my dissmay the wifi is STILL broken somehow it says error and will not switch on. Everything else seems to be working fine though. This is crucial there is no way I can go without wifi on my phone. I don't want to ruin anything further or permanitely but i do plan to move forward. My plan is to download a sense rom (MeanRom) which im doing now but it's taking forever on 3G. Wipe everything (using TWRP 2.2) Data Dav rom and use super wipe, and try to install MeanRom. If anyone has any other suggestions Im all ears. Also im alittle confused on the Hboot kernel limitations I know I have to use Flash GUI if Im going from a sense Rom to Aosp and vise versa but do I have to use it when say Going to a nandroid backup of a sense rom while currently on a Aosp rom because I couldnt find a boot.img file in my backup file when i used the tool to extract it. I hate S-On HTC really screwed us with this. And I hate my original evo which had S-Off for dying on me on the 15th day and me having to get this replacement with 1.15 im sorry guys I love this phone but it has become a nightmare and the Evo 3D was no walk in the park either. I apprectiate any comment from anyone this is the first time in almost 8 years of hacking I've been truely worried I may not be able to fix something.
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
You also might want to try a different rom with its corresponding boot img. I'm currently running Venom rom with its boot img file and its working great. Right now, it sounds like your kernel is what is giving you problems like mine, so flashing the correct boot img should fix it.
vel7wil said:
Try this....had the same problem during one of my flashing sessions from rom to rom...this fixed it for me.
Click to expand...
Click to collapse
Thank you I'll be sure to try this out quick update, in TWRP recovery I had (force MD5 check on all zips?) checked now I don't remember checking it or if it came checked by default but as soon as I unchecked it I was able to run superwipe and flash MeanRom which both failed multiple times when it was checked on. Not sure if this was the cause of my problem but I agree I think I got a bad kernel in the CMX nightly. Either that or the Flash GUI app didnt exract the boot image properly. Either way I haven't been brave enough to try another AOSP rom man I hate having S-On my first Evo was perfect then I get stuck with this locked down replacement. One question though is that boot image for a stock/sense rom just wanna be sure.
vel7wil's advice worked for me I was having the same issue. Download the zip he recommends. Use flash image gui to flash the kernel and clear dalvik and cache. I just did a standard reboot after that and it said "android updating... apps x of xx" then everything was back to working.
SO here is the deal... I am a complete an total rooting noob but i need some help. After unlocking the bootloader with the help of Hansoons2000 tool and then flashing the phone and then pushing SuperSu to the phone i installed super su and that is where my issues began. After installing SUperSu i got stuck on the Quietly Brilliant screen on my first boot i heard this could take a while so i waited about an hour. Thats when i realized I had a problem. Heres a list of all the steps i attempted so far but to no avail..
I went into recovery and did a factory reset and cleared the cache.. Didnt work
I also relocked the phone and unlocked assuming it would wipe it that did not work.
ANy help to save my phone would be greatly appreciated. I am a first time rooter and have been stressing about my phone all day thinking i threw 700 dollars down the Drain. Any help would be greatly appreciated. And i may ask some stuid question because i am a noob. Thanks in Advance!
By the way it is an Att One X+ that i got about 3 weeks ago if that helps
which recovery you have?
you need a custom recovery for rooting
Install the TWRP Recovery if you haven't already. Do it through terminal. Then, go install a custom Rom (I suggest Viper XL+). Make sure you wipe everything your supposed to. You can do this with the installation of. Venom, it is the AROMA Installer. Flash the boot.img through terminal to. Everything should be fine and it will be rooted.
»»»Correct me if I'm wrong.
Sent from my HTC One X+
This might mean that you would need to reinstall a new rom. Now what you can do to avoid the whole fast boot terminal stuff you can try locking the bootloader and running the ruu for the at&t hox+. What that does is it wipes everything and brings the phone back to stock (stock rom, stock recovery)
After the install goes through you can re unlock the bootloader and install a custom recovery (I have an at&t hox+ and use CWM) and flash a new rom (I use desensed stock look Elegancia ROM)
I like doing the ruu method because I like having a clean slate if something went wrong.
Sent from my HTC One X+ using xda premium
Thanks
I got my phone working again and all set up using th ATT ruu so now i wondering how to make a good backup for my phone and go at rooting it again! thanks
albert1854 said:
I got my phone working again and all set up using th ATT ruu so now i wondering how to make a good backup for my phone and go at rooting it again! thanks
Click to expand...
Click to collapse
Gald you got it working again! I had to find out myself how to fix my phone when similar stuff happened to me too, now I am able to flash my phone properly with different roms. It's almost like an addiction .
now on topic, the one method i do use for backup is I use the CWM backup method, because it says your apps and your systems settings etc all in one folder and when you finish installing your new rom you can use the CWM recovery to restore the backup of your phone. CWM will restore your information and apps as well as the screens and where the icons were at in the home screens. Pretty cool I'd have to say
Now as a backup to the backup I keep my text messages call logs MMS alarms near and dear to me so I use My Backup Pro, keeps a backup online on their servers and can restore them without a prob (although I do find it annoying when it saves information when you sync facebook to the contacts. i have about 200 contacts on my phone and somehow it backs up 700 contact information?)
The tool I used to unlock my bootloader, root my phone, and install CWM (Clockworkmod Recovery) is here
pretty self explanatory and easy and has not failed me
Any questions feel free to ask
same
That the same program unused the first time that bricked my phone after installing super su so do I need to install supersu or are there any alternatives? Thanks for all your help.
Hello all,
This may be the wrong forum to post on, but I have a somewhat big problem. I have an HTC Desire 816w that came from China. I were hoping by rooting it, it would remove the restriction of Google and I could actually USE the phone. So I unlocked the bootloader, rooted the phone, flashed CWM, then flashed a ROM (KingSense DS). However, when I flashed the ROM, I was given the option to wipe the phone. I had 4 GB of bloatware so why the heck not. However this made the phone weird and it now only boots to fastboot. I tried flashing the DS ROM again but to no avail. We then tried other ROMs but they also did not work (would force close and abort installation).
So this is my question: how would I be able to fix this? I had an idea of finding the stock recovery.img and boot.img so it would at least boot into stock but I have no idea where to find them. I unfortunately couldn't back up the stock roms so I don't have that. Any solutions? Would anyone have a stock recovery.img and boot.img that they're willing to share? Is this phone still "repairable"? Please help! :S
bump
So, to start, I rooted my phone, unlocked the bootloader, and flashed TWRP for the recovery.
I did all of this so that I could prepare it for CyanogenMod. I made the mistake of not backing up my data (I seriously, seriously regret this decision now) and wiped my phone so that I could install Cyanogen, only to find out that there is no Cyanogen build available at this time for my phone model. I've looked all over google and bing and couldn't find one.
So I tried to find a stock rom to install. Screw it, I can debloat it myself if it's rooted, right? Nope. No stock roms. Sorry. Tried the RUU, and the one for my carrier says it's not the correct one, the metroPCS one stops halfway through the flashing process before it decides to tell me the same thing, and I didn't try the sprint RUU. This is driving me up the wall and all I want is a single flashable rom to work with so that I have some kind of functioning phone again.
Any help is appreciated.
Update: This thread helped me restore my phone to factory state, and I was able to re-reoot from there.
http://forum.xda-developers.com/desire-626/development/desire-626s-root-t3249254
Please lock or delete this thread.