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
Related
Hey guys,
Was having too many issues with GNex so I traded in for a rezound but hate all the bloat on it. Decided I'd finally stick my neck out there and try my noob hand at rooting and customizing it.
So, got my rezound unlocked and rooted and before i try anything, how do I ensure I don't brick the phone?
Searched around for a real dumbed down guide to backup and recovery but I'm at a kindergarten level with this stuff. For example, it took me about 4 hours to figure out how to unlock and root the phone and HTC gives you directions on unlocking.
Have titanium backup, and rom manager. I read there's 2 ways to create a recovery file - cwm and amon-ra, read about nandroid backup but don't know what these things mean or how they function.
Can anyone give me a quick tutorial in backing up the phone in case I eff it up?
Any help would be much appreciated, I apologize if this is too basic a question.
Thanks
No apologies! You have to start somewhere so it's all good. I would start with these two very helpful threads:
http://forum.xda-developers.com/showthread.php?t=1418653
http://forum.xda-developers.com/showthread.php?t=1418659
I would recommend using the Amon_Ra recovery from THIS post.
Since you are coming from a Gnex...is it safe to assume you know how to flash a custom recovery with the boot.img?
It's not safe to say I know how to do anything yet haha. I liked the non cluttered feel of the gnex so I didn't mess with it and I never did anything with my og Droid. Never flashed anything so I'm about as noob as they come. I unlocked and rooted this phone and that's my experience to this point. Again all help is good
Sent from my ADR6425LVW using XDA App
Thanks for the links btw. Slowly figuring this stuff out. Got amon ra recovery now... What does that do exactly? Just trying to ensure I can get back to where.I am in case I mess up my phone. Should I do a nandroid backup? Not sure what that means either but I see some threads about how to do it.
Sent from my ADR6425LVW using XDA App
biond said:
Thanks for the links btw. Slowly figuring this stuff out. Got amon ra recovery now... What does that do exactly? Just trying to ensure I can get back to where.I am in case I mess up my phone. Should I do a nandroid backup? Not sure what that means either but I see some threads about how to do it.
Sent from my ADR6425LVW using XDA App
Click to expand...
Click to collapse
A nandroid is an image of your phone in its current state. So yes, you should do a nandroid back up now before you flash a ROM so if something goes wrong you can restore it back to how it is now.
Then if you're going to flash a kernel after you flash a ROM you should probably make one before flashing the kernel as well in case something goes wrong.
Then when you have the phone the way you like it with a custom ROM/kernel you can make a nandroid at that point as well so you have that handy in case of anything going wrong somewhere down the line or if you just want to get back to that setup after trying out a different ROM. Then you just restore that instead of having to flash the other ROM/kernel again. If you want you can make nandroids of all your custom ROM configurations so you can switch them whenever you want. Of course you should keep an eye out in the threads of the ROMs in case of updates, and sometimes you need to wipe and flash the new version if there is an update.
Here's a few links with some good info:
Beginner's Guide to Rooting Android Devices
Quick INTRO TO ROOTING for those new to rooting
[HOW-TO] ADB for Dummies(How-To Learner's Guide)
If you've never flashed anything before and are planning on customizing this thing; welcome to the family of rezound.
welcome! The ReZound in my opinion is a great phone.
Alright, got myself some good information from you all. Nandroid backup done and saved on my PC so now I'm good to ROM? Eager to rid myself of the enormous amount of bloat the rezound comes with.
One more thing to add for you to know about your original backup, or subsequent ones- that wasn't brought up here.. (smarter folks shoot this down if I'm wrong).. Someone stated above that once you have your nandroid you're always ready to go back to that original backup with a simple flash. This is not the case if he's gone to another rom that uses a different kernel right? It seems some devs have found ways to work the kernel install into the rom install/flash, and others haven't.. Until there's a standard- there's never a guarantee that restoring that original nandroid will bring you back to your original kernel correct? You may have to d/l and install the boot.img after the restore.
That's part of my issue now. I keep ready about flashing roms and kernels but they all assume some level of proficiency when it's something I've never tried. I'm thinking of starting with clean Rom 1.5 but I want to keep some apps like nfl. I just can't find the bare bones explanation of what to do with the file and how to get my data back after i flash that Rom (a process I am foreign to). I download the zip to my PC.... Then what?
Sent from my ADR6425LVW using XDA App
You may also want to get the stock rooted kernel, and keep it with the nandroid. If, and when you want to restore, place your nandroid, and kernel on your sd card. Boot into Amon ra, and restore, then flash the kernel in fastboot. Not the best description, but I hope that helps....
Sent from my ADR6425LVW using Tapatalk
I'm running ineffabalis with their stock rooted kernel right now mainly because I want to wait until the kernel update process is a little more streamlined and the kernels themselves are a little more ironed out. That said, the complete newb sticky guide over in the dev section has a process that seems easy enough.. Basically involves a simple fastboot command from dos. It's written for ziggys but should translate to other kernels as well.
Sent from my ADR6425LVW using Tapatalk
Looking for help/suggestions.
I have 2 aria that developed random reboot for no apparent reason...
My work aria was rooted and s-off running cm7.1 for about a month with no issues, I've flashed kang cm7.2 and all seemed ok, but the next morning the phone was dead (it was at 50% before going to sleep). charged it in the morning (the battery was 0%), came to work and while it was on my desk the phone rebooted and continued to do that through out the day. At home, i did factory reset, did not help. I've put it back to s-on and put back the stack ATT 2.2, same results, continues to re-boot at random intervals. Thinking it was hardware, got my job to get me a different phone.
3 weeks later, my wife's aria (rooted but still s-on) running cm7.1 started to run extremely slow and battery would drain in about 5 hours. I've done factory reset, clear everything and it still doing random re-boots just like my aria.
With one aria, I thought that it was a hardware issue, but now 2 arias, looks like os/software. Resetting/ re flashing does not help.
Any suggestions would be highly appreciated.
Are the devices overclocked?
Theonew said:
Are the devices overclocked?
Click to expand...
Click to collapse
yes, they both were overclocked, do not remember at what level, i think whatever the cm7.1 default was.... I did put them back to 600, which did not help.
Thank you
was such a problem! htc aria repaired and the problem was in nand module! I advise to contact the warranty service center!
dimon2242 said:
was such a problem! htc aria repaired and the problem was in nand module! I advise to contact the warranty service center!
Click to expand...
Click to collapse
Thank you, I gave mine back at work, my wife's is out of warranty. Interesting that both of them developed the same problem (i haven't touched wife's in months). Do you know what may cause such a problem?
Did you try doing "format system" before doing a clean install? Also make sure you are using a recent version of Clockworkmod (5.x).
strykme said:
Thank you, I gave mine back at work, my wife's is out of warranty. Interesting that both of them developed the same problem (i haven't touched wife's in months). Do you know what may cause such a problem?
Click to expand...
Click to collapse
You should touch your wife('s) more often
Sorry, couldn't resist
Running CM-7.2.0-RC for about a month and the Airia just started random rebooting this morning. Nothing changed except some software updates -- such as Google Maps.
I restored to a NAndroid backup from 3 weeks ago and it still random reboots. Suspecting a hardware problem, I even put the SD card in another Airia and restored the older NAndroid backup, but still having the reboot problem.
Any thoughts?
yar2 said:
Running CM-7.2.0-RC for about a month and the Airia just started random rebooting this morning. Nothing changed except some software updates -- such as Google Maps.
I restored to a NAndroid backup from 3 weeks ago and it still random reboots. Suspecting a hardware problem, I even put the SD card in another Airia and restored the older NAndroid backup, but still having the reboot problem.
Any thoughts?
Click to expand...
Click to collapse
yea i do
malware
wipe the phone , then check it out
I have performed factory resets and all other formats and clear functions in Clockworkmod. Should I refomate the SD card too?
Sent from my Liberty using XDA
yar2 said:
I have performed factory resets and all other formats and clear functions in Clockworkmod. Should I refomate the SD card too?
Sent from my Liberty using XDA
Click to expand...
Click to collapse
Can, because possible errors on the SD card
I still have not solved the random reboot issues. I have two Arias with the exact same problem. I think I somehow contaminated the 2nd phone by swaping SD cards and loading a Nandroid backup from the 1st phone. Both phones are rooted.
I have tried loading 4 roms -- Liberated, CM7.1 stable, CM7.2 RC and Menjeni's version of CM9 and have the exact same random reboot problem Seems like the phones works for anywhere from 5 minutes to over an hour and then reboot.
When I load the different ROMs I wipe everything -- the factory data reset, all the caches and re-formats that CWM offers. I also reformatted the SD card and reloaded CWM via Rom Manger in an effort to completely clean the phone. I also ran two a virus/malware scans on the phone and SD card -- which found no errors.
Is there something else I can do to further clean the phones? Since the same problem is with both phones, I seriously doubt its a hardware problem.
Anyone interested in purchasing 2 somewhat functioning Arias?
yar2 said:
I still have not solved the random reboot issues.
Click to expand...
Click to collapse
yar2, what HBOOT version do you have on the two devices?
HBOOT 6.02.1002
Thanks for trying to help me with this!
yar2 said:
HBOOT 6.02.1002
Thanks for trying to help me with this!
Click to expand...
Click to collapse
OK. I'm assuming you have an AT&T Aria. If not let me know.
Here's what I'd suggest you do. I'm basically trying the most extreme steps to correct the issue so we can verify if the issue is something that can be corrected or not.
1) Reformat your SD card(s) with SD Formatter 3.1. This tool sometimes fixes hard to detect problems that aren't corrected when formatting with other methods. (Default settings are fine.)
2) Run the AT&T 2.2.2 RUU to revert your phone to almost 100% stock. I say almost because the RUU will NOT change your HBOOT, which means even after doing this process, you will still have S-OFF.
3) Try using the phone with the stock unmodified ROM to see if you experience the random reboots you described. If you do, the rest of the steps are not necessary and it's probably a hardware issue.
4) Install CWM by putting your phone into FASTBOOT mode, then using the Android Flasher utility to install the latest version of Clockworkmod. Use this version: http://www.mediafire.com/?lg6b63aqpi1cvbg (source). If you know how to do this from command line with the fastboot command line tool, that is fine too.
5) Boot into CWM. Do factory reset/wipe data and format system partition. Then install the ROM of your choice. I'd suggest something like a recent version of CM7 since it is very stable. If using CM7, install 20110828 gapps immediately after flashing CM7. Reboot and see how it goes.
Even if you already downloaded any of the above files, delete them and download them again this time around (or check the md5 sums if you know how). It's possible the files were corrupted when you downloaded them before and that is why you keep having problems.
Also, as an aside: Are you using third-party batteries with your devices?
Aria random reboot
Thanks drumist for all you advice! When I did my last attempt at a clean install, I used a spare SD card that had never been in the phone.
Both phones are AT&T Arias with the original batteries. I liked the Aria size so much that I upgraded my wife's expired Iphone contract when AT&T was providing a free Aria upgrade just to have a spare in case I damaged one by rooting. Now I have managed to mess up both phones!
I was thinking my next step would be to go back to a stock state, as you recommend. I was thinking of going even further and un-rooting and S-On. Do you think the problem could be in the Hboot partition? And wouldn't going back to S-on replace the Hboot?
I still think I somehow contaminated the 2nd phone by restoring a Nandriod backup from the first phone. The 2nd phone was working find until I did the restore.
Regardless, I will try what you suggest and let you know the results.
yar2 said:
I was thinking my next step would be to go back to a stock state, as you recommend. I was thinking of going even further and un-rooting and S-On. Do you think the problem could be in the Hboot partition? And wouldn't going back to S-on replace the Hboot?
Click to expand...
Click to collapse
Reverting the HBOOT to stock (and yes, returning to S-ON) has some risk -- i.e., if you make a mistake during the process, you can permanently brick the device, so I wouldn't recommend that except as a last resort. The RUU will reflash every other partition on your phone back to stock besides the HBOOT and is safe to do, so stick with that.
I still think I somehow contaminated the 2nd phone by restoring a Nandriod backup from the first phone. The 2nd phone was working find until I did the restore.
Click to expand...
Click to collapse
Yeah, it's possible. If that is the case, though, the HBOOT wouldn't be the problem (because Nandroid backups do not touch the HBOOT). The RUU will reflash every partition that Nandroid touches.
If you already tried using a different SD card, then I wouldn't worry about using that SD Formatter tool.
Can't find a copy of the AT&T 2.2.2 RUU. They took it off the HTC website. The instructions there are for an OTA update, which I can't do since I'm not running the stock rom.
---------- Post added at 02:51 PM ---------- Previous post was at 02:12 PM ----------
Never mind. I found a copy of the RUU on my laptop.
I have installed the hboot drivers and the phone shows up as a device on my computer, but the RUU says it can't find my phone. I am running Windows 7, if that makes any difference.
Got the RUU to load from an XP machine. Bad news is that the phone still randomly reboots.
I guess the only other step is to un-root and S-On. What have I got to lose. Can't use the phones as they are now.
Got a good way to do this?
So I'm pretty sure I'm going to flash that new rom once I'm home but i haven't done one of those nandroid back ups since the infuse was new...can someone point me in the right direction, i forgot how to do it. Do i really need to do it?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
u can just boot recovery and then go to backup n restore and select backup no?
Sent from my SAMSUNG-SGH-I717 using XDA
You need to flash clockwork recovery then just go to the backups menu and do a backup. If you're going to install the Solaris rom you need clockwork anyway.
And DONT SKIP THE BACKUP!! I cannot stress this enough!
sent from my iPhone killers killer, Samsung Galaxy Note.
Backup up, backup always
Sent from the only smartphone designed by Chuck Norris
macked said:
You need to flash clockwork recovery then just go to the backups menu and do a backup. If you're going to install the Solaris rom you need clockwork anyway.
And DONT SKIP THE BACKUP!! I cannot stress this enough!
sent from my iPhone killers killer, Samsung Galaxy Note.
Click to expand...
Click to collapse
That's what i plan on doing...thanks.
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Always always backup. I am a hypocrite (and many probably are) when I say this as I have skipped the back up. But I have learned the hardway. When I got into flashing with my G1 I soft bricked for about 3 days. This scared the bajesus out of me as there was no wide spread support, this was the first commercialy available android phone so any sites that did exsist were in their infantile stages at the time. I dodged the bullet and found someone who was able to get me fixed, but was a real PITA. The odds of this heppening are far less now a days so long as you read the instructions and follow them, but it's still not worth the risk. Doing a CWM backup takes a few minutes so there is no reason not to do one. Something else I learned the hard way the most people overlook, TEST THE BACKUP. Lucky for me I never got in an instance where my failed backup caused me anything but a little more work. I can think of atleast a half dozen times I created a backup that would fail when I tried to restore to it. If restoring the backup failes, you will be able to just boot back up into your ROM. However if your stuck in a bootloop from a failed ROM flash, and now your backup wont flash, you're in a little hot water. Likely you'll just have to pop your SD, xfer a couple images onto it, then back to phone and start flashing till you get one to boot up. Learn from those who have already been stupid, laughing at us is better then people laughing at you down the road.
Chief Geek said:
Always always backup. I am a hypocrite (and many probably are) when I say this as I have skipped the back up. But I have learned the hardway. When I got into flashing with my G1 I soft bricked for about 3 days. This scared the bajesus out of me as there was no wide spread support, this was the first commercialy available android phone so any sites that did exsist were in their infantile stages at the time. I dodged the bullet and found someone who was able to get me fixed, but was a real PITA. The odds of this heppening are far less now a days so long as you read the instructions and follow them, but it's still not worth the risk. Doing a CWM backup takes a few minutes so there is no reason not to do one. Something else I learned the hard way the most people overlook, TEST THE BACKUP. Lucky for me I never got in an instance where my failed backup caused me anything but a little more work. I can think of atleast a half dozen times I created a backup that would fail when I tried to restore to it. If restoring the backup failes, you will be able to just boot back up into your ROM. However if your stuck in a bootloop from a failed ROM flash, and now your backup wont flash, you're in a little hot water. Likely you'll just have to pop your SD, xfer a couple images onto it, then back to phone and start flashing till you get one to boot up. Learn from those who have already been stupid, laughing at us is better then people laughing at you down the road.
Click to expand...
Click to collapse
Good points but the first time i bricked my phone (flashed a gb rom over my froyo infuse) i just used the ultimate unbrick tool and bam back to stock, yea i have to start over from stock but at least my phone is all set. Is there a tool available for the note that unbricks it like the infuse has or is the back up we make our only option to unbrick?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Do. It. (just do it)
Do it. Back it up!
Sure it adds a few minutes to your flashing routine, but just start it and go make a coffee.
I cannot begin to tell you how many times I was glad to have something to restore to after playing around with a new/updated rom package.
nash2000 said:
Good points but the first time i bricked my phone (flashed a gb rom over my froyo infuse) i just used the ultimate unbrick tool and bam back to stock, yea i have to start over from stock but at least my phone is all set. Is there a tool available for the note that unbricks it like the infuse has or is the back up we make our only option to unbrick?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Nope, nothing that I know of, but the ROM scene is in its early stages. Theres not much need for tools such as this when there is little action. Something like this may hit the scene once our Note starts getting lots of custom ROM releases. I have only heard of that tool for two phones though. It's pretty hard to truely brick a phone nowadays, if you download the right packages and read the instructions a couple times and then (heres a commonly skipped one) FOLLOW the flashing directions, you won't encounter too many issues that can't be easily overcome by restoring image, delete rom and redownload, and try again. Alot of ICS ROMS actually require a double flash, if you don't read the instructions and don't catch that, you'll be freaking on the boot loop.
nash2000 said:
So I'm pretty sure I'm going to flash that new rom once I'm home but i haven't done one of those nandroid back ups since the infuse was new...can someone point me in the right direction, i forgot how to do it. Do i really need to do it?
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
Should always backup before flashing something, just as a precaution.
Although I don't worry too much, it's fun re-customizing anyways. Going into market online and reinstalling apps is quick. Contacts and calender restores from google, at least for me anyways.
If you're thinking of flashing a new radio or going into something that makes major changes to the way your device is configured. I would highly recommend you have a nand of your last working setup. In case you need to revert.
clockcycle said:
Should always backup before flashing something, just as a precaution.
Although I don't worry too much, it's fun re-customizing anyways. Going into market online and reinstalling apps is quick. Contacts and calender restores from google, at least for me anyways.
If you're thinking of flashing a new radio or going into something that makes major changes to the way your device is configured. I would highly recommend you have a nand of your last working setup. In case you need to revert.
Click to expand...
Click to collapse
I think we're more concerned with if the image doesn't flash or he gets stuck in a boot loop. If your able to get to CWM, you can recover. But having something to flash from immediately on hand is a very nice thing to have. As for recustomizing though, i'm with you all the way there. I look at as a good way to cut the fat. I use Titanium backup, but don't do full automated restores, but rather select the desired apps and ignore the rest untill I find myself needing it.
Let me start off by saying Im far from new to the rooting and roming game. Been through several phones. Never run into this issue.
Note 2 - i605
Team Win Recovery - Up to date
Clockwork Recovery - Up to date
MJ9 Radio from Zif
I am able to install CleanROM and Sophisticated. But when I attempt to install CM11, MeanBean, or Gummy the install fails. It attempts to unzip but always ends with failed. This occurs on both recoveries. I have even tried an alternative recovery. Nothing seems to get it done. Please someone help. Like to note I checked my external SD card for errors. It passed.
Sent from my SCH-I605 using XDA Premium 4 mobile app
General consensus seems to be that philz recovery is currently the recovery of choice for 4.3, id say give that a try
Note2.5
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Jiggabitties said:
This same thing happened to me. I couldn't even install backups I had. I finally gave up, ODIN'd back to stock and reran casual, everything has been fine since. Even re-installing the same exact recovery.
Click to expand...
Click to collapse
Im going to give that a shot. I think it may actually be the thing that sorts this all out. Not hat Phillz is not a good option. But that's the other recovery I already tried. Thinking that maybe the Casual I did was not smooth. As it did hang a couple times and was not as smooth as I would have liked. I am going to reply back when I do it to let everyone know how it turned out. Just in case someone else has the same issues.
:good:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Crotty.Josh said:
So I odin stocked the phone. Perform casual. Much smoother this time. But still no dice. Still able to install only some roms.
Installable:
Sophisticated
CleanROM
Unable to Install:
CM 11
MeanBean ICE
MeanBean Reborn
Gummy
:crying:
Click to expand...
Click to collapse
Hmmmm. Somewhere there's a step that's failing you (obviously). Maybe break down your process, from download to flash, and try to pinpoint where it's going wrong. In my experience the things that have caused an install to fail have been either an incompatible or outdated recovery, bad download (check the MD5), or borked system partition (which is when I Odin'd and re-casualed).
Had issues with CM11 until I ODIN'd back to stock LJB, unlocked bootloader/rooted, updated to latest TWRP 2.6.3.1 via ODIN, wiped all partitions included cache, data, dalvik, system, internal sdcard, external sdcard then adb push CM11 plus gapps and installed. Just make sure you can adb push before wiping everything along with checking file CRC and temporarily disable antivirus.
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Crotty.Josh said:
So I the issue ended up being one of an interesting nature but not normal. When I download thw rom of choice to my phone I move it to my SD card. Making sure its out of the distruction path. As is normal practice. I am using Rom Toolbox root browser to make the move. Turns out that although it gave the impression it was moving the files, it did not always do so. So each time I copy a file from place to another I have to check that it was done in full and without flaws. Quite an interesting problem. As a move of that sort should not break files.
Click to expand...
Click to collapse
It's always something small it seems. Good practice is to download the ROM, get it to it's final destination then check the MD5. I always wait until I've moved it to the SD to check the MD5 just in case there was a bad transfer.
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