Yesterday I flashed the deodexed and debloated Rom for the DNA and no I don't have permission to write to my internal storage, On the Rom thread they said to fix this you have too relock and ruu. I know how to fastboot oem lock but I dont know how to ruu can someone please help as I'm am new to the forums and couldn't post in the development section.
Sent from my HTC6435LVW using xda app-developers app
The easier way to fix the problem is to just format /data in recovery then reboot. All of your storage/settings will be wiped but the problem will be fixed. Just make sure to back up your files off of your phone ahead of time.
Sent from my HTC6435LVW
Thanks man I got it to work just mounted storage and flashed storage and I fixed permission... Out of habbit
Sent from my HTC6435LVW using xda premium
Related
If it does get bricked or bootlooped is there a method similar to odin, or rsd to unbrick? This is my first HTC device. Thanks
Sent from my ADR6400L using XDA App
Brick means there is no recovering. You toss it and get another one.
As long as you can get into bootloader, you are not bricked. As posted above, the correct definition of a bricked phone is a phone that will not boot anything including the bootloader. This goes for any phone from any manufacturer, not just HTC. The phone ultimately is a paper weight at this point, and there is nothing that can be done, unless you have money for a JTAG device. I'm not even sure if a bricked Thunderbolt has been successfully revived with this device. Someone else will need to comment on that.
Now if you mean recovering a phone where its OS no longer boots, yes it can be re-flashed through bootloader (full RUUs and Radio) or recovery (custom ROMs).
Sent from my ADR6400L using XDA App
Thanks for the help. Is there an app similar to odin or rsd that is run from the pc or is it all done through the phone on HTC?
Sent from my ADR6400L using XDA App
Most work is done on the phone itself. In case of a non booting OS, the computer is only needed to transfer ROM files to the root of the SD card and to check the MD5 checksums. Custom recoveries such as Clockwork Mod or Aman_Ra will allow USB connections to set the SD card as Mass storage in case of a non booting OS.
Odin and RSD are flash programs, where as our phones are capable of flashing themselves without use of a flash program.
Sent from my ADR6400L using XDA App
that answered my question perfectly. thanks everyone for all the help. im new to the bolt and came from the charge and must say that i am really happy already with what ive seen
To reach the Hboot where you can flash a recovery ROM turn off your phone hold volume down to reach this screen any flash should be named PG05IMG.zip
Sent from my ADR6400L using XDA App
c2thej said:
that answered my question perfectly. thanks everyone for all the help. im new to the bolt and came from the charge and must say that i am really happy already with what ive seen
Click to expand...
Click to collapse
Here's a great place for you to get started. Read everything in it. It explains how to root, unroot, flash, troubleshoot, etc. This should answer anymore questions you may have as you continue to explore.
http://forum.xda-developers.com/showthread.php?t=1220484
Sent from my ADR6400L using XDA App
awesome! you guys are a big help. im not gonna lie i dont miss my charge at all lol
So what's with this whole pno5img or whatever? Is it needed to flash roms?
Sent from my ADR6400L using XDA App
c2thej said:
So what's with this whole pno5img or whatever? Is it needed to flash roms?
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Yes it is needed as this is the flash file. The correct file name is PG05IMG and it is a .zip file. Full stock RUUs and Radios must be named PG05IMG (if when you DL it and it is not then re-name it)
Any file with this name MUST be flashed through HBOOT (bootloader). Just remember once you are finished flashing, you need to delete the flash file from your SD Card.
Custom ROMs are different in that they do not need to be renamed however they MUST be flashed through Recovery and not HBOOT.
Sent from my brain.
Ok so custom roms can be flashed in cwm. Does this include rooted stock roms or are those still in hboot with the pg05img.zip file?
Sent from my ADR6400L using XDA App
Sorry for the late response but yes, rooted stock ROMs get flashed in recovery.
Sent from my brain.
Awesome thank you
Sent from my ADR6400L using XDA App
Hi everyone,
I'd like to erase EVERYTHING in my SD card, No personal data whatsoever, & still keeping Elegancia ROM.
How do I do that please?
I thought about formatting SDcard, but am afriad that would format the ROM content & can't use the phone anymore.
Please advice,
Thanks
dsymbol said:
Hi everyone,
I'd like to erase EVERYTHING in my SD card, No personal data whatsoever, & still keeping Elegancia ROM.
How do I do that please?
I thought about formatting SDcard, but am afriad that would format the ROM content & can't use the phone anymore.
Please advice,
Thanks
Click to expand...
Click to collapse
Format Data from TWRP
Addicted2xda said:
Format Data from TWRP
Click to expand...
Click to collapse
Thank you Addicted2xda
Addicted2xda said:
Format Data from TWRP
Click to expand...
Click to collapse
AFAIK formating /data results in loss of personal data and you most likely will have to re flash rom
Sent from my HTC One X+ using xda app-developers app
reaper90 said:
AFAIK formating /data results in loss of personal data and you most likely will have to re flash rom
Sent from my HTC One X+ using xda app-developers app
Click to expand...
Click to collapse
I think he wants to sell off / loan the device or something... he wants to remove everything except ROM
Refer to the OP
Addicted2xda said:
I think he wants to sell off / loan the device or something... he wants to remove everything except ROM
Refer to the OP
Click to expand...
Click to collapse
but does the rom still work when formatting /data partition? there seems to be a lot of important stuff in there or is it just userdata and it is like a factory reset when formatting i'm curious if that works.
reaper90 said:
but does the rom still work when formatting /data partition? there seems to be a lot of important stuff in there or is it just userdata and it is like a factory reset when formatting i'm curious if that works.
Click to expand...
Click to collapse
Yup, it works - I have formatted my data partition along with doing a factory reset. It worked fine. (Elegancia - I am not sure if some x/y/z ROM has any issues though .
Go to your settings and factory restore or use a file explorer and delete everything
Sent from my HTC One X+ using xda app-developers app
dsymbol said:
Hi everyone,
I'd like to erase EVERYTHING in my SD card, No personal data whatsoever, & still keeping Elegancia ROM.
How do I do that please?
I thought about formatting SDcard, but am afriad that would format the ROM content & can't use the phone anymore.
Please advice,
Thanks
Click to expand...
Click to collapse
If you're selling the phone or something similar, download the RUU, plug your phone in, and run the executable to get the phone in the state it comes in out of the box. This will flash the stock ROM, recovery, etc.
Sent from my Nexus 4 using xda premium
kylealanr said:
If you're selling the phone or something similar, download the RUU, plug your phone in, and run the executable to get the phone in the state it comes in out of the box. This will flash the stock ROM, recovery, etc.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Thank you kylealanr.
kylealanr said:
If you're selling the phone or something similar, download the RUU, plug your phone in, and run the executable to get the phone in the state it comes in out of the box. This will flash the stock ROM, recovery, etc.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
First you need to lock the bootloader...
Then you can attempt to flash the RUU - you will succeed only if your hboot is 1.35 or lower...
Ah yea I had to do the same thing you want to flash to an odexed stock Rom before attempting the ruu otherwise you will be on an h boot boot loop the only way to get out of that is to re unlock the boot loader use hysoon 200's tool kit if your already on h boot 1.40.00 you cannot run the lower h boot you will have to go to the HTC site and download the at&t ota ruu I went through the same thing to do a warranty swap ecause my digitizer went out and no I didn't play with it even with a locked boot loader stock Rom/kernel and the ruu ran it still bas dead spots in the same places
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 08:16 PM ---------- Previous post was at 08:11 PM ----------
Quick question anyone download the Google key board? Its a Google made aosp key board that you don't have to root to install and use I'm liking this a lot better so far
Sent from my HTC One X+ using xda app-developers app
---------- Post added at 08:40 PM ---------- Previous post was at 08:16 PM ----------
Or if you want to keep the ROM and you still have the in lock key and the hysoons kit relock the boot loader then in lock the boot loader with the key it will erase everything but the ROM
Sent from my HTC One X+ using xda app-developers app
Lol this is like ages ago but it still bugs me somehow so i am out to resolve it here :-\
This is my first time asking a question, feels awkward as i have been helping people all along. Lets get to the main point.
I followed all the steps in the topic. I mounted /system and /data
I went on to flash the kernal........all seems fine. I went to flash the rom........after flashing, cwm showed some error talking about some file called recovery.log
I did not wipe anything and i rebooted. After that, i lost cwm and i was in a bootloop. The next day, i unbricked it by flashing stock rom(as my signature says) What bugs me is others who wiped (no need to wipe data) had problems but i did not wipe and i have problems. My friend said is because i did not wipe but i believe that the error showed befor i had time to wipe. I want to let go of this matter so i am just asking for an answer. Not really important :-\
Sent from my LT22i using xda app-developers app
AndroidNoob69 said:
Lol this is like ages ago but it still bugs me somehow so i am out to resolve it here :-\
This is my first time asking a question, feels awkward as i have been helping people all along. Lets get to the main point.
I followed all the steps in the topic. I mounted /system and /data
I went on to flash the kernal........all seems fine. I went to flash the rom........after flashing, cwm showed some error talking about some file called recovery.log
I did not wipe anything and i rebooted. After that, i lost cwm and i was in a bootloop. The next day, i unbricked it by flashing stock rom(as my signature says) What bugs me is others who wiped (no need to wipe data) had problems but i did not wipe and i have problems. My friend said is because i did not wipe but i believe that the error showed befor i had time to wipe. I want to let go of this matter so i am just asking for an answer. Not really important :-\
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
You can't flash kernel with locked bootloader. Maybe that's why you get bootloop.
Clear data, cache and dalvik cache and after that install the rom.
DaRk-L0rD said:
You can't flash kernel with locked bootloader. Maybe that's why you get bootloop.
Clear data, cache and dalvik cache and after that install the rom.
Click to expand...
Click to collapse
But it said locked/unlocked bl and the one i flashed was supposedly for lb...
Sent from my LT22i using xda app-developers app
AndroidNoob69 said:
But it said locked/unlocked bl and the one i flashed was supposedly for lb...
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
No mate. This rom will work on both locked and unlocked bootloaders but you can only install the kernel provided on unlocked.
So i suggest you to flash stock rom, root, install cwm for lb and install the rom. This way should work.
AndroidNoob69 said:
But it said locked/unlocked bl and the one i flashed was supposedly for lb...
Sent from my LT22i using xda app-developers app
Click to expand...
Click to collapse
Are you official JB of xperia P with root access and locked boot loader ?
If so, open ROM zip and delete the kernel file, and flash it!
Sent from my Xperia U using xda app-developers app
But who can explain the error by cwm
Sent from my LT22i using xda app-developers app
Ok so I have the newest Verizon firmware and have been able to unlock bootloader root and install custom recovery now when I flash a custom Rom it bootloops and I just have to restore my nandroid backup any ideas
Sent from my ADR6425LVW using XDA Premium 4 mobile app
ruler1976 said:
Ok so I have the newest Verizon firmware and have been able to unlock bootloader root and install custom recovery now when I flash a custom Rom it bootloops and I just have to restore my nandroid backup any ideas
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
if your s-on you forgot to take the boot.img from the rom and flash it via fastboot
Edit: Only use boot.img from the rom your gonna install....make sure you read proper method in first few posts from developer as there is instructions to make your phone work properly
Yes, you need to flash the boot image if you are S-ON...
But save the headaches and don't even bother flashing a ROM from your installed recovery (you really don't even need to install a custom recovery at all), all you need is the "recovery.img" from the recovery ZIP file of choice, although I currently recommend TWRP, in your adb directory and the ROM on your SD card then...
1) Reboot into Hboot and start Fastboot, connect PC
2) Type "fastboot boot recovery.img" and wait a minute for the Recovery to start on the phone
3) Wipe as per normal for installing a ROM
4) Install/Flash ROM zip as per normal
5) Reboot and enjoy!
Thank you guys this is my first HTC someone stole sgs3
Sent from my ADR6425LVW using XDA Premium 4 mobile app
ruler1976 said:
Thank you guys this is my first HTC someone stole sgs3
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
It's worth going S-Off if you are going to flash very often at all... makes it so much easier to just flash one file and done.
It seems scary, but if you follow the instructions, it's not bad at all. I've done it twice now.
Also, you will have to flash a stock rom first (it's been done on other rom's, but ymmv... its safest to go stock before s-off).
I am stock newest ics
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Is that ok
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Yes
Sent from my Rezound using xda app-developers app
ruler1976 said:
Is that ok
Sent from my ADR6425LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You can do it from custom roms too, from what I've seen, but since you are stock, that is perfect
So I screwed up royally and to an experienced rom flasher its probably no big deal and an easy fix. I was in my in recovery( TWRP 2.6.3) and installed the HTC Dumlock trying to flash a rom without a computer. My Rezound is 4.0.3, and now I get as far as the Verizon 4G LTE black screen and that's as far as it will boot... I've tried to wipe and restore like I have in the past when I've screwed up and now I'm out of ideas. I think that the boot image is "corrupted" don't know if thats the right lingo but when I reboot to bootloader the image name that always came up is now different. Can someone please help me with my dilemma? Oh and if detailed description is needed about everything that I did- I kinda freaked out and panicked and I tried so many things to fix it that I don't remember all that I did.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
undeadking said:
So I screwed up royally and to an experienced rom flasher its probably no big deal and an easy fix. I was in my in recovery( TWRP 2.6.3) and installed the HTC Dumlock trying to flash a rom without a computer. My Rezound is 4.0.3, and now I get as far as the Verizon 4G LTE black screen and that's as far as it will boot... I've tried to wipe and restore like I have in the past when I've screwed up and now I'm out of ideas. I think that the boot image is "corrupted" don't know if thats the right lingo but when I reboot to bootloader the image name that always came up is now different. Can someone please help me with my dilemma? Oh and if detailed description is needed about everything that I did- I kinda freaked out and panicked and I tried so many things to fix it that I don't remember all that I did.
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Extract the boot.img from the ROM zip file, flash ROM, reboot into bootloader and start Fastboot, then flash boot.img via fastboot on a PC, should clear it up...
In the future I would recommend going S-OFF via rumrunner, no more need to worry about flashing boot partitions separately ever again.
Ace, you are a genius! Got the rezzie back up and running! Flashed Tachyon 1.2, flashed the boot image via twrp and it started right up! Now if I go and delete the PH98IMG.ZIP will it still die again if I reboot in the future???
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
undeadking said:
Ace, you are a genius! Got the rezzie back up and running! Flashed Tachyon 1.2, flashed the boot image via twrp and it started right up! Now if I go and delete the PH98IMG.ZIP will it still die again if I reboot in the future???
Sent from my DROID RAZR HD using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, your good.
Sent from my Nexus 4 using Tapatalk
Just made a backup in TWRP and rebooted and all is well, you're awesome man. Thanks again
Sent from my Rezound on Tachyon using XDA Premium 4 mobile app