All right this problem has now been solved! Thank goes to khamsakamal48 for posting the solution for the problem. The problem is solved by replacing the updater-script with the one that is used in the GSM version the of Rom. Then Using the latest 4ext recovery, wipe everything and install. Thank you to everyone that have participated in trying to get this solved. This might also work with other recoveries, but has not yet been confirmed.
Updater-Script: http://db.tt/sUfk5p8E
Latest 4ext recovery: http://db.tt/sP5o7HhJ
only thing i could think of is try a different recovery .I haven't had any trouble at all booting miui an i use cwm touch version.
Alright I'll have to give it a try. Was trying to avoid that but oh well. Thanks!
Sent from my Incredible 2
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
kylesag21 said:
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
Click to expand...
Click to collapse
Can you give us a little more background on your phone setup? Have you flashed roms successfully before or is this a first time? Are you s-off?
Sorry bout that. I am S-off and I am able to flash all of the other roms available. But when it comes to this one it just won't flash.
Sent from my Incredible 2 using Tapatalk 2
I have been having this same problem. I am going to try to go through everything I have done to see if I can get more info.
I had MIUI V4 (2.9.29 CDMA) running shortly after rooting this phone (maybe 1 week ago). I installed it from the latest TWRP, so that isn't our problem. I loved it and everything was great. I am unsure what radio I was on at the time, and I think that may be where my problems came in.
I successfully installed ViperINC 1.0.0 after doing a factory reset, wiping cache, dalvik from my WORKING MIUI V4. It booted and I played with it for a few hours, but wanted to go back to MIUI. At this point I was on the firmware from nitsuj17's thread. When I tried to factory reset and install MIUI clean again I started having the same trouble as OP. Since then I have tried every radio I could get my hands on, and may have even been a bit sloppy about what firmware I flashed (the only one I'm unsure of is CondemnedSoul's Return to stock as I am unsure what all it included other than radio and stock rom). After a lot of different attempts, I used CondemnedSoul's PG32IMG and went back to stock where I had everything working fine (for stock). I got an OTA update, but wasn't satisfied so I kept trying different radios from the pinned post on the Development thread (really only .0312 and .0320 as well as the first leaked firmware I linked from nitsuj17). So far nothing has worked to get me any further than the OP unless I just use a different rom. Had this rom never worked I would just talk to the developer, but as I had it working before and no idea what changed I'm at a loss.
I don't have enough posts to get something on the Development forum, but if anyone here can help, I'd really appreciate it.
I've been scouring these forums looking for someone who has made progress on this issue. I'm going to make a list here of posts by people having similar problems, if not the exact same. I have yet to see anyone successfully address them.
One of a few people on the MIUI V4 thread who have had the same issue. I had this rom running at one point, though, so I'm not sure what change caused it to stop. I definitely get further with the TWRP recovery (freezes on "android" splash screen) than the 4ext recovery (reboots to recovery).
I don't believe the JB issues are directly related, but similar problems.
Similar to the Jellybean issue above. More similar to my own situation since I also only started having trouble after flashing ViperINC, but I have formatted, wiped and reverted (even to S-ON and unroot Froyo) so much that I can't see how it would have changed anything that I have not removed. This thread has 3+ people with the same sort of issues. Last report one of them installed ViperINC with all defaults and let it run for a few minutes then wiped and re-installed CM10 with success. I may try this, only with MIUI. I have no idea what settings would be slipping through.
And the cdma miui is one of the only roms that boots for me. Running it now. I think Zelmo is right, there's something sticking around with that Aroma script. I've flashed aosp roms over sense roms and vice versa without even wiping and never had issues like these. I've basically wiped this thing with steel wool and always the same thing. It's gone atleast 15 mins with it's bootloop/freezing max cpu process. It ain't gonna boot! I was up until 2am last night ****ing with it. I'm done.
I'm nearly there. Had I never been able to run MIUI, I would probably have dumped it by now, but it's like an itch I can't reach at this point. There is just something there that I can't see or imagine that is hanging in through every wipe I can find. I just formatted my SD card and did a bunch of wipes (I know that has been tried) and I'm going to try VenomINC with all defaults like Zelmo88 had some success with. If I don't have any luck getting to MIUI from there I'll probably go back to my dinc or buy a new phone soon. This one was really an experiment anyway.
Will follow up if I can figure out anything else.
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
stoicwood said:
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
Click to expand...
Click to collapse
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
grunt9800 said:
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
Click to expand...
Click to collapse
I think most of us first noticed these problems around the time we flashed Viper, but I have nuked this thing so hard from so many different directions since the last time I ran Viper that I can't imagine anything surviving. Still, a little too coincidental.
Running the GSM version didn't last long, either. I played around with trying to get it to use my sim, but as soon as I changed some of my network settings it went into a bootloop tailspin and somewhere along the way corrupted my /system. That took a little work to get around, so now I'm back to aeroevan's CM10 which runs OK... other than what doesn't.
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
[SOLVED]
khamsakamal48 said:
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Worked perfectly first try! Now running CDMA version without problem. I don't know why it works, but it works. Everyone thank khamsakamal48!
I'm not seeing a meta-inf folder. Is there another place it could be?
Sent from my vivow using xda premium
I believe it is in meta-inf>com>google>android
Updater-script should be located there.
Sent from my HTC Incredible 2 using Tapatalk 2
Nope, no meta-inf. Back to Google
Sent from my vivow using xda premium
Are you using 7zip to open up the zip file?
Sent from my HTC Incredible 2 using Tapatalk 2
I'm too embarrassed to tell you what I was trying got it now, thanks again
Sent from my vivow using xda premium
Related
Wellp. I win.
I win a no expenses paid trip to my nearest Sprint dealer.
Ever since I used unrevoked to root my phone in November, I've been voraciously digging through these forums for tasty roms. I've been snorting lines of Cyanogen, MIUI, and a myriad of other, well-designed roms.
Using a on older version of hboot (pre 1 methinks) I was able to avoid the latest hassles with ClockworkMod (plus, I down(up?)graded to 2.6 via RomManager).
Tonight, as I was enjoying some tasty foodstuffs at my local foodstuff vendor, my phone rebooted. Then, it rebooted again. Then again. I once made the folly of flashing a new rom without running the appropriate wipes, and was no stranger to the bootloop. I patiently fired up hboot (my poor volume rocker is all but wore out) and ordered up the trusty recovery mode.
...then it rebooted again... and again... and again.
PusSidiasus: ONOES! I HAVE THE WTFBBRICKED MY PRECIOUS!
SmartAsSidiasus: Hang on for a second, let's check the internet. Try this link: tinyurl.com/4vgeyeg
PusSidiasus: ...
Unfortunately, my internal dialogues are not nearly as witty. Also, my best attempts to de-brick-ify were for naught. Fastboot gave some wacky error message when I tried to flash a new recovery, and installing via PC36IMG.zip did nothing to improve the situation. I even went so far as to install a stock image someone pulled from an RUU (with a 2.02hboot, so as to avoid wimax woes)...
Still, a whole lotta nothing. I can't do anything beyond hboot, and whatever recovery image I install (Clockworkmod, AmanRa) the machine still bootloops.
At this juncture, I've resigned to taking the phone into the sprint store and playing dumb. It is a stock rom, though I hope the attendant misses the S-OFF bit at boot. Which brings me to my proper question:
1) Has anyone run aground a similar issue and found a way out?
OR...
2) Anyone know how to turn S-(back)ON in my current situation?
Any insight would be greatly appreciated. Also, you can rest assured that I'll be rooting again whatever phone I walk away with, and the work that is exhibited in these forums is amazing. Keep churning out wonderful roms and guides.
Sidiasus
(Currently, Sadiasus... )
First...... Wrong subforum. Try Q and A.
Second, in all your rom flashing, did you maybe forget to wipe, and re-wipe before your rom install?
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Happened to me when trying to root my brothers Evo. (Already had mine rooted). I thought the phone was bricked because there was no recovery installed and all that worked was hboot. I tried several different versions of PC36IMG.zip until 1 finally worked.
Cheers
Yes! try updating with PCM36IMG.zip ROm that should help you out, ex "Sprint lovers". Good luck.
sidiasus said:
Ah piss. I'll move subforums. Also, the last flash I ran (from Evervolv Gingerbread -> MIUI 1.1.07) I am quite certain I wiped. I may be mistaken, but non-wiped user data shouldn't bork recovery.
Click to expand...
Click to collapse
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Mikedick said:
Recovery thing confused me a little bit. I didnt get in your post where that became a problem. If a phone bootloops all on its own, its usually due to wiping either not being done, or a certain recovery not wiping it correctly. At least that's what ive seen in all my reading. Hope you get this ironed out.
Click to expand...
Click to collapse
No problem, I tried to write in a more humorous style than the other "HALP" threads, and my ability to clearly relate the important details suffered. Thanks for the good wishes!
Etiquette question: I've duplicated this thread in Q & A, should I just delete this one?
Also, thanks to all for the lightning fast responses, trying more PC36IMG'ses.
Nah, just let it die.
Found like you're radio fried, it's a well known defect on some evos and incredibles. Try to put it in the fridge while turned off and afterward it may run for long enough to turn s-on.
Sent from my PC36100 using XDA App
Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67
So, I don't really post on forums because I'm pretty tech-savvy, but I have a big problem that I can't fix, and I can usually fix everything (thanks to you guys!)
This morning, my incredible acted up as I was checking an e-mail and it froze, so I decided to battery pull because restarting my phone didn't work. (Note, my incredible has been running VERY solidly on a CM7.1 nightly). As I tried to boot up the phone again, it would stay on the white HTC Incredible screen. When I rebooted into recovery thru HBOOT, i realized that there was an error mounting something, like recovery_log, or something like that (i didn't mind this because I thought I knew what I was doing), but I tried restoring my old nandroid backup that was working well, but it didn't work. It said it couldn't format /data or something... It ended up staying on the white HTC incredible screen. So, I wiped data/cache like 10 times, and dalvik cache as well and tried re-flashing a clean install of cm7.1 stable, but didn't work again - led me straight to the white Incredible screen. So, installing a fresh rom AND restoring a solid backup didn't work... so...
I found the RUU 2.3 stock rom on the development forums, and tried to install that like I do with the radios (PB31IMG.zip) through HBOOT, but no cigar. It did go PASSED the white screen, but boot loops at the Droid eye.
So, I thought I'd find a different stock img, and found the 2.2 official OTA .zip and installed it the same way, but got the exact same result (boot loops, forever).
Any suggestions? I can't think of anything else.... I feel like my phone is bricked, but I didn't do anything to make that happen.
I feel like something happened that made me not able to format the /data, and stuff. I even formatted my SDcard in case it was the problem.
Any help is appreciated. Thanks!
Load the RUU onto a different fat32 sd card and see if you are able to boot.
Sent from my ADR6300 using XDA Premium App
i'll try that and give an update. thanks for the reply!
*update* no luck. same thing happens. i tried on three different sdcards formatted fat32...
Can you factory reset and flash a ROM from a different sd than the one you were using? Description sounds like bad sd, and AOSP roms interact with the sd on boot. If original (CM 7) sd is toast, it'll never boot, hence different sd card and prefably RUU
Sent from my ADR6300 using XDA Premium App
I had this happen once where no matter what rom i flashed all i got was bootloops. I had to get the stock froyo ruu.exe that you run from your pc and install it that way. Then once installed boot up and go to settings/sd & phone storage and do a factory reset from there. This factory reset is a true reset as it wipes out vzw programing also. After reset folow on screen steps to reactivate your phone, you can skip the rest of the setup. Once thats done your good to go just flash clockwork or amon ra recovery and then flash what ever rom you want. No guarantees but it worked for me.
NOTE: This assumes you are s-off, if your not after flashing the ruu you will have to use unrevoked to regain root and s-off again.
You can also try wiping /system and /boot.
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
if you are non root. you will need to download the RUU.exe for 2.2 and install if from you pc.
http://androidforums.com/htc-droid-...mplest-instructions-ever-windows-xp-only.html
follow that and your phone will be back to the day you got it out of the box.
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
SlimSnoopOS said:
All the recommendations prior to Synisterwolf's post require root.
Some of the "abbreviations" are detailed in the Droid Incredible Development section. If you head over there you can read up on a beginners guide to root terms and helpful links in one of the top four threads namely:
If You're New to Modding/Rooting, Read This First! (Updated 08/05/10)
I will say though:
CM7.1 = CyanogenMod 7.1 (this is a rom)
OTA = Over The Air
2.2 = Froyo (Android software version 2.2)
RUU = basically refers to a file that people use to revert back to the Droid Incredible's pre-root status. Although there are additional steps as well.
Click to expand...
Click to collapse
RUU = ROM Update Utility
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Then its gotta be a hardware failure.
Sent from my sexy assistant. (AMOLED HTC Incredible)
wow... what a bummer. thanks for the help anyway, it's much appreciated.
sl4m said:
no luck, I installed the program on my XP machine, but the app can't connect to the phone.
The phone literally keeps rebooting over and over.
Click to expand...
Click to collapse
Does it give any specific error code when it says it can't connect to the phone?
Someone correct me if I'm wrong but don't you have to have HTC sync installed on your pc to use an ruu.exe? Do you have that installed?
Sent from my ADR6300 using xda premium
I'll try it again to verify the code, I'm pretty sure it was "170"
sl4m said:
*token post to get my post count high enough to ask for help in the hacking section, dumb rule btw. FAIL*
Mine is now stuck in a continuous boot as well. It's not rooted and have no idea how to fix it.
I see instructions in this thread but they mean nothing to someone who doesn't know what the abbreviations stand for or how to go about the commands required.
Click to expand...
Click to collapse
I had this issue the first time i rooted my phone and attempted to put on a ROM, and i resolved it when i found this post to get back to stock. I also used this to fix a problem where my phone had a black screen with a line through it on booting to recovery or attempting to do a nandroid back up:
droidforums.net/forum/droid-incredible-hacks/95406-how-correctly-unroot-incredible.html
All i did was basically use the PB31IMG Method without turning s=on, ( i had stock radio and still have 7.28 )
1) download that PB31IMG.zip and drop it on the root of your sd card ( it has to be named ( PB31IMG.zip ) so make use you have file extensions showing on your PC.
2) boot to hboot and and let see the file and install it
3) used unrevoked ( remove sd card ) to aquire root again.
idk if this helps, but this seems to get me out of the few weird situations i had
sl4m said:
I'll try it again to verify the code, I'm pretty sure it was "170"
Click to expand...
Click to collapse
Check this out to fix your 170 error.
http://androidforums.com/incredible...170-171-solution-windows-7-a.html#post1472468
This low key happened to me and I booted in to HBOOT and went to clear storage and it did its thing and booted up, from there I had to activate it then I was set!
Sent from my ADR6300 using XDA App
=D
Sent from sweet snacks off tapatalk.
I'm suddenly having storage issues with every ROM that I flash after running a ROM with some script that isn't widely used.
First I'll give you a brief idea of my problem. I"m running out of storage and get notifications from the market saying as much after I download and reasonable amount of apps. The thing is... It show's I have used 738MB of ext4 out of 1.5 so that isn't the issue. The problem is internal memory. My phone won't move dalvik cache for some reason. When I run any ROM with a2sd or m2sd they both say that there is a problem and leave the dalvik cache where it is.
I think my internal folders are jacked up from 40ad2sdx or a zip that was used to clear memory before the ROM. There was a ext4 superwipe cleaner to load before the ROM. I did that without researching first. When I did go looking for the thread about it, it plainly said that it was for one phone only, and it wasn't my phone. I believe it was the Galaxy S3, but I can't be certain. It was a week ago. It was advised not to use it on any other phone because part of what it did was reset the internal folders. Does this mean I can now flash a ROM for the galaxy s3? Lol Just kidding.... Seriously, the second part is all my speculation and I have been wrong many times concerning android. Will somebody help me get my phone back in oem condition please?
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
nate234 said:
Okay, I'm not even sure what you did here, because not knowing the script, anything could have happened.
Try wiping everything and flashing stock rooted here, then go from there with other roms after that.
If that doesn't work. Here's what I would do. It might be a major pain, but it is almost a surefire fix.
Unroot and return to stock, then root again.
[UNROOT]
[ROOT]
For future reference, NEVER flash anything that is meant for another device. (Obviously, if it's a port then you're ok.)
ALSO EXTREMELY IMPORTANT: Backup your SD card, and wipe that puppy clean!! Only partition using Amon-RA recovery, otherwise it will screw you up quite often. I repeat, if you do not have the partition done correctly, then odds are that A2SD or equivalent won't work.
Click to expand...
Click to collapse
I did the wipe and flash to stock earlier today, then flashed the Pac man ROM but the issue is still there. I had looked at unrooting my phone earlier today also. I'm glad to read this because it lets me know that I do have some idea of what to do. Thanks for the reply. I'll post here again with the results. Check back soon.
EDIT----> Man, my phone is okay. I loaded up a fairly recent ROM by Tronit, and it worked fine. It was the ROMs. Just to be sure, I went back to the last two ROMs just to see, and they did the same thing again. Now I'm on the AOKP Unnoffical and it's working just fine. The a2sd is working perfectly like it should, and my dalvik cache is moving to ext4. It was just coincidental that the last three ROM's I loaded all have issue with the a2sd. It's funny how nobody else see's problems but me. I looked in the bin file of one of them and it's missing part of the a2sd file. The other two have weird init.d files that I don't know anything about. I'm assuming the a2sd problem is related to that. It's funny how I see lots of problems, and report them, but I get blown off by some people as a noob who is making mistakes. I am a noob, and I do make mistakes, but I know some of my theories about problems are correct...... I gotta get me some respect by compiling my own ROMs.
Status update..... My phone is jacked up for sure. It does work with the AOKP Unofficial by Tronit, but this morning when I cleared my cache with Smelkus Recovery, it had major problems with almost every app. Clearing the cache in recovery is something I've done with every ROM and this has never happened. I uninstalled all the apps and reinstalled them. Got them working again. Everything seemed to be okay. However, when I cleared my cache with Android Tuner, again it ruined every app. I've used android tuner every day for two months to clear the cache and never had problems like this. Something is very wrong.
*****edited and deleted for the sake of peace*****
Long story short, I flashed something made for another phone. I can't explain why I did this without taking up lots of pages, and it doesn't even matter really. Lets just focus on the solution. Here is the link. I flashed both of the zips in the link.
http://forum.xda-developers.com/showthread.php?t=1477955
So I think my permissions for the files on my phone are out of whack. Is that what I"m reading is the possible outcome of flashing these if your phone is not the one listed? Please post your thoughts. I need them.
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
g2435 said:
Try backing up your SD card on a computer and format you SD card and repartion it
Sent from my PC36100 using Tapatalk 2
Click to expand...
Click to collapse
I did that. Both with Smelkus, and Mini partition wizard. Same problems. I just tried to fix permissions with smelkus 4.3 on the AOKP Unofficial ROM and it took a minute for it to do it's thing. The line of dots was two full rows. So when It loaded back up, I suddenly see the same disk Icon in my notification bar, and now this ROM says it it out of memory. Man, it was working fine. I had twenty more apps on it too and I uninstalled them. It was working fine then, so with twenty less apps, it shouldn't suddenly say "Running out of Storage space."
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
nate234 said:
I have told you this already: Please do not flash things meant for other phones, it could mess up. If it's meant for another device, it might screw yours up. To stay on the safe side: If it's not generic (works for every Android phone) or phone specific (exclusive to the Evo 4G) then don't flash it.
Click to expand...
Click to collapse
I flashed this about a eek ago, when I was looking for the ext4 wipe. I thought it was the same thing as another zip despite what it said. Stupid... I know. I think this may be the cause of my problems, but I can't be sure. I don't know at all really. Just speculations. I reflashed the CWM touch and used to flash a stock ROM. Gonna try that again. I ran the test on CWM touch and it said that the
/sys/class/android_usb/android0 was missing and unable to perform the test. Can this be the cause of my problems?
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
nate234 said:
Don't beat yourself up man, it was an honest mistake, just learn from it and you'll be alright.
Now the optimal recovery for this device would be the Amon-RA recovery, and I recommend redoing what I said in my first post once you have Amon-RA installed. Amon-RA is an awesome recovery, and it's super easy to install. Check out this easy-to-follow video on how to install by clicking here.
Do that, then do what I said in the previous posts. Let me know what happens, because I'm almost certain this should work.
Click to expand...
Click to collapse
I tried loading the Pacman ROM again with CWM and it wouldn't even load. It gets stuck in a bootloop. After that I flashed smelkus and went back to the Stock Rom.
*****edited and deleted for the sake of peace****
RADIO EDIT------
Sent from my PG86100 using xda app-developers app
edited and deleted for the sake of peace
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
I was finally able to get my phone straightened out. I loaded up a stock ROM then decided to use my SD Maid to look around. I found a file with completely different dates on it, but it wouldn't let me remove it. I ended up copying everything else in the subfolder and then deleted the parent folder. Then added everything else back. Wah lah.... magic. I don't know what that file was or where it came from but it was killing my internal memory. I'm wondering how it stayed from ROM to ROM. I dunno, but it's gone, and the Pacman ROM is lovely now. BOOM!!!!
jlmancuso said:
As I stated in my pm give me a day or so till I get back home and I will check into a fix for you. Only don't expect any one on one help. If the fix works cool if not I will dig further. TNN strives to help with any issue no matter who is at fault. I will look at the wipe script you flashed and see if it can be undone. Just be prepared of the possibility that your phone may never work correctly again.
Sent from my PG86100 using xda app-developers app
Click to expand...
Click to collapse
Whatever I did only fixed part of the issue. I'm left with in a situation where every time I go into recovery my downloaded apps stop working. It is cutting part of them off whether I clear cache or not. All I have to do is power off into recovery, and when I reboot, all of my downloaded apps begin giving messages that "Unfortuately such ans such has stopped." My phone becomes inoperable. The only way I can keep it working is to send a new launcher to my phone from the market, let it install, then open it up and uninstall all the downloaded apps. I'm pretty sure this is an easy fix for someone like you Mancuso. I have a logcat and it show LOTS of errors that I have never seen before on any of my other logcats. What are my options? Tell me what to do to get my phone back to absolute OEM and then I'll reroot. UNLESS you know of some fix.
I've supplied a logcat from Catlog if you or anybody else wants to have a look. I'd really appreciate some help here. I love my Evo and I love learning this stuff. If somebody can help me positively identify the problem, I can most likely figure it out from there. Please give me your suggestions here. I'm nothing without some guidance on this. It's way out of my scope.
I've included a link to the ext4 script wipe that I used. How I got to this page, I do not know. However, I ran it because this page said it COULD POSSIBLY work on other phones despite the fact that it was made for another phone.
http://www.xda-developers.com/android/darkside-super-wipe-easily-wipe-partitions-when-flashing-roms/
And I flashed both zips from the thread that the story links users to. Here is the link for the two zips.
http://forum.xda-developers.com/showthread.php?t=1477955
I'm not sure this is the problem. I'll try to find the Vold.fstat thread that I tried on my own before you came up with the 40ad2sdx solution for the MIUI ROM.
This is the memory fix I tried as mentioned above.
http://forum.xda-developers.com/showthread.php?t=2246909
Please note that you see before and after pics of sd storage. You can see that my pics clearly resemble the after pics shown in this thread. I believe this is my problem. How can I undo this?
This post reflects the only things I did outside of normal flashing. My problem is here somewhere...
The fix you used is for samsung devices. That could have caused your problems.
ok guys i have htc one x and my nephew just got a wildfire s and tried to root and rom it.
so heres where im at. ive flashed this rom but im stuck at the htc logo.
he installed the latest CWM for this phone 5.0.2.8. then full wipe and installed a few roms but none worked and then i got here.
with my one x i have to flash boot.img but as far as i can see thats not the issue here??
can anyone help?
It's a gsm wfs with a sim slot. I'm assuming the next step is to install the correct RUU for the phone right?
the phone is stuck at the htc logo
Can someone possibly point me to the correct RUU? Its a UK phone that was on Tesco/o2 mobile and I cant find the right RUU.
Any help is greatly appreciated
Nothing??
Sent from my HTC One X using Tapatalk 4
Seriously no help at all????
Sent from my HTC One X using Tapatalk 4
Oh well
Sent from my HTC One X using Tapatalk 4
So I get told of four posting in a rom thread and get told to post here and I get zero help. Ffs
Sent from my HTC One X using Tapatalk 4
Usually when you're stuck on the HTC logo it's because the ROM you are trying to flash also needs the kernel flashed, which you have to be S-off to do and the developer you got the ROM(s) from should have provided it. You were very general, but I presume a full wipe was cache, dalvik-cache, data/factory reset, and (optional), battery stats? Are you just plain stuck, can't do a factory reset and/or didn't make a backup before trying the ROMs? I was going to flash this ROM at one time and he gives some pretty good instructions to follow...sounds like it might work for you. Better than staring at the HTC logo, eh?!
http://forum.xda-developers.com/sho...ht=what+files+can+i+remove+from+my+wildfire+s
Thanks for the reply. I can get to recovery but I can't install anything as recovery can't seem to find the internal storage.
Sent from my HTC One X using Tapatalk 4
Most recoveries are going to look on the external storage, the actual sd card. Can you move your ROM to that and give it a try? Just to save time, I'll say I'm figurin' the sd card is formatted (FAT 32) and if there's a problem seeing that you might have to go into, "Mounts and Storage" and mount the sd card. I'm in the middle of a movie and will get back after, if you have another question I can help with. Hope it works.
ok so i finally got CWM to see the sdcard and i installed a rom and flashed the boot.img.
now the phone just reboots into recovery. what the hell is wrong with this dam phone????!?!?!
So far we've been successful with the, "One step back and two steps forward" approach so:
You extracted the boot.img file from the ROM zip to your PC for use after and then installed the ROM, rebooted the phone into recovery>>fastboot, hooked up to the PC in a command prompt and changed directory to where you have the boot.img and the adb/fastboot command files and at the command prompt typed: fastboot flash boot boot.img
Typically you would then type: fastboot erase cache, or back in recovery wipe the cache and reboot to find the ROM (slowly) booting for the 1st time.
I'm a one step at a time person (so I know what worked). So if all that's true, and it's still stuck in a recovery loop then I'd try wiping cache again and dalvik-cache and rebooting.
If that doesn't work I'd suggest one of two things:
1. Start over and I don't mean at htcdev, but wiping cache, dalvik, and data...install ROM, flash boot.img, wipe cache reboot...or
2. We can go over all the steps (as briefly as possible for both our sakes) and I'll say why: one time I was writing a macro and it just wouldn't work, after 3 days of spending too much time on it each day I asked someone else to look at it and he found I had missed a slash or used a comma instead of a semi-colon or some one simple thing. So it wouldn't hurt to see if there was one little thing skipped.
Lastly for now - if you post again, whatever you post, just for my curiosity tell me which (compatible with the Wildfire S) ROM your wanting to use.
First of all I just want to thank you for trying to help.
I did those steps perfectly and they've always worked with my HTC one x but no dice with this wildfire.
http://forum.xda-developers.com/showthread.php?t=2206780
That's the ROM I'm trying to get to boot.
I really want to fix this phone for my nephew but its not looking good.
Sent from my Nexus 7 using Tapatalk 2
I know how it is...we all get fixed on wanting one thing and then intent on making it work.
I did a quick look at the page for your intended ROM and first thought, aha...in the instructions to install, the wipe file he provides seems to indicate for a marvelc in the name, so does it wipe all it should on a gsm WFS; but, then he's got that link to the ROM for a marvel c(dma); anyway I did a quick search of the thread (there are 119 pages!) for, "Reboots into recovery" and found this (among others):
http://forum.xda-developers.com/showthread.php?t=2206780&highlight=reboots+into+recovery&page=102
I do see where there was a rebooting into recovery problem with this ROM and a fix was applied in July 2013. I think the link above is to the, "fixed" ROM (hopefully for GSM WFS) but I'm not going to claim that as fact; again, I just took a quick look between my morning news readings and did not read around the problem or, about Lizards patch.
We could go deeper like formatting partitions, but since he has provided a wipe script and there's so much info there...well, I'm not dumping you, but I am thinking researching there might get you more specific results since we've pretty much been going through the generic version of flashing ROMS. What do you think?
ok i read the entire thread and flashed all the fixes etc but no dice. however i did flash a different rom altogether and now everything seems to be working fine!!!!!
dont know why that never occurred to me before!
i must say thank you for all your help. it is very much appreciated
now for some strange reason the original rom now works !!!!!!!!!
For as long as I"ve been fooling around with electronic devices, it often still just seems like, "PFM" sometimes; and, I don't know how many times I've done the right thing over and over and over and then just given up and set it aside only to pick it up again a day or two later and then everything goes like it should...and not doing anything different!
I'm glad you got everything going again, and I'm sure you just want to get back to enjoying it, but I'm curious to know (along with anyone else that might be following) what ROM finally worked, and then you ended up going back to which, "Original" ROM, stock?
I hear you on that. So many times I've had to work on systems for hours then magically I'll do something and it works.
What I did was flash another custom ROM which was unofficial cm10.2 it's on the main page made by owl. That booted up fine but I wasn't happy with that ROM so I flashed the one that I've been trying to flash, marvellous cm10, the one you helped me with.
The only thing I did differently was flash the boot. IMG after I flashed the ROM , I usually flash the boot image first on my one x.
And that's about it.
Sent from my Nexus 7 using Tapatalk 4
I clicked a thanks (and thank you for yours). I enjoyed the exchange and glad you've got it going. The Wildfire S is a great phone, especially for me (although I have my SIM in another phone now) and hopefully your nephew, because it needs to be managed, tuned, tweaked, etc. which is what I love to do and hopefully your nephew will too and keep at it now that you got him off to a good start.
good start yes, but i have to fix the mistakes!! lol
Do you know where u can get int2ext?
Sent from my HTC One X using Tapatalk 4
You caught me right at the end of a movie I was watching!
I've always been happy with Link2SD, but you can't beat moving all of data to SD.
Try this:
http://forum.xda-developers.com/showthread.php?t=1716124
also, this is an easy way to get init.d if you don't have that...I think it's needed for int2ext:
http://forum.xda-developers.com/showthread.php?t=1710980
Have fun!