file partitions - Sprint HTC One (M7)

i've got a question: i flashed a 4.2.2 rom then did the deal with the sdcard to straighten out that. used that rom a couple days, but 4g was acting up, so i went back to a 4.1.2 rom, after backing up the 4.2 rom, now my question is if i restore the 4.2 rom will my file partitions be messed up again.it's not a big deal i was just wondering,
WELL, iguess i'll find out when i do it, won't i.

Related

[Q] Recovering from rom ics leak

Current phone information should be attached. Short form is, I'm using the Gummi 1.2.0 rom, put onto my phone after using safestrap (and following the instructions to make a backup before doing so). Safesystem is enabled.
Two backups: located on my external SD card
nonsafe-2012-05-26.07.52.54/
safe-2012-05-27.08.06.28/
Safestrap recovery v1.09 (afraid to update to 2.0 without breaking more stuff)
What I'm looking to do is return my phone to working stock, which I believe was Gingerbread 2.3.6. That said, every time I've touched this thing trying to go back, I've black screened it. I don't live in an area with 4g (screw the mountains, and their 1x service), so any attempts to connect to the 4g network for any part of the process will require me driving into Pennsylvania, 30 minutes away. I've heard before that you can't return from the ICS leak to the Stock for the Droid 4, for various reasons (but i believe the important one was it was a later firmware and it isn't a process designed to go backwards)
I'd like to know if thats still the case currently, or if something has changed. I'm getting shaky wifi/data/cell reception up here, and its flawless back on stock. Hell, I've got an old razor as an emergency phone that's flawless up here. Next time I'll do more research for this stuff I was a proud OG droid owner, and ran cyanogenmod on it before the vid card fried one evening. Thought the droid 4 would be a good deal, but I've had nothing but trouble with the roms on it.
All that said, I can simply smash and return this droid if its the only way to get a stock one back, but I don't like destroying useful and good technology when I can help it. Besides, I like fixing the problems I create.
Thanks for the help XDA, either way.
-- TheChaoticDoctor
Did you flash the leak ICS from Motorola or did you use Safestrap and flash Gummy ICS?
If you flashed the leaked ICS, there is no going back. You will need to find get the files to flash the partial .219 system back so you can run the .206 leak update again.
If you just used safestrap to flash Gummy 1.2.0 then you can use the .219 flash files to completely re-do your phone.
Currently there are no ROMs to flash if you are on the leak, Hashcode just released his Safestrap 2.0 to do so but still nothing to flash. All the current ICS ROM builds are for the stock phone running the Gingerbread Kernel.
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
TheChaoticDoctor said:
Sorry about the delay, was off camping. I rooted the phone first on gingerbread, then eventually installed safestrap and flashed the gummi rom. Can you (or someone else) walk me through the steps for flashing the .219 files and then flashing the .206 files?
Click to expand...
Click to collapse
You should probably go up to .208, that's the latest leak. Make sure to use rootkeeper, and follow all the instructions. So far I haven't lost root, but be aware I'm stuck on .206 because I don't want to lose root....
Look here for more info:
http://forum.xda-developers.com/showthread.php?p=26311439
Sent from my XT894 running ICS
First of all, it sounds to me like you've just flashed a ROM, not flashed the leak. If that is the case, you can just toggle the safe mode in safestrap to get back to stock. Safestrap lets you toggle between stock and the ROM. It is pretty awesome because you can play with the ROM and then go back to stock whenever you need to.
If you HAVE flashed the Motorola leak (as opposed to just a ROM) you are SOL.
If you haven't flashed the Motorola leak and just want to get back to factory conditions, you'll have to flash via RSDLite. That info you should be able to find here:
http://forum.xda-developers.com/showthread.php?t=1622256
Honestly I WOULD NOT flash the leak at this time. IMHO, it doesn't really offer enough to risk getting off the upgrade path forever, and losing the ability to flash back via RSDLite.

[Q] Possibility for completely removing the stock rom?

Hey everyone,
I'm new to this forum as far as registering goes, and i just have one simple question: Is it possible to completely remove the stock ROM on the droid bionic?
The reason i am asking is because i followed the rooting/flashing ROM guide
(http://forum.xda-developers.com/archive/index.php/t-1455888.html)
to a word, and after a couple of days of using my new ROM (eclipse 2.2 w/ fury x theme) i have been having problems.
ie: tried backing up stock rom with safestrap, says "error backing up android.secure.img/emmc skipping backup of application". then it says "error backing up android.secure.img/osh skipping backup of application"
Now my phone is back on the stock ROM, but even with ROM manager i cant even back up my stock ROM or flash a new ROM, i have also tried using the older versions of rom manager with no luck.The phone just reboots every time i do.
BTW= I am rooted (super user confirmed), and i have update ver 902.
I have everything backed up on my personal computer in case something goes horribly wrong
So i just wanted to know if i could skip this headache, and remove the stock rom completely and then flash my new "stock rom".
Does anyone know how to do something like this?
It almost sounds like you've got a bad flash in your phone that prevents the recovery utilities from being able to correctly identify all the partitioning at the block level like it should.
If I were in your situation, I'd definitely do a full FXZ flash back to 5.9.902 so that everything is rewritten, then you can try wiping and re-installing another ROM.
Awesome, i will give it a shot.thanks

weirdest problem, and i have NO clue how to fix. please help.

Hello,
I decided to upgrade from CM9 to Lanlight V6.5DD:
I installed V6.5DD using the exact method that was written on the OP. I was coming from CM9, it booted up correctly and everything works great except three things:
1) i have no lock screen (lock screen is checked(slide))
2) I don't get any notifications, whatsoever(i can pull it down, but i hear an email or sms come in and nothing appears)
3) when i hold the home button, the recent apps don't show.
I formatted everything again and re flashed, same exact problem.
What should i do? everything worked well on cm9
I installed different JB roms and same problem.
I decided to go back to CM9, and guess what? the same problem stayed (i formatted everything, and clered nstool, inti.d, clean old kernel files, everything).
It looks i have to Odin back to stock. Can anyone please help me, so i don't have to Odin. OR at lease so i can try JB for once.
please help
sincerely,
Thatguy
Yeah try flashing a gb stock rom e.g. uckk4 from the master thread. Then flash the rom you want.
you should have made back up of your cm9 to Restore back to. I have a cm10, lanight, and slim bean 2.7 backups. that i can go back to.
I just Flashed Slim Bean 2.8 last night. Running Good :good:
Yea, i'm planning on going back to Odin and flashing to the latest official version (newer GB boot-loader would do the trick?I don't know anymore)
I had a nandroid backup and i restored yet the same problem is there.

