I am pretty much trying to double check and make sure I have done everything needed before installing a custom ROM. I have a LG P509 from T-Mobile. I rooted my phone and backed everything up on my SD card using Titanium Pro. Then I installed a custom recovery (Thunderbird) following instructions from the forums. From recovery I did a Nand backup. I chose Nand+extra+android_secure. (I am unsure if that was the right option to choose, if not can I just delete the nandroid folder from my SD and repeat the process the right way?). I replaced then lost my original boot animation before backing up, does that really matter? I was reading about a custom ROM and it said something about "requiring AMON_RA recovery". I used thunderg and was wondering the difference, if I should install it and how to do so (if its the same process/where to find the files)? From everything I have done I should be able to recover to pretty much my stock phone, correct? One last question, does installing ROM and/or kernals completely erase, reformat my SD card? I have read up a ton but some things haven't been fully clear to me. I know these questions have probably been answered a million times so I thank you for all the help and insite! If I missed or forgot some things please let me know as well, thanks.
You are ready the method to back up also fine now just download rom u like and flash it.
No installing rom doesn't format ur sdcard. But some rom requires u too partition ur sdcard that's where sdcard gets formatted.
The recoverry u install is old I think u should flash new ones like amonra or cloakwork but be aware that the nandroid backup of different recovery is not compatible with each other.
Sent from my LG-P509 using XDA Premium App
rustedashes said:
I am pretty much trying to double check and make sure I have done everything needed before installing a custom ROM. I have a LG P509 from T-Mobile. I rooted my phone and backed everything up on my SD card using Titanium Pro. Then I installed a custom recovery (Thunderbird) following instructions from the forums. From recovery I did a Nand backup. I chose Nand+extra+android_secure. (I am unsure if that was the right option to choose, if not can I just delete the nandroid folder from my SD and repeat the process the right way?). I replaced then lost my original boot animation before backing up, does that really matter? I was reading about a custom ROM and it said something about "requiring AMON_RA recovery". I used thunderg and was wondering the difference, if I should install it and how to do so (if its the same process/where to find the files)? From everything I have done I should be able to recover to pretty much my stock phone, correct? One last question, does installing ROM and/or kernals completely erase, reformat my SD card? I have read up a ton but some things haven't been fully clear to me. I know these questions have probably been answered a million times so I thank you for all the help and insite! If I missed or forgot some things please let me know as well, thanks.
Click to expand...
Click to collapse
first if u want amonra orelse clockwork which can be found here http://forum.xda-developers.com/showthread.php?t=1024838 just place the file in ur sd card root and flash from recovery then reboot. DONE! u can find the latest amonra recovery here http://forum.xda-developers.com/showthread.php?t=1065197.
now when u install a new rom and wipe ur sd card then obvious that it wipes ur sd completely as some rom require to create ext partition so keep all your backup safe in pc too.
Boot animation is not an issue at all.
as for the backup nand we normally choose nand+android secure (in case no ext partition) and nand +android secure+ext (in case of ext parttion) i am not sure about the exact lines as different recovery might have differnt option type but moreorless they are same.
note:if u flash any other recovery like amonra or clockwork it is better to create a new backup using the latest recovery
I'm about to flash my first rom too. After reading alot and trying to undestand all those procedure is hard, as english is not my primary language. Recently I have install root and install costum recovery 1.2 from terminal emulator and did some nandroid backups. Also did a stock recovery backup.
My phone is stock and my provider is Telus. Do I have to unlock the phone or anything similar before flashing a new rom?
Not sure if it works on a locked phone, guess it will.
Just give it a shot, you can restore your nandbackup any time if it fails.
Hi
I would like to install mik's cm7 ROM but there are some things which I did not understand (never installed custom ROMs before, so I'm a noob):
- which recovery should I use? Amonra or Clockwork? (some explanations here contradict others, so it's not clear to me: should I copy in my SD card root both recovery.img and signed_recovery files? Because in the clockworkmod recovery topic I only found the archive containing the recovery.img file, no signed_recovery anywhere. Also in the ROM Manager app there is the option Flash ClockworkMod Recovery - can I flash a custom recovery just by pressing this option?)
- do I need to partition my SD card for this ROM? If it's necessary, how should I do it best? I mean, I was thinking at 32mb cache, 1mb ext2 or 4 and the rest fat32. And what is the real use of this partitioning?
Sorry for asking a lot of silly questions, but there is no real full tutorial for noobs here, and reading all the explanations spread around the forum is kinda confusing.
Thanks in advance
Thanks. I went ahead and flashed to the new recovery, worked perfect, and made new backups. Just waiting to get to a computer to backup to PC.
_Arjen_ said:
Not sure if it works on a locked phone, guess it will.
Just give it a shot, you can restore your nandbackup any time if it fails.
Click to expand...
Click to collapse
I'm not going to just give a try as my knowledge about the whole thing about flashing is new to me. I don't want to brick another O1 So many user here and no straight answer, wow!
I just want the right tools to proceed to flash as smooth as it can be.
Again do I have to unlocked the phone or do anything else before flashing a first custom rom? The phone is stock, beside root and custom recovery.
martymart18t said:
I'm not going to just give a try as my knowledge about the whole thing about flashing is new to me. I don't want to brick another O1 So many user here and no straight answer, wow!
I just want the right tools to proceed to flash as smooth as it can be.
Again do I have to unlocked the phone or do anything else before flashing a first custom rom? The phone is stock, beside root and custom recovery
Click to expand...
Click to collapse
This thread may give you some insite. I do not know if its what your looking for but might help.
http://forum.xda-developers.com/showthread.php?t=1075525
martymart18t said:
Again do I have to unlocked the phone or do anything else before flashing a first custom rom? The phone is stock, beside root and custom recovery.
Click to expand...
Click to collapse
From what I've read here it works only with P509 ROMs; P500 ROMs don't work.
wrong please delete it.
Hey guys, Im in urgent need of help here.
I'll give you an exact account of what i did.
saved apps via Ti. Back.; uploaded the new ICS radios and debloated, deodexed rom from my computer to my tbolt, renamed the radio from my computer; booted into 4ext, nandroid, wiped EVERYTHING, booted into bootloader; bootloader detected the new radio and I confirmed its update
Next thing that happened was that the HTC splash screen appeared as normal but disappeared, leaving a blank screen with dim backlight. Pulled battery and tried to reboot 10+ times to no avail. Same thing happens everytime. ADB doesn't recognize the phone but i CAN boot into bootloader. The problem is that everytime I boot into bootloader, the radio begins to update, leaving with the only option to reboot. Thus, I cant get into recovery.
I've spent the past couple hours trying to do my homework on this but its not looking too hot. I need this bad boy, so help is much appreciated.
Doug
You need to take the radio off the sd card, so you can boot to recovery and actually flash the rom.
Sounds like you haven't flashed a rom yet, so it has nothing to boot into.
With the radio image (PG05IMG.zip) on the root it will not go to Recovery.
So you will need to find a card reader to rename the radio file, since you wiped prior to flashing the radios.
The preferred process would have been to flash the radios, boot to your current rom, rename the radio file from within the current rom.
Then boot to recovery and flash the new rom.
I somewhat outlined this in the OP of the rooted rom thread where you should have gotten the download from.
santod040 said:
You need to take the radio off the sd card, so you can boot to recovery and actually flash the rom.
Sounds like you haven't flashed a rom yet, so it has nothing to boot into.
With the radio image (PG05IMG.zip) on the root it will not go to Recovery.
So you will need to find a card reader to rename the radio file, since you wiped prior to flashing the radios.
The preferred process would have been to flash the radios, boot to your current rom, rename the radio file from within the current rom.
Then boot to recovery and flash the new rom.
I somewhat outlined this in the OP of the rooted rom thread where you should have gotten the download from.
Click to expand...
Click to collapse
Makes sense.I dont know why I read "wipe everything" before the rest of your thread and thought that meant to do so before reflashing radios.
Got a $10 reader and was able to change the radio file and boot into recovery. Flashed the rom as usual and it looks lke everythings working.
Thanks for the help man.
Daughter handed me her phone today and said it "turned off and would not turn back on"... I could use some help figuring out what went wrong and how to fix it. I have flashed many roms, built a few from source, installed recoveries, rooted devices, etc. Though not a complete noob, I do have no formal training on this stuff and consider myself a novice compared to many here at XDA.
The phone was unlocked and rooted using Hasoon2000's HTC Rezound All In One Tool Kit about 1 month ago...
The rom that was fully functional for the past month, until today, is Liquidsmooth JB v2.9 Official vigor. It has worked exceptionally for her, until today. AT this point, if you pull the battery and then put it back in - it will boot to a white HTC screen for a few seconds and then go BSOD indefinitely. The only way to get any action after that is to pull the battery and try again... You can use the power & volume down to get into fastboot (if I pull out the external sd card) or into recovery (if I leave the external sd card in place).
Here's what the status on the fastboot screen shows:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Here's where I'm stuck at trying to get it back up and running - I do not think it is hard bricked:
1) I can boot into recovery and was able to open TWRP 2.5.0.0 and move around in it. However, it seemed to be saying there is no internal memory on the phone (cant mount or open) cache, data, system, sdcard (internal), NO ROM. I can not wipe any of the above partitions or format either...but it does see everything on the external sd card, though you can't flash anything to the internal sdcard or system, etc... Therefore, I decided to try another recovery, so...
2) Eventually I figured out how to fastboot flash a new recovery (after lots of reading here on several forums) and managed to get CWM Touch v6.0.3.6 Installed... it also does not see the system, cache, data, sdcard (internal)... but it does see my external sd card, as did TWRP. Again, no flashing to internal memory or formatting of the aforementioned partitions...
3) I have tried to fastboot flash boot.img from the aforementioned rom - fastboot flash boot boot.img - which appears to work, yet there is no change in status after rebooting or pulling the battery. Same problems exist...
4) I have tried fastboot flashing the RUU - fastboot flash ruu radio.img - appeared to do something, but still no change in status...
5) I have tried fastboot flashing the system image - fastboot flash img Liquid.zip (I changed the name of the file in an act of desperation trying various methods I read about online) - appeared to do something, but still no change in status...
6) If I boot into recovery, ADB can see the device and shows it in recovery mode. I have tried to ADB INSTALL the rom and boot.img - no luck there either (though I could be doing something wrong)...
7) If I boot into recovery, my windows 8 computer sees the external sd card of the device if I mount it as a USB MASS STORAGE device, but does not see the internal sdcard.
8) I have tried using Hasoon2000's tool to do various things and had no luck with making any more progress than using fastboot or adb.
9) I have tried to fastboot boot several different recoveries, but could not get any of them to boot up... though the process looked like it was working and rebooted - and just stuck at the white HTC screen...
I have been hacking away at this phone for about 7 hours now, reading forums, trying many things (some of which are listed above), and I've run out of ideas...
If anyone has any experience with this situation and knows of a positive solution that does not involve me flushing this thing down the toilet, I'd be really appreciative of your detailed advice. Though I have some basic experience, I can get lost quickly if you skip the details in any suggested solutions.
I appreciate any help or advice you may have to offer. I'm not thinking it's bricked - I just don't know enough to have the solution and have been reading for hours... getting a bit delirious at this point.
Thanks for you time...
It honestly sounds like some partitions are corrupt or damaged. Try using amon ra and see if it can see the internal partitions, if it can, format ext3 then ext4. Fstrim can corrupt the partition and amon ra can fix that.
If that doesn't work, you might be SOL as there is no full ruu for global OTA at the moment which may be your last resort. If you are on the recent OTA, which by your hboot, sound like it, you'd need S-off to RUU.
Sent from my Infected Rezound using xda app-developers app
Its deffinately not bricked...being able to boot to bootloader is a good thing...But as Uzephi said your best bet is to S-Off to make any further progress...that way it makes it easier to do things...fstrim especially used by LagFix app has caused this error in the past and what Uzephi said i will second to...in recovery you can try converting from ext4 to ext3 and back to ext4 and try wiping the internal within the recovery and that may fix it...if it doesnt there is a few fastboot and adb command tricks for formatting...however with s-off downgrading or upgrading the ruu is possible which may fix it also...i ran into this error once actually shortly after i modded my rezound the first time while it still only had sense...luckily i s-offed and was able to throw a few tricks at it
Guys, THANK YOU both for throwing some ideas at me... I will try as you both suggested and give an update once I'm done.
I will see if I can figure out how to s-off this thing... Then,
I will fastboot flash amonra and see if I can reformat internal with it.
If neither work, I will research adb and fastboot reformatting the internal memory.
Thanks again... This give me some more things to work on today. I will keep you posted.
Sent from my GT-I9505G using xda premium
still stuck...
So, I have spent the better part of my day working on this phone and still no luck...
From what I can tell reading various posts through the forums, I can't do the s-off thing without having the stock ruu installed... (If I'm understanding things correctly, which it is entirely possible I'm missing something obvious here...) I also run Ubuntu 12.04 on my computer in a 64bit virtualbox environment (windows 8 64 bit is my native os)- which 64 bit virtual Ubuntu seems to not be compatible with doing s-off.
I also can't get amon ra to install via fastboot flash or fastboot boot - again, entirely possible I'm missing something obvious.
I have gone over and over flashing and re-flashing twrp and cwm, trying various things to no avail... After being up late last night working on this and up early this morning, I'm officially throwing in the towel (for now). I'm really tired and a bit frustrated.
Of the dozen or so android devices that my family owns, I have rooted every one of them and installed roms, built a few fully functional roms from source, installed recoveries, etc... I have never run in to such a thing.
I still don't think it's bricked, but I'm feeling like the fix is above my head. If anyone thinks of something that I might be able to try, I will check back in a little later today. I need to get some work done around the house right now.
Thanks again for your help.
dandroid7 said:
So, I have spent the better part of my day working on this phone and still no luck...
From what I can tell reading various posts through the forums, I can't do the s-off thing without having the stock ruu installed... (If I'm understanding things correctly, which it is entirely possible I'm missing something obvious here...) I also run Ubuntu 12.04 on my computer in a 64bit virtualbox environment (windows 8 64 bit is my native os)- which 64 bit virtual Ubuntu seems to not be compatible with doing s-off.
I also can't get amon ra to install via fastboot flash or fastboot boot - again, entirely possible I'm missing something obvious.
I have gone over and over flashing and re-flashing twrp and cwm, trying various things to no avail... After being up late last night working on this and up early this morning, I'm officially throwing in the towel (for now). I'm really tired and a bit frustrated.
Of the dozen or so android devices that my family owns, I have rooted every one of them and installed roms, built a few fully functional roms from source, installed recoveries, etc... I have never run in to such a thing.
I still don't think it's bricked, but I'm feeling like the fix is above my head. If anyone thinks of something that I might be able to try, I will check back in a little later today. I need to get some work done around the house right now.
Thanks again for your help.
Click to expand...
Click to collapse
you can s-off straight from windows...i was actually able to do it on windows 7 64 bit. you can still find the latest ruu and flash it via a ph98 img file Hasoons toolkit has the appropriate files for the s-off tools...besides just flashing twrp did you use any of the format/convert/ or wipe sd card methods within them...also amon ra does have a ph98 img you can install through the bootloader itself....if worst comes to worst you can always send it to someone who can....not saying verizon but someone like me.who has done this before.
REV3NT3CH said:
you can s-off straight from windows...i was actually able to do it on windows 7 64 bit. you can still find the latest ruu and flash it via a ph98 img file Hasoons toolkit has the appropriate files for the s-off tools...besides just flashing twrp did you use any of the format/convert/ or wipe sd card methods within them...also amon ra does have a ph98 img you can install through the bootloader itself....if worst comes to worst you can always send it to someone who can....not saying verizon but someone like me.who has done this before.
Click to expand...
Click to collapse
I have an old beater pc that has windows 7 32 bit on it... I can try it from there. Am I supposed to just run s-off as juopuntubears instructions, eventhough I would be using a windows pc? Actually, I may still have a dual boot of Ubuntu 12.04 running on that machine... I'll have to take a look at it and see.
As for the latest RUU - I have downloaded "global_ota_radio_PH98IMG" that I found off the xda forums and it said it is the latest radio. I have tried to fastboot flash it and also to flash it through hasoons aiotk, neither seemed to get me functional. I also put it at the root of my sdcard, and though it appeared to be doing something when I boot into fastboot, I still have the same issues as I started with (nothing showing up on the internal memory). The version of Hasoons toolkit that I have does not appear to have any s-off features. I will have to look at older versions, I recall seeing something somewhere on xda with that feature.
As for TWRP and CWM, since they can't mount the internal partitions - they don't format or convert anything - since they fail to mount them.
I have also tried to install amon ra through the bootloader, to no avail.
I'm going to research the aiotk with s-off tools as well as check out my old pc to see if I can s-off through win7 or my dualboot Ubuntu (if it is still there)...
I do appreciate you helping point me in the right direction.
dandroid7 said:
I have an old beater pc that has windows 7 32 bit on it... I can try it from there. Am I supposed to just run s-off as juopuntubears instructions, eventhough I would be using a windows pc? Actually, I may still have a dual boot of Ubuntu 12.04 running on that machine... I'll have to take a look at it and see.
As for the latest RUU - I have downloaded "global_ota_radio_PH98IMG" that I found off the xda forums and it said it is the latest radio. I have tried to fastboot flash it and also to flash it through hasoons aiotk, neither seemed to get me functional. I also put it at the root of my sdcard, and though it appeared to be doing something when I boot into fastboot, I still have the same issues as I started with (nothing showing up on the internal memory). The version of Hasoons toolkit that I have does not appear to have any s-off features. I will have to look at older versions, I recall seeing something somewhere on xda with that feature.
As for TWRP and CWM, since they can't mount the internal partitions - they don't format or convert anything - since they fail to mount them.
I have also tried to install amon ra through the bootloader, to no avail.
I'm going to research the aiotk with s-off tools as well as check out my old pc to see if I can s-off through win7 or my dualboot Ubuntu (if it is still there)...
I do appreciate you helping point me in the right direction.
Click to expand...
Click to collapse
juopuntubears s-off method is meant for windows...for the latest ruu all you need to do is make sure it looks like PH98IMG.zip and place it to the root of your external sd card then run in bootloader and it will go through the process of install from there. I havent seen the other all in one kit in action but juopuntubears method is what i used....im pretty sure its somethjing very simple but i would load the ruu first n see where we go from there....my guess is your internal sd card was either in the middle of a reformat and was interrupted or if lagfix was used it caused the error or files were improperly deleted or the possibility of someone trying an s-off method on the s-on device....ive gotten the tampered message before and that usually means a improper hboot flash method was used
I have no clue what would have caused this issue, but my 13 year old daughter uses the phone as a WiFi only android device for Facebook, instagram, pinterest, etc... It is not even hooked up to a phone provider. She was sitting on the couch using it, her brothers were nearby using their tablets... One minute its working, the next minute it turns off...
The only thing I can think of is that I had installed goomanager when I unlocked, rooted it, and flashed a recovery and ROM. I'm wondering if she may have gotten a notice of an update for her rom or gapps through goomanager and let it start the update process without knowing what was going on... If she stopped it in the process of an update, I could see this happening somehow... I don't use goomanager much, so I'm not even sure if what I'm saying is possible?
I have a long week ahead of me with work... Not sure how much I will get to this until next weekend. Hopefully I can give it a bit of time in the evenings... But I have some extra training to do this week...
Thanks again. I will update this thread once I have taken additional steps. I do really appreciate your help.
Sent from my GT-I9505G using xda premium
dandroid7 said:
I have no clue what would have caused this issue, but my 13 year old daughter uses the phone as a WiFi only android device for Facebook, instagram, pinterest, etc... It is not even hooked up to a phone provider. She was sitting on the couch using it, her brothers were nearby using their tablets... One minute its working, the next minute it turns off...
The only thing I can think of is that I had installed goomanager when I unlocked, rooted it, and flashed a recovery and ROM. I'm wondering if she may have gotten a notice of an update for her rom or gapps through goomanager and let it start the update process without knowing what was going on... If she stopped it in the process of an update, I could see this happening somehow... I don't use goomanager much, so I'm not even sure if what I'm saying is possible?
I have a long week ahead of me with work... Not sure how much I will get to this until next weekend. Hopefully I can give it a bit of time in the evenings... But I have some extra training to do this week...
Thanks again. I will update this thread once I have taken additional steps. I do really appreciate your help.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Ya that may of done it...it is a possibility....again if all else fails someone can work on it for you....me personally id do it for you free of charge and you can trust me...i hate seeing people without and to be honest mine was completely hard bricked to no return and Neo has done me a great deed of help so im passing along the karma...but by the sounds of it yours isnt hard bricked which i know is fixable
10-4... I may take you up on your offer at some point THANK YOU for the kind offer.
I'm pretty stubborn... I may figure this out yet. S-off seems like my next conquest to overcome. Fortunately this isn't my work phone or anything, so im less stressed about having an immediate fix. My daughter will survive without it...
As well, I still don't feel like its hard bricked, so I know there is a solution out there to resurrect it from the dead. I just have to learn how to do it. That's what I love about android and the community of great people out there to learn from.
My line of work is construction management... But I'm an android ninja in training at home These android challenges cause me to learn and grow in new ways. Critical thinking, logic, problem analysis... Its all part of learning android. I enjoy the challenge and opportunity to learn from people like yourself who are willing to teach people like me, who would otherwise have no way to learn a thing like android.
Thanks again. Time to crash for the night....
Sent from my GT-I9505G using xda premium
dandroid7 said:
10-4... I may take you up on your offer at some point THANK YOU for the kind offer.
I'm pretty stubborn... I may figure this out yet. S-off seems like my next conquest to overcome. Fortunately this isn't my work phone or anything, so im less stressed about having an immediate fix. My daughter will survive without it...
As well, I still don't feel like its hard bricked, so I know there is a solution out there to resurrect it from the dead. I just have to learn how to do it. That's what I love about android and the community of great people out there to learn from.
My line of work is construction management... But I'm an android ninja in training at home These android challenges cause me to learn and grow in new ways. Critical thinking, logic, problem analysis... Its all part of learning android. I enjoy the challenge and opportunity to learn from people like yourself who are willing to teach people like me, who would otherwise have no way to learn a thing like android.
Thanks again. Time to crash for the night....
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
well your internal memory is borked but phone isnt bricked...hard bricked is when your phone wont even boot to the bootloader but reads as a certain different device in device manager...ill look into many other ways to fix this for you and i do hear you on being stubborn...im the same way when it comes to this sorta stuff and push myself to learn more....great devs learn and come from that same influence and drive to do so
Can you restore your partitions? Or can you not because you can't format them? If you can't, I suggest just flashing a stock RUU from you bootloader, being very careful though, you don't wanna get bricked. From there you can just flash your recovery and restore what you can, hopefully. Do you want a link to the RUU?
Sent from my ADR6425LVW running EclipticRezRavampedV9 (Lunar Kernel) using xda app-developers app.
Because I'm s-on right now, I don't believe I can flash an ruu, can I? I'm pretty sure I can't go backwards to an earlier ruu being s-on. Also I thought I read there is not a full ruu available of the current one I have on the phone. I could be wrong to all of the above, but I thought I read this somewhere recently.
I have been reading about s-off, but have not had time to do it. I also am unclear if it is even possible to do s-off in the current state the phone is in.
I can't format because it won't mount any internal partitions. I dont know how to restore a partition... But if the internal memory won't mount, I'm not sure if a restore would work.
I'm willing to try stuff, just not today... Had a reeeaaally long day. If you want to send me a link for an ruu or have any other ideas, I am interested in getting past this issue. But it may not be until this weekend that I have time to get back to it.
Thanks.
Sent from my GT-I9505G using xda premium
dandroid7 said:
Because I'm s-on right now, I don't believe I can flash an ruu, can I? I'm pretty sure I can't go backwards to an earlier ruu being s-on. Also I thought I read there is not a full ruu available of the current one I have on the phone. I could be wrong to all of the above, but I thought I read this somewhere recently.
I have been reading about s-off, but have not had time to do it. I also am unclear if it is even possible to do s-off in the current state the phone is in.
I can't format because it won't mount any internal partitions. I dont know how to restore a partition... But if the internal memory won't mount, I'm not sure if a restore would work.
I'm willing to try stuff, just not today... Had a reeeaaally long day. If you want to send me a link for an ruu or have any other ideas, I am interested in getting past this issue. But it may not be until this weekend that I have time to get back to it.
Thanks.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
if your on hboot 2.28 that is the most recent up to date leaked radios...however the most up to date full ruu comes with 2.27...if you are s-off its kind of hard...a user posted in the threads earlier that he completely removed his external card and his windows was able to detect the 2 internal partitions...and he formatted the 10.5 gb fartition and worked flawless...if all else fails...how well do you know about using linux and or a linux based rescue disk for partitions
Holy cow - its alive!!!
THANKS to everyone who has been helping point me in the right direction.
I'm now close to functional again... bootlooping at the splash screen for a rom is much better than no internal partitions on the device...
I relocked the bootloader using hasoon2000s all in one kit...
After doing much research, I was finally able to flash a PH98IMG file that someone had posted here on the xda forum that was here (said it works for S-on):
http://forum.xda-developers.com/showthread.php?t=2250494
http://d-h.st/BIj - had to rename the file to PH98IMG and flash from sd card in bootloader/hboot.
Once I did that, I unlocked the phone again using hasoon2000s all in one kit, then installed amon ra recovery.
I flashed a new rom via amon ra recovery.
I then fastboot flash boot boot.img that I pulled from the new rom
I now see paritions on the internal memory when I'm in recovery, and the splash screen of the new rom is bootlooping... I'm soooo close to being functional again.
I'll let you know when I get passed the bootloop...
dandroid7 said:
THANKS to everyone who has been helping point me in the right direction.
I'm now close to functional again... bootlooping at the splash screen for a rom is much better than no internal partitions on the device...
I relocked the bootloader using hasoon2000s all in one kit...
After doing much research, I was finally able to flash a PH98IMG file that someone had posted here on the xda forum that was here (said it works for S-on):
http://forum.xda-developers.com/showthread.php?t=2250494
http://d-h.st/BIj - had to rename the file to PH98IMG and flash from sd card in bootloader/hboot.
Once I did that, I unlocked the phone again using hasoon2000s all in one kit, then installed amon ra recovery.
I flashed a new rom via amon ra recovery.
I then fastboot flash boot boot.img that I pulled from the new rom
I now see paritions on the internal memory when I'm in recovery, and the splash screen of the new rom is bootlooping... I'm soooo close to being functional again.
I'll let you know when I get passed the bootloop...
Click to expand...
Click to collapse
Use CWM or TWRP for flashing. Amon ra is known to have flashing/wiping issues. And did you clean wipe? Even though you have RUU you still need to wipe.
Sent from my Infected Rezound using xda app-developers app
Thanks for the info... I never used amon ra before, I read about it being buggy.
I actually wiped everything, repartitioned it, then flashed ROM with amon ra, then fastboot flashed boot image.
I have to get up a 4am... So I'm calling it quits for tonight. I have another long day tomorrow... I'm feeling like I'm in the home stretch now. Tomorrow I will switch back to twrp 2.6 or cwm touch 6 and see what happens. I will do a full wipe, flash ROM, then fastboot flash the boot image.
Fingers crossed...
Thanks again. I'm always learning here on xda and other android forums. I really appreciate your kindness in pointing me in the right direction and giving me ideas of things to try. I did a ton of reading to get this one figured out as far as I have, though I'm still not done yet.
I will touch base again once I do the things above.
Sent from my GT-I9505G using xda premium
dandroid7 said:
Thanks for the info... I never used amon ra before, I red about it being buggy.
I actually wiped everything, repartitioned it, then flashed ROM with am on ra, the fastboot flashed boot image.
I have to get up a 4am... So I'm calling it quits for tonight. I have another long day tomorrow... I'm feeling like I'm in the home stretch now. Tomorrow I will switch back to twrp 2.6 or cwm touch 6 and see what happens. I will do a full wipe, flash ROM, then fastboot flash the boot image.
Fingers crossed...
Thanks again. I'm always learning here on xda and other android forums. I really appreciate your kindness in pointing me in the right direction and giving me ideas of things to try. I did a ton of reading to get this one figured out as far as I have, though I'm still not done yet.
I will touch base again once I do the things above.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Hey i may have found a fix...another user had the same issue and fixed it by using TWRP and wiping emmc first. Once he did that he wiped the internal sd card. Should then work... Format afterwards just to be safe.
K good to know. Have a great night... I will give it a rip tomorrow... I'm pretty stoked to have gotten this far today.
Sent from my GT-I9505G using xda premium
Hey all, have a few questions, I hope you can answer in laymans terms.
First of all, my att htc one 64gb is now unlocked/superuser/twrp recovery/rooted/and s-off.
I'm running the stock software that came with the phone, and to be honest, I've used aosp on my droid incredible, but for now I kind of dig the stock sense feel. So I wanted to flash a upgraded stock sense rom. I saw this one
ROM][9/11/13] AT&T Leaked 3.10.502.2 - Android 4.3 / Sense 5
I read through that thread and learned a lot and also confused the hell out of myself. With my droid incredible, I'd download a new rom to my pc, transfer it from pc to sd card and then reboot to recovery, wipe data/system/cache/dalvik cache/ install rom/ reboot. Done!!
I'm guessing the principle is the same on the htc one, however, this doesn't have an external sd card, so if I transfer the new rom onto sd card, which to me is really internal memory on this phone, then reboot to recovery, wipe, well wouldn't I lose everything on that sd card (internal memory), including my twrp folder which has nandroid backup?
That's my first question.
My second question is that same rom I highlighted above has an rom and ruu download. Now if I have read correctly, the ruu has the rom plus firmware updates, like hboot, radio, etc. You can't flash this via booting into recovery. I believe it said you flash into fastboot, which I'm a little green on exactly that process.
I also see, that if you flash an ruu, you lose root, custom recovery, and pretty much everything except s-off, so I guess you have to redo those things again.
Like everyone else, just don't want to fry the thing, so figured I'd better ask questions first
Just don't wipe the sd card and your backups and stuff won't be touched.
Sent from my HTC One using Tapatalk 4