[Q] HELP! Having problems installing apps after installing new ROM - Desire HD Q&A, Help & Troubleshooting

I've just rooted my phone and flashed the leeDroid ROM successfully, however a few days after flashing the ROM, my phone is unable to install any apps successfully. There is always a sign saying "Installation of xxxx is not successful"
Anyone have solutions to this problems? Do not really know what to do here

Try to factory reset your phone: settings>SD & Phone storage>Reset
If that doesn't solve it, download the ROM again and reflash it. And make sure you flash FULL-WIPE-1.3.zip first!

If you don't want to have to flash another app (for wiping data etc.) you can just do this from recovery where you can decide what needs wiping (between ROM's and re-installs though wipe everything).
Just my personal preference.
Sent using witchcraft via XDA Developers App.

sandmouse said:
I've just rooted my phone and flashed the leeDroid ROM successfully, however a few days after flashing the ROM, my phone is unable to install any apps successfully. There is always a sign saying "Installation of xxxx is not successful"
Anyone have solutions to this problems? Do not really know what to do here
Click to expand...
Click to collapse
I had a similar issue & FIX posted here: http://forum.xda-developers.com/showthread.php?t=1054073
Not sure if will work for you, but maybe a few ideas.
Edit: Usually clearing Market cache, reboot into cwm recovery & delete dalvik does the trick, but for me, Gmail was part of the problem as well.
Sent from my Desire HD using XDA App

Foladko said:
Try to factory reset your phone: settings>SD & Phone storage>Reset
If that doesn't solve it, download the ROM again and reflash it. And make sure you flash FULL-WIPE-1.3.zip first!
Click to expand...
Click to collapse
FULL-WIPE = the most effective solution for the all the problems!!
in adition he can do "formats" in the paragraph "mounts and storage" (if I donĀ“t forgot the location )
This way already you insure yourself of having a hyper-clean ROM

Related

[Q] stuck at white htc evo 4g screen - not flashed anything yet

hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Maybe its the busybox that you downloaded. You should hit up recovery and do a full wipe! The start up again. What rom are you running, most roms have busybox included so when you download it I've seen phones get the white screen of death. Grab a rom and reflash it. Since you put busybox that nandroid you made probably is no good. Reason I'm telling you all this is because has happened to me before. Good luck
Sent from my PC36100 using XDA Premium App
ravissimo said:
hello all, noob here. searched the forums already, not quite the same problem here.
I just rooted my phone with unrevoked 3.32, had zero problems. I confirmed that i had nand unlocked in hboot (says S-OFF). I started up my phone without problems after rooting, checked and I had superuser permissions in the app drawer. i then proceeded to download busybox, rom manager, my backup for root, and titanium backup from the market, but I did NOT open any of them. I thought I would do a nandroid backup first.
I rebooted into hboot, went to recovery. this started up clockworkmod (that came with unrevoked 3.32), went to backup and restore, and hit nandroid backup. It completed, said done, then i selected "go back" and selected the first option, reboot system now.
I then tried to turn my phone on, just regular power on not into hboot, and i get stuck at the white htc evo 4g screen, it then reboots, and continues to cycle up to that point.
I have NOT flashed anything other than rooting my phone. i haven't wiped anything, done anything else than what i have there.
Hboot version is 2.10
radio version says 2.15.00.11.19
clockworkmod version is 2.6.0.1
EVO is from June 2010, not a new evo.
I can get into hboot and recovery, no problems, but i can't startup the phone.
Please help! i just want to start up the phone, don't want to flash anything yet. Thanks in advance.
Click to expand...
Click to collapse
Well, I'm not sure what exactly went wrong for ya, but I might suspect it was something to do with some of the apps you downloaded prior to making your backup. The first thing to try, would be to boot to recovery, and wipe cache, and then go to 'advanced' and wipe dalvik cache. Then try to reboot. If that fails, then you're next option (without flashing a new ROM) is to do a data/factory reset. You will however lose all of your apps, settings, contacts, texts, etc. You unfortunately don't really have any other options, unless wiping cache's helps you out. If a factory reset doesn't allow you to boot, then you're most likely going to have to flash a new ROM. And also, I thought that Unrevoked flashed the latest clockwork recovery, which would be 3.0 or somehting like that, no?
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
You don't need to download busy box, I would delete that app. If you flash a rooted rom it should already have busybox; if you just rooted your phone and want to download busybox on your current stock rom then it will be ok. I would wipe and flash a new rom just to be safe.
Sent from my PC36100 using XDA Premium App
ravissimo said:
Hi k2buckley,
So I tried wiping the cache and the dalvik cache then rebooted, no luck. Does this mean the nandroid backup I made is also corrupt? Restoring that won't do anything will it? So the options are to do a factory reset or flash a new rom? If I lost everything anyway, I might as well try to flash a new rom.
However, to clarify, I didn't "install" busybox. I downloaded the app but I didn't open it up and click install. So even if I flash a new rom, then I install busybox and do a nandroid backup it will work? If so, why didn't it work this time? If I do a factory reset, then do the same thing and install busybox, will the same thing happen? Is busybox incompatible with the sense froyo that comes from the sprint OTA?
Click to expand...
Click to collapse
Well, I'm not exactly sure why you want to download busy box so badly. Any rom comes with busy box cooked in. I have only once installed busy box. The only time i remember having to do it, was Immediately after I rooted with Unrevoked, i went to use Titanium, and had some error. I hit the problems button and that updated busy box from there. Other than that, I've never messed with it.
And yes, most likely your nandroid backup is not going to be of any value to you. You could try restoring it if you'd like, but I predict it would be a waste of time. And I'm not sure that it matters that you didn't 'open' and click install on busy box. If you downloaded it from the market, wouldn't it just download and install itself automatically? I would just flash a rom, and be done with it. Roll with whatever version of busy box comes with the ROM you flash. As you said, you're only option is a factory reset now, and if you're going to do that, you certainly may as well flash a custom rom at the same time. You just need to download a rom, and put it on your sd card. You can mount the sd card as a disk drive to your computer from within recovery. I use amon ra, and its called USB MS TOGGLE. I'm not sure what it's called in clockwork, but the option is there. So put the rom on your sd card, perform a complete wipe, (i'd flash calkulin's format all.zip as well), flash a rom, reboot, and forget about anything with busy box. It will be installed on the rom already.
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
If you can get a logcat that should show what is causing it to bootloop. It's 'adb logcat > logcat.txt' to do it, run that and wait for it to loop 3 or 4 times before pushing Ctrl+C to stop it.
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
ravissimo said:
Well, the only reason I download busybox was because I wanted to use titanium backup and it is required. Other than that, I could care less about it. It does not install automatically after downloading. You have to go into the app and choose which version you want to install and I didn't install it. The thing is I didn't want to install any roms in the first place. I wanted to just root the phone for the purpose of wifi tethering. So basically my better option is doing a factory reset.
I won't be able to do this til I get home in a few hours, so if anyone else has any suggestions on how to fix this without losing my data, I would appreciate any tips. Thanks.
Click to expand...
Click to collapse
Right. But unfortunately now, your data seems to be lost. Did a factory reset help anything? If not, you got to wipe and reflash a rom.
Sent from my PC36100 using XDA App
ravissimo said:
Busybox isn't included in the ROM because I didn't flash a ROM! I'm using the sense 2.2 froyo Ron that comes from sprint and HTC. I didn't flash anything as I stated in the title. I just did a nandroid backup and now my phone won't boot.
Click to expand...
Click to collapse
I understand that. As I stated, I'm not sure what's causing your problem. As xhausx said, try getting a logcat
Sent from my PC36100 using XDA App
What method of rooting did you use? What recovery do you have right now? As hausx said you could do a logcat and he'll check it out!
Sent from my PC36100 using XDA Premium App
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
ravissimo said:
Hi xHausx,
I will have to wait til I get home to try that, but how do I get into the prompt to type that in dos. Do I need to run anything in hboot or clockworkmod before connecting my Phone and trying that? I am a noob, so even though I've read a lot before rooting, I don't know much. Please assume I need a step by step. Thanks again.
Click to expand...
Click to collapse
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
xHausx said:
You can use the root tools zip from the link in my sig to get to adb, there is a script in there called OpenShell that will bring up a dos prompt in the right folder. Rooting should have enabled adb during boot so you should be ok on that end.
Click to expand...
Click to collapse
OK, so I downloaded and extracted the auto-root tools only zip from your sig, and then ran OpenShell.bat and typed as you said "adb logcat > logcat.txt" with my phone plugged in. said "waiting for device" and then i turned on my phone and let it boot 4-5 times before ctrl+c and pulling the usb. all the logcat.txt says is...
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
am i doing something wrong?
my apologies, i've only throughly read on how to root, i hadn't gotten into flashing or anything else yet. just been on xda site for a few days now reading all i could about rooting (which went fine, but now i'm screwed).
dirkyd3rk said:
If you download busybox from the market and it already has it built in the rom you might bork the rom and get a bootloop. Try it and see for yourself !
Sent from my PC36100 using XDA Premium App
Click to expand...
Click to collapse
For the hell of it I did just that and it did bork it.... lmao
chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
Did it really? Lol It did it to me man I was pissed!
chefdave12118 said:
For the hell of it I did just that and it did bork it.... lmao
Click to expand...
Click to collapse
man, for the life of me, i can't believe i didn't do a nandroid before i downloaded the app. for some reason i thought only downloading an app from the market, not flashing anything or whatever, would not screw up my phone.
anyway, since my data is lost, i wanted to try again. can i flash the unrevoked S-ON utility and then the latest Sprint RUU and then re-root? i read somewhere else that it won't remove my wimax/RSA keys or SD card, is that correct? is there a way to backup my RSA keys before I do anything else? should i do that, re-root, then nandroid, then mess with stuff? i basically wanted a stock Sprint EVO but one that's rooted so i can run root-based apps, that's what I want to get to.
Flash the Amon Ra recovery via the AR pc36img.zip file in hboot method, then reboot to recovery, do a full wipe/factory reset and try to boot to system.

[Q] Rom manager installs corrups phone

Everytime I install a custom rom on rom manager, it has corrupted my phone and each and everytime I'd have to restore it. Is there any way to fix it? I've seen comments on the custom roms and people have commented that it works fine on the DHD.
Hi drkhrsy
Kindly explain further by your meaning of corrupt? This would allow us here to clearly understand the problems you're facing. Thanks.
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
drkhrsy said:
Well I first installed cyanogenmod 7 and that gave me the boot loop. After restoring the phone I thought I'd try another ROM, so I went to download the TB 7.0.3 ROM and that booted up the phone but I had constant popups on HTC sense force closing and couldn't do anything else so I had to restore the phone again. So yeh, I'm not really sure what I'm doing wrong here.
Click to expand...
Click to collapse
Did you do a full wipe before flashing those roms, multiple fcs normally indicate that you didn't try a full wipe then reflash either of your chosen roms.
Full wipe as in factory settings?
Well I've installed a new RUU after the boot loop problem, isn't that considered as a full wipe? or should I just do a wipe again now?
I had that horrible boot loop aswell after installing Rom.manager but I fixed it with a ruu
Sent from my Desire HD using XDA App
Installing a new RUU does not constitute that you have full wipe any data and cache. As the ROM you tend to flash is, in a small or large extent, relatively different from that of RUU. That why we always advised to do a full wipe whenever we wish to flash ROMs. Else it will cause some issues such as Force Close issues.
You have to boot into recovery and select Wipe Data and Wipe Cache. That you will consider yourself that you have wipe those data and caches. Then now you can flash the desired ROM in your list.
In addition, before flashing is best to do a Nandroid back-up.
Also do check on your recovery version before you flash any ROMs as different ROMs need/may require different version in order to be flashed successfully(i.e. no or minimal issues)
Cheers mate.
aiight sweet, I'll give that a go.
Cheers!
You're most welcome.
drkhrsy said:
aiight sweet, I'll give that a go.
Cheers!
Click to expand...
Click to collapse
Memory serving EVERY ROM says you MUST perform a wipe of data and cache if coming from a different ROM. This is custom ROM 101. Please read instructions thoroughly before doing things like this. The ROM devs don't spend their free time writing instructions just for the hell of it.
Regarding ROM Manager, don't you get asked if you want to wipe data and cache when you flash a new ROM (or is that not an option on the free version)?
Yeh I do get asked for wiping data and cache, I do that and it just seems to still screw up. Also backing up my files through clockwork seems to make my phone get stuck on the HTC boot up screen which requires me to reformat using the RUU file.
I would suggest re-flashing the recovery.img file.
Also, are you using the same cwm-r version to restore as used to create backup? For example, If version 2.x.x.x was used to backup you can't use 3.x.x.x to restore.
Sent using witchcraft via XDA Developers Premium App.
I've just checked my CWM-R version and its recovery version is at 3.0.2.6 hmm now I cant get into the recovery boot screen :S. I'd just most likely restore the phone again and try root the phone again. but thanks anyway
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
drkhrsy said:
nvm I got in the recovery boot. Yeh the CWM-R are the same version.
Click to expand...
Click to collapse
I think you miss understand. I don't mean do they match wherever you look.
Did you make the original backups using version 3.0.0.x or 2.5.x.x?
Sent using witchcraft via XDA Developers Premium App.
drkhrsy said:
I'd just most likely restore the phone again and try root the phone again.
Click to expand...
Click to collapse
You don't need to do that, just redo the recovery.img
Sent using witchcraft via XDA Developers Premium App.

[Q] Need help with flashing roms Galaxy s3

I tried flashing two different roms (synergy and chemistry) on my sprint galaxy s3. It turns on but then wont go past the "galaxy s III" logo. I just restored my backup and all is well but I really want to get multi window on this thing so I could really use some help as to what is not letting me boot up all the way. The last thing i messed around with rooting was my DroidX and with that it really mattered a lot which version of android you were flashing from. I have 4.1.2 the most recent update. Is that why these roms are not working? Any help would be much appreciated I am very excited to get a killer rom on this bad boy.
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
CNexus said:
Did you clear /data, /system, cache, and dalvik cache before flashing? If not, what is your flashing procedure?
But no, the current version should not make any difference when flashing because you are clearing everything anyway
Click to expand...
Click to collapse
I boot into recovery after i put the rom on to my sd card. Then wipe the factory data, cache partition, and delvik cache. I do those steps twice, then install the rom. The install seems to go fine, it always says successful at the end, it just wont go past that screen. Does it mater which version of clockworkmod I use?
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
CNexus said:
You need to wipe /system too. A factory reset only clears app data, and thats no help if you're not wiping the OS as well because you're installing the new one on top of the old without cleaning up first...and thats why it wont boot because different pieces are getting mixed and not together with the files it should be with
It should say something like "format /system"
Click to expand...
Click to collapse
Thank you so much for your quick response. As far as I can tell, I am wiping everything I should be. I use clockwork recovery mod version: and the choices it gives you are: Wipe data/factory reset, wipe cache partition, and wipe dalvik cache. From all the instructional threads I've read, those are the only things you need to clear out before the install. My clockwork version is v5.5.0.4 which i think might be really old. Could that be my issue? Does it matter how I rooted it? I just tryed to put jellybomb v14 on it and it didn't even give me the galaxy s III logo. Luckily it booted back into recovery though. I really don't want to hard brick this thing.
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
A-Shin said:
Which recovery are you using?
For TWRP, I generally recommend formating system too.
Also, make sure to flash the rom zip and THEN the gapps.
Click to expand...
Click to collapse
clockworkmod v5.5.0.4
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
Make the switch to TWRP v2.3.1.0 (newer ones I've heard have problems) but you will be thanking me later. It's way easier and much better than CWM... just an FYI for ya!
cchrisrollins said:
clockworkmod v5.5.0.4
Click to expand...
Click to collapse
I suggest trying a flash with TWRP. If you are unsure how to install TWRP, just download the Goomanager app, then choose install Open Recovery Script. But, before you install or change anything, look around a bit on how to install it. Make sure you follow directions step by step. After you have installed TWRP, try flashing again. Good luck!
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
cchrisrollins said:
Haha, so it looks like switching to twarp is something that i need to do, I'll start researching how to do that. I don't thing clockwork is causing the issues im having, but I could certainly be wrong. Since my phone is rooted, that also means the bootloader is unlocked rite?
Click to expand...
Click to collapse
Samsung bootloaders come unlocked by default, so yes
Easiest way to switch is to download Goo manager from the Play Store and have it install TWRP for you
Generally speaking, CWM is great on most devices, but for the S3 it's TWRP that's the best and easiest to use
And when flashing new roms, make sure to always format system, it prevents corrupted files from showing up because you would be installing the new system right on top of the old one if you don't
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you made a nandroid backup in TWRP (I'd recommend to put it on the external memory, but that's just me), you should be good to try any ROM you want (only Sprint ROMS). Just follow CNexus's post (linked for posterity). Wipe system as well as factory reset, cache, and dalvik, prior to installing the ROM.
cchrisrollins said:
So I did as you suggested. I installed twrp from the play store. I made a backup on there so I should be ready to tryn flash again. The only thing is I use this phone for work all the time and if mess this thing up I'm gonna be in deep doo doo haha. So with the last several attempts failing, I'm a little apprehensive to try again. I'm going to re-odin and flash a different root just to be safe (I used team epic v5). Can you guys recommend a good root to use for my s3?
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
If you've already rooted, re-rooting isn't going to fix anything, so no need to go there.
As previously explained and detailed, do a full system wipe, and you'll be good to go.
Thank you guys so much for your very quick responses, thank you for bearing with my noobishness too haha. I am going to tryn reflash jellybomb tonight, I'll post on this thread how it goes (hopefully good).
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
cchrisrollins said:
So unfortunately it was the same result with the TWRP. Tryed doing it with a few different roms. Some roms will boot to the "Galaxy s III" logo and others like jellbomb wont even get that far. It just flashed the Samsung logo and that was it. It's gotta be something simple that im missing here, but I can't figure out what it is. On the jellybomb install afterwards TWRP did come up with a message that said something along the lines of: your phone doesn't appear to be rooted, would like to install bla bla bla. So that doesn't make sense, because I know that I do have root access. Feeling pretty frustrated because I'm doing everything the correct way. HELP!
Click to expand...
Click to collapse
It took me like 4-5 months to personally figure out that the problem was the kernel. You need to flash a kernel right after you flash the ROM. Either the stock kernels or better kernels like Anthrax will do. I know that for jellybomb, there's a kernel included in the Rom but for some reason,it got stuck on the gs 3 logo if I didn't flash another kernel.
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
cchrisrollins said:
Oh thank goodness there is something else I can try, I was out of ideas. Thank you!
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
No prob, just hit dat thanks button do you know where to get the kernels?
Zin0 said:
No prob, just hit dat thanks button do you know where to get the kernels?
Click to expand...
Click to collapse
I tryed the KT47 AOSP Jellbean kernel after flashing jelly bomb and it did the same thing it did before, black screen after flashing the samsung logo
Now I did go into fix permissions and it did say failed, is that abnormal?
This is my exact procces:
1. boot into TWRP
2. factory reset
3. system wipe
4. cache wipe
5. Dalvik wipe
6. Install from external SD: jellybomb v14
7. Wipe cache/Dalvik
8. Install Kt47 kernel
9. Wipe cache/Dalvik
Anything wrong there?

[Q] Recovery and Rom Install Problems

Help, I will describe the following and any help I would love. I have the PRIMOC VM usa HTC ONE V.
Using Hasoon2000's All in one toolkit I have successfully Unlocked my phone, flashed TWRP recover 2.4.4, got root, and made a backup.
I then continue on to wipe cache and system and Factory reset to prepare to install ANY ROM. When I try to install the rom every time it just says Error in /sdcard/...[wherever rom is] (Status 1) FAILED
So then I proceed to restore my backup (this is why you always make a backup) and that works fine
Does the "(Status 1)" mean anything important?
I thought this was happening because I was running the newer radio so I used the RUU tool and now am using the good radio (not 0928) But this did not fix anything. This same thing happens over again. I have checked to make sure and I do have full root privileges.
I then tried to flash boot.img first and jmz kernel flashed successfully, but no rom will flash.
Why will NO ROM install?
I feel like I am missing something obvious but can't figure it out.
Also, whenever I do the factory restore it goes through all the process then fails when trying to wipe sd:ext , but my card is not partitioned. <I didn't know if that would be any help>
I am not a complete newb at all of this (running lg optimus for years- just new to the htc methods)
NEED Help please...
Can anyone help me out with this?
I have not made any progress since yesterday. I am successful at flashing kernels, I have flashed the boot.img of the sic kernel, but on both kernels I have no WiFi with the stock ROM.
So I either need to find the stock boot.img or have help flashing a ROM that fails everytime.
When every instruction says "Extract ROM" that is only to pull out the boot.img right, we don't flash an extracted package you flash exactly what you downloaded right?
sdxben said:
Help, I will describe the following and any help I would love. I have the PRIMOC VM usa HTC ONE V.
Using Hasoon2000's All in one toolkit I have successfully Unlocked my phone, flashed TWRP recover 2.4.4, got root, and made a backup.
I then continue on to wipe cache and system and Factory reset to prepare to install ANY ROM. When I try to install the rom every time it just says Error in /sdcard/...[wherever rom is] (Status 1) FAILED
So then I proceed to restore my backup (this is why you always make a backup) and that works fine
Does the "(Status 1)" mean anything important?
I thought this was happening because I was running the newer radio so I used the RUU tool and now am using the good radio (not 0928) But this did not fix anything. This same thing happens over again. I have checked to make sure and I do have full root privileges.
I then tried to flash boot.img first and jmz kernel flashed successfully, but no rom will flash.
Why will NO ROM install?
I feel like I am missing something obvious but can't figure it out.
Also, whenever I do the factory restore it goes through all the process then fails when trying to wipe sd:ext , but my card is not partitioned. <I didn't know if that would be any help>
I am not a complete newb at all of this (running lg optimus for years- just new to the htc methods)
Click to expand...
Click to collapse
When u flash sickkernel make sure you also install the zip through your recovery that should fix your WiFi problems and which recovery are you using ? Twrp or cwm?
Sent from my HTC One V using xda app-developers app
Obeezy562 said:
When u flash sickkernel make sure you also install the zip through your recovery that should fix your WiFi problems and which recovery are you using ? Twrp or cwm?
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Hi Obeezy562,
my advice is to use the recovery program CMW or TWRP to re-format your external SD card. Then follow the normal instrutions and install the rom from zip using your recovery program. If you still have the same issue just let me know and I'll ponder longer.
regards
mcgi5sr2 said:
Hi Obeezy562,
my advice is to use the recovery program CMW or TWRP to re-format your external SD card. Then follow the normal instrutions and install the rom from zip using your recovery program. If you still have the same issue just let me know and I'll ponder longer.
regards
Click to expand...
Click to collapse
I'm not the one with the issue is sdxben lol I was just helping him but you are correct. I also recommend people cwm.
Sent from my HTC One V using xda app-developers app
Obeezy562 said:
I'm not the one with the issue is sdxben lol I was just helping him but you are correct. I also recommend people cwm.
Sent from my HTC One V using xda app-developers app
Click to expand...
Click to collapse
Ok, so tonight I will reformat my sdcard with TWRP then try to install the ROM. I tried the CWM recovery, but it was not touch based and did not respond to the power button as the OK, only the volume rocker worked.
I will try CWM recovery if someone can provide a link to the latest one, perhaps I was using an old one.
Twrp 2.4.4 I've also had issues with flashing some roms then downgraded to Twrp 2.2.0 and everything has been well since
sentfromtx
I can add that twrp 2.4 does have some issues. I use a cwm I found on google somewhere and if works just fine.
Sent from my HTC One V
http://forum.xda-developers.com/showthread.php?t=1871243
try this one out, should set up everything fine. Let me know if you need any further help

Status 7 Issue_Reborn

I know this issue has been covered before on various occasions but I really need some help or recommendations as to what workarounds are possible to fix this issue.
I read pretty much every post, and followed every guide to fix the status 7 error. I was able to root, install CWM and flash any custom rom's prior to this error. Yesterday tried going from a custom JB rom to ParanoidAndroid rom by doing factory/reset wiping everything delvik etc, permission fix, factory data, system wipe etc... error appears failing every time no matter how many times I wipe.
I even flashed my stock Bell rom via Odin and rooted, CWM, and tried flashing but still get the status 7 error.
Any input would be gladly appreciated..
Regards,
Try twrp or a slightly different version of cwm
ogikovacevic said:
I know this issue has been covered before on various occasions but I really need some help or recommendations as to what workarounds are possible to fix this issue.
I read pretty much every post, and followed every guide to fix the status 7 error. I was able to root, install CWM and flash any custom rom's prior to this error. Yesterday tried going from a custom JB rom to ParanoidAndroid rom by doing factory/reset wiping everything delvik etc, permission fix, factory data, system wipe etc... error appears failing every time no matter how many times I wipe.
I even flashed my stock Bell rom via Odin and rooted, CWM, and tried flashing but still get the status 7 error.
Any input would be gladly appreciated..
Regards,
Click to expand...
Click to collapse
try twr instead of cwm it worked for me.
What version of cwm are you running?
Is it just a status 7 error or does it say anything more?
Update to latest CWM or use TWRP
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
jayRokk said:
Update to latest CWM or use TWRP
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
I tried using the latest CWM and TWRP but still had no success.
I had to edit the zip ROM file, /META-INF/com/google/android/updater-script by deleting the first line only.
I tried this already but I must have incorrectly saved it, it worked the 2nd time around.

Categories

Resources