[Q] Would this work?

Recently, the ROM "H-Delicious" for 4.1.1 was released and there was an option to restore it to your stock ROM in SS3 because it saves space. I was wondering, once a stable release of Batakang ROM came out, could I flash it to a ROM slot, back up that ROM slot, wipe my stock ROM slot and then restore using the backup of the slot with batakang ROM on my stock slot? I was thinking about this and it seems to make sense. I'm sorry, I know I'm being lazy by asking other member of the community to test and help out on this suggestion, but im still quite new and could use more experienced input.

[Q] Stuck with older custom rom

So, around April-ish last year I rooted my At&t galaxy note 3 and installed safestrap, then alliance rom. I wanted to find a ROM I liked, then just sort of stick with that so I didn't have to monitor development updates about my phone and all that. The only problem with the ROM was that it had a memory leak so bad that I had to reboot about 3 times a day or else the memory would get all used up and the phone would freeze. For some reason, I didn't think it would bother me that much- the phone boots quickly and I was so fed up by then I didn't want to try anything else. I figured that if I ever did want to go back to stock (and I do now), that I had my stock ROM backed up to one of the extra slots that safestrap gives you. Well, I looked- turns out I don't. I checked my external hard drive and found a backup folder with "TWRP" in it, and in it a folder called stock -1970 -04- 02. I placed that folder in the corresponding TWRP folder on my phone's extsdcard, but safestrap doesn't see it in the restore screen. Does it have to be a zip? I totally forgot all this stuff; I haven't messed with my phone in half a year.
If that doesn't work, I'd really be cool with wiping everything and flashing a stock ROM build. I don't know where to find one though, and it should be mentioned that my Alliance ROM build has "MJ5" in it somewhere, if that means anything.
I've rambled a bit, but hopefully someone can point me to my best options.
Thanks!
Use Odin to flash the file with "home" in it from this thread.
http://forum.xda-developers.com/showthread.php?t=2838117
It will load the latest stock firmware. You can re-root with towelroot.com
The "home" file doesn't wipe anything so your apps will be intact. If you want a full wipe and install use the other 4 files in that thread.
Thanks
Worked like a charm, thanks!

Categories

Resources