A few days ago I flashed Zarboz's 4.2.2 kernel over NOS 3.0.6 and found trickstermod would crash on launch or crash the entire phone. A complete wipe of system and internal fixed that.
With all the current issues I forgot why I wiped again but after flashing NOS the phone stays on the slash screen.
At this point I figure a ruu is needed. I relocked, an trying to use the utility but it stops after I click "update" no warnings or messages out just goes away.
I'm pretty sure it's dead but am looking for help before headed to Verizon for a new device.
Thanks.
Trying flashing the nos kernel separately
Phaded said:
Trying flashing the nos kernel separately
Click to expand...
Click to collapse
Thanks. I'm going to have to. I'm stuck S-On with HTVDEV not accepting a SuperCID.
Phaded said:
Trying flashing the nos kernel separately
Click to expand...
Click to collapse
No go. I'm stuck at the initial splash screen not the bootanimation.
fr4nk1yn said:
No go. I'm stuck at the initial splash screen not the bootanimation.
Click to expand...
Click to collapse
Are you able to get into fastboot or recovery while holding down the volume buttons?
durgis said:
Are you able to get into fastboot or recovery while holding down the volume buttons?
Click to expand...
Click to collapse
Yes, both.
What's really odd is when I run the fastboost Command to get the unlock code it's different Evey time. None of which htcdev will accept. I am supercid.
fr4nk1yn said:
Yes, both.
What's really odd is when I run the fastboost Command to get the unlock code it's different Evey time. None of which htcdev will accept. I am supercid.
Click to expand...
Click to collapse
Usually only your original code will work. Do you have the email still?
Phaded said:
Usually only your original code will work. Do you have the email still?
Click to expand...
Click to collapse
I fixed that by superciding with 2s, got the code after that. I'm trying to get rid of the custom splash screen but am getting a failed: remote not allowed error. The eng Hboot won't go away either. from what I'm reading it all needs to be changed to RUU(?).
Looked at the LG G2 and it "did nothing for me" so I'm back to trying to get this fixed. Feels like some progress although not really in actuality.
-Edit: I'm still unlocked S-Off trying to flash.
-Edit2: I thought 1.33 was the eng Hboot. DOH!
fr4nk1yn said:
I fixed that by superciding with 2s, got the code after that. I'm trying to get rid of the custom splash screen but am getting a failed: remote not allowed error. The eng Hboot won't go away either. from what I'm reading it all needs to be changed to RUU(?).
Looked at the LG G2 and it "did nothing for me" so I'm back to trying to get this fixed. Feels like some progress although not really in actuality.
-Edit: I'm still unlocked S-Off trying to flash.
Click to expand...
Click to collapse
You have a custom splash screen installed?
Phaded said:
You have a custom splash screen installed?
Click to expand...
Click to collapse
I did. It's now stock splash screen, 1.33.001 HBOOT, *** RELOCKED ***, I even flashed the 2.06 OTA so recovery is stock.
The RUU still disappears after clicking "Update", I'm DL'ing from a different source. I can only figure there's a problem with it.
-Edit: And that was it! Update is going.
Yea it shouldn't just disappear...
After clicking update, do ctrl+atl+ delete
Is the ruu still a running process? If so, give it some time... It might just be "loading"
If you need a new source still tomorrow I'll host it on my Dropbox
Phaded said:
Yea it shouldn't just disappear...
After clicking update, do ctrl+atl+ delete
Is the ruu still a running process? If so, give it some time... It might just be "loading"
If you need a new source still tomorrow I'll host it on my Dropbox
Click to expand...
Click to collapse
It was closing. I let it run while taking a nap earlier.
But now I have the 158 image error! Motherpussbucket!
fr4nk1yn said:
It was closing. I let it run while taking a nap earlier.
But now I have the 158 image error! Motherpussbucket!
Click to expand...
Click to collapse
That is usually hboot related. Flash stock hboot from my rts thread
Phaded said:
That is usually hboot related. Flash stock hboot from my rts thread
Click to expand...
Click to collapse
Thanks the 2.06 for messed me up. I thought supercid allowed downgrading. It apparently does not.
So much for that. I now have a 152 update error!
I'm back to thinking the hardware is messed up. That would explain my weird kernel problem.
TWO bad downloads! Before I gave up, which I was close I decided to download from the Hotfile link.
It too hours but... I'm now booted! MD5s probably would've saved me some time.
@Phaded I extracted the rom.zip just in case. I'm going to upload it later if you want to link to it.
flashing it through fastboot would probably be easier and it shows errors unlike the RUU updater.
Thanks for the help.
I have a question...
The RUU... Were you flashing it? Or running it on the computer? I only ask because of your attached pic.
Anyways, RUU.exe usually shows errors. I wonder if the one link is bad... I'll download from it tonight and run it on my throw away DNA...
Phaded said:
I have a question...
The RUU... Were you flashing it? Or running it on the computer? I only ask because of your attached pic.
Anyways, RUU.exe usually shows errors. I wonder if the one link is bad... I'll download from it tonight and run it on my throw away DNA...
Click to expand...
Click to collapse
I did everything possible is every combination.
While flashing after in "recovery", (black screen, HTC, and 4 exclamation points), I founda thread saying to try flashingthe rom.zip, so I did that too.
The photo is after unplugging the phone on that screen. It showed the error.
The HTC RUU shows the error afterwards but not that it was having a problem with /system.
Flashing through fastboot showed the error in realtime. Besides it skips that dreaded programand could be done in Linux or Mac
This is Odd...
I appear to be soft bricked again after flashing NOS and Zarboz kernel.
Going to try CM.
fr4nk1yn said:
I did everything possible is every combination.
While flashing after in "recovery", (black screen, HTC, and 4 exclamation points), I founda thread saying to try flashingthe rom.zip, so I did that too.
The photo is after unplugging the phone on that screen. It showed the error.
The HTC RUU shows the error afterwards but not that it was having a problem with /system.
Flashing through fastboot showed the error in realtime. Besides it skips that dreaded programand could be done in Linux or Mac
Click to expand...
Click to collapse
Could always do fastboot oem rebootRUU and then fastboot flash zip ruu.zip instead of running the .exe
Sent from my HTC6435LVW using XDA Premium 4 mobile app
times_infinity said:
Could always do fastboot oem rebootRUU and then fastboot flash zip ruu.zip instead of running the .exe
Sent from my HTC6435LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Did that again tonight. It's much quicker and easier than the exe.
I flashed the wrong splash image and it still took. I'm interested in if it runs any checks at all. That would be aewsome for restoring to stock.
Side note: my phone will boot CM-20130913, but not 20130914. this is so weird I checked my computers' memory with MemTest.
Related
I'm using the latest version of Joelz Sense Redefined and occasionally my phone would just restart when I'm using it. It happened to me today and it won't boot back up. I got it into fastboot by holding down and power after a battery pull but when I choose any of the options, it just shows me the HTC screen and the turns off. It also won't charge...I haven't had this before. Is there something like ODIN for HTC phones?
I don't know what ODIN is but if you're willing to start over you can run the RUU and get yourself back to stock. You'd have to download the latest 2.x version, relock the phone in fastboot, make sure you have HTC Sync installed on your pc, run RUU. Then you can flash Amon Ra again and install su from the AR developer menu to regain root. Then you can flash a ROM again.
Fera,
Thanks for the response. I was downloading an RUU in hopes that would work, but I currently can't find anyone offering them for more than a few kbps.
Did you remember to delete the .img file from your SD card the last time you did an install?
Yeah, I just used Scott's CleanFlash to flash the img.
RUUing actually failed. Said I had the wrong bootloader or something. I had indeed relocked.
which RUU did you run, the 1.xx or the 2.xx?
EmerikL said:
which RUU did you run, the 1.xx or the 2.xx?
Click to expand...
Click to collapse
RUU_Vigor_VERIZON_WWE_2.01.605.11_Radio_RS_0.95.00.1123r_3161E_9K_QMR_release_233635_signed
It says I have 3.10.
It's failing at Updating Signature....
Essentially I need the ICS RUU and I think I'll be okay. Anyone know where I can find a working link?
There isn't one but try searching for Awesome Recovery Tool in the dev section. It automates mainver workarounds. If that doesn't help your situation search "mainver" as you need to do a fix since your phone is on a higher mainver than the official one due to the ICS leak.
feralicious said:
There isn't one but try searching for Awesome Recovery Tool in the dev section. It automates mainver workarounds. If that doesn't help your situation search "mainver" as you need to do a fix since your phone is on a higher mainver than the official one due to the ICS leak.
Click to expand...
Click to collapse
Unfortunately I can't even get to recovery to use that tool :-( Yeah the mainver errors seem to be trouble if you can't even get to recovery...that's why I think that 3.10 RUU will be the ticket to get me back on track...
thatguy222 said:
Unfortunately I can't even get to recovery to use that tool :-( Yeah the mainver errors seem to be trouble if you can't even get to recovery...that's why I think that 3.10 RUU will be the ticket to get me back on track...
Click to expand...
Click to collapse
Well you won't get a 3.x RUU until the official ICS release afaik.
You said you can get into fastboot? Try flashing Amon Ra again, I read that v3.10 is best for ICS. And maybe the kernel in case that got corrupted.
Look at this post. You have two options to help you.
Personally I think that fix 2 will get you to where you need to be. I tried it before just to see if I could do it, and it was pretty easy.
EmerikL said:
Look at this post. You have two options to help you.
Personally I think that fix 2 will get you to where you need to be. I tried it before just to see if I could do it, and it was pretty easy.
Click to expand...
Click to collapse
I'm having trouble with adb not seeing my device although the fastboot devices command does show it. I am in fastboot on the device.
feralicious said:
Well you won't get a 3.x RUU until the official ICS release afaik.
You said you can get into fastboot? Try flashing Amon Ra again, I read that v3.10 is best for ICS. And maybe the kernel in case that got corrupted.
Click to expand...
Click to collapse
Tried reflashing Amon Ra and the kernel but the phone is just shutting off/going black when I choose Recovery in fastboot.
Did you get the file?
Are you in charge only mode?
EmerikL said:
Did you get the file?
Are you in charge only mode?
Click to expand...
Click to collapse
I got the Android SDK and the hex editor. The trouble is I can't get into charge only mode because you actually need to be able to boot into Android to get that. :-( So I'm stuck with only being able to work from the bootloader/fastboot/hboot.
thatguy222 said:
I had indeed relocked.
Click to expand...
Click to collapse
Have you re-unlocked since this?
EmerikL said:
Have you re-unlocked since this?
Click to expand...
Click to collapse
Yes, but I re-unlocked via the All-In-One tool. I'm currently showing as Unlocked.
And when you go into fastboot does it change to fastboot USB when you connect to your computer? Is HTC Sync disabled?
Sent from my ADR6425LVW using xda premium
Hi Everybody-
Last night I went to unlock my phone, and it froze. I'm running leaked ICS firmware, and it has been working fine for weeks. So, pulled battery, restarted, and it would not boot past the white HTC screen.
So far I have tried-
F
lashed a new kernel in fastboot
Restoring a backup (and flashing appropriate kernel)
Re-installing the rom and reflashing kernel
Still won't boot past white HTC screen.
I'm on the new firmware, so I thought I'd try to reflash the RUU. I have the PH98.. file on the SD card, it reads it but won't give me the option to flash, just returns to bootloader.
At this point i'm stuck, is there a way to force the RUU to flash? Should I think about getting S-OFF and trying to flash back to the GB RUU?
Thanks for any help!!!!!
Do s-off. DO NOT UNLOCK AFTER S-OFF. Then run gb ruu twice. Try booting back up after if no luck on the ruu then run in fastboot mode fastboot oem writesecure 3 and send in for a warranty replacement
Sent from my ADR6425LVW using XDA
Thanks! I appreciate the response. I still want to try to get the RUU to take without s-off, not sure what's up with that. Good call on not unlocking after s-off, maybe that will make the RUU take.
You could try running the ruu exe on windows if you haven't tried it yet.
Sent from my HTC Vigor
So, an update-
I flashed the RUU through fastboot (thanks, con247), it went fine but it still just shows the white HTC screen, goes black, then shows the white HTC screen again.
I am going to try unlocking again, flashing a new recovery and reinstalling a basic rom. At this point though, I have a bad feeling.
Has anyone seen anything like this!?!?!? It seems like something internal tweaked, but what would cause only that part (i guess \system, \data or something) to fail?
Thanks all for any help!!!
iaRIVR said:
So, an update-
I flashed the RUU through fastboot (thanks, con247), it went fine but it still just shows the white HTC screen, goes black, then shows the white HTC screen again.
I am going to try unlocking again, flashing a new recovery and reinstalling a basic rom. At this point though, I have a bad feeling.
Has anyone seen anything like this!?!?!? It seems like something internal tweaked, but what would cause only that part (i guess \system, \data or something) to fail?
Thanks all for any help!!!
Click to expand...
Click to collapse
Can you get back to fastboot by holding power and volume down? If so get to command prompt through platform-tools then type fastboot boot boot.img
that should hopefully get you to your rom. Thats what worked for me anyway.
If that fails
iflawdya said:
Can you get back to fastboot by holding power and volume down? If so get to command prompt through platform-tools then type fastboot boot boot.img
that should hopefully get you to your rom. Thats what worked for me anyway.
Click to expand...
Click to collapse
if you dont know the button combination use ADB
ENTER
ADB REBOOT FASTBOOT
or try
ADB REBOOT RECOVERY
then press your home key for a few seconds. choose wipe data. then reboot
hope this helps.
I helped him last night and the issue was resolved.
con247 said:
I helped him last night and the issue was resolved.
Click to expand...
Click to collapse
You the man!
con247 said:
I helped him last night and the issue was resolved.
Click to expand...
Click to collapse
Having the same problem with a friends phone...could you give some instruction on what you did?
If your on the GB firmware, run the Ruu.exe, you should be able to pull the battery and run from fastboot.
If your on an ics leak, con worked some magic so I could s-off, then run the GB Ruu. Check to see if wifi works, mine is c still broken and I will have to get a clnr. The easiest fix might be to just call for a replacement.
Sent from my ADR6425LVW using Tapatalk 2
Okay I have made a thread about this before, but no one had an answer for me, so I will try again, but I will be more descriptive of my issue.
So the other day, my Evo 3D, which is flashed to MetroPCS, lost its carrier settings when I was flashing a ROM. So I had to go home and use QPST to edit some files in the nvm/num folder (Using EFS). While I was editing, the program crashed, and I was forced to unplug my Evo.
Now, after it rebooted, it would go past the HTC Screen, and flash the boot animation for a split second, then shut off and restart. It would loop like this no matter how long I left it.
So I went into 4-EXT recovery, and formatted system, boot, data etc, and then flashed a ROM. Rebooted and got the same thing. So in a last ditch effort, I downloaded the latest ICS RUU for this phone, and tried all three methods to install. I ran the .exe, the program ran as expected, and the phone showed the progress bar on a black HTC Screen as updating, it rebooted when done, and then just continued to bootloop. I also pulling the rom.zip and renaming it to PG86IMG.zip and flashing it from fastboot. It worked and once it rebooted, did the same thing. I also ran it from fastboot usb, and got the same result.
However, I extracted the rom.zip and tried to use fastboot to flash individual .img files, and on EVERY one, I got "FAILED - Error: (remote: not allowed).
I had previously used the wiretrick to get S-OFF on my Hboot 1.58.
It says "Unlocked" at the top of the bootloader.
I really need to get my phone working, can someone PLEASE point me in the correct direction or at least help me out? Is my phone ruined? Is there a way I can clear the NV memory or something to truly reset the phone?
Once again, I will repeat, RUUs will not work!, I am S-OFF on HBOOT 1.58, my bootloader says "unlocked." No matter what I do it will bootloop. I can flash a recovery, but if I flash a rom it does the same stuff.
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
So now I screwed up, I got it to be able to erase/write in fastboot, I used fastboot erase instead of fastboot format and now my partitions are gone, how do I get those back?
AtmosFEAR4701 said:
I don't remember, but wouldn't the RUU fail if it was unlocked? Because it didn't fail, it just didnt work.
Click to expand...
Click to collapse
Sounds like a similar thing that happened to me when trying to flash a JB rom with a kernal that was not compatable....no matter what I did I could not get it out of the boot loop...I am Hboot 1.58 HTC unlocked and wire trick S-off...I finally flashed an old backup I had with a stock kernal and it fixed it all...dont know if this helps you at all but try wiping everything possible and flashing a stock kernal or an old backup you may have...
coal686 said:
When you ran the ruu.exe, did you lock the bootloader first? If you don't, the ruu won't work.
Click to expand...
Click to collapse
His s-off so doesn't matter if its locked or not.
iTzLOLtrain said:
His s-off so doesn't matter if its locked or not.
Click to expand...
Click to collapse
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
coal686 said:
Good to know. I always thought you had to lock the bootloader anyway but leave it s-off. I learn something new everyday. :beer:
Click to expand...
Click to collapse
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
AtmosFEAR4701 said:
Ok so I had accidenatly did "fastboot erase" and lost my partitions. I flashed the RUU again and now they are back, but if I try to use fastboot format, it says "Failed - Error: (remote: unknown command)." and it also said something about cannot determine partition type or something. I really need some help lol.
Click to expand...
Click to collapse
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
ramjet73 said:
Why are you using fastboot commands like "erase" and "format". Partitions should be formatted in recovery, not the bootloader.
If the RUU ran successfully it should reboot into the stock ROM when it finished. Did that work?
ramjet73
Click to expand...
Click to collapse
My first post says that I have run the RUU countless times and it still bootloops.
Nevermind... I sold it.
AtmosFEAR4701 said:
Nevermind... I sold it.
Click to expand...
Click to collapse
That's one way to solve the problem.
Sorry we couldn't figure it out.
coal686 said:
That's one way to solve the problem.
Sorry we couldn't figure it out.
Click to expand...
Click to collapse
It's okay. I am not buying another Evo 3D though. I am a MetroPCS customer so I buy flashed phones a lot, and I have a low budget so I'll either grab a flash Galaxy S2, or possibly grab the MetroPCS Galaxy S3 when I get some money.
I have a rezound that is now semi-broken. I've got Arman's recovery, but I can't seem to flash anything. I'm really hoping someone can help me out!
I have an hboot that says tampered, unlocked hboot,
VIGOR PVT SHIP S-ON RL
HBOOT-2.25.0000
RADIO-1.22.10.0421r/1.22.10.0424r
OpenDSP-v13.6.0.7611.00.0104
eMMC-boot
Apr 12, 2012 16:47:46
This whole thing is acting weird, and I've been working on it for a few hours. I can't seem to get a rom actually working. Maybe I'm not waiting enough, but I left it there for five minutes on the boot screen and it did nothing. I've tried both OTA superstock and Ecliptic, neither to any avail.
Fastboot is being a *****. I've tried everything I can to get fastboot to work, and it will not. It just simply wont work. So I'm hoping someone has some ideas, because I would really like to make sure this isn't my first real brick. plz <3
What commands are you using? And what files are you trying to flash?
Sent from my HTC Rezound using Xparent Skyblue Tapatalk 2
I can help you with Ecliptic, which should have just been a simple reboot to hboot after rom flash and then normal reboot. What exactly is occurring? Are you getting "mainver is older" error?
I've tried flashing both hboot_7230ddr2_Runnymede_1.28.0006_20120424 and supermisc - and at this point, I believe the partition tables are borked. I currently have amonra for the recovery, and now when I try and install zip from sdcard it gets all lame and says it cannot mount it. I think what needs to happen first is through ADB I need to find a way to flash a full RUU or something. It used to have 4.03 on it, so I know I'm not far away from success.
oh and at no point has flashboot oem lock ever worked. No Flashboot command has ever responded with anything. I have uninstalled all HTC drivers, removed Sense, and installed just the revolutionary drivers, and they still don't work.
Win 7 x64 -
If the phone boots to hboot fine you should be able to get the ph98img ruu for 605.12 and put that on your SD card and have it reflash your phone. It will fix partition problems as well. Can you try that and report back?
Sent from my ADR6425LVW using Tapatalk 2
@cellularticulate
Going by your info in post #4 it sounds like your trying to flash stuff meant for the Sensation XL. You can't do that, also to add you are s-on and if you try to load an eng hboot you WILL brick.
Run through this PH98IMG RUU in bootloader mode.
http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Snuzzo said:
@cellularticulate
Going by your info in post #4 it sounds like your trying to flash stuff meant for the Sensation XL. You can't do that, also to add you are s-on and if you try to load an eng hboot you WILL brick.
Run through this PH98IMG RUU in bootloader mode.
http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/
Click to expand...
Click to collapse
And make sure you allow the RUU to complete, it will run through twice. It will go to a black screen for several seconds and then it will start over again. Make sure you don't interrupt it. Iirc, it will end up in bootloader when it's done, or maybe it reboots the phone.
It will only run through once, hboot and radio versions will match.
Sent from my ADR6425LVW using Xparent ICS Tapatalk 2
I need to fix the sd card permissions, I think. I will try flashing the RUU. I'm supposed to rename it and place it on my sdcard, and then just boot into hboot? It just...starts...automatically?
cellularticulate said:
I need to fix the sd card permissions, I think. I will try flashing the RUU. I'm supposed to rename it and place it on my sdcard, and then just boot into hboot? It just...starts...automatically?
Click to expand...
Click to collapse
If the ph98img is correct it (hboot) will detect it and prompt you to press up to start the update....
Sent from my Nexus 7 using Tapatalk HD
So I think I just realized why this has been a catastrophic failure this entire time. It's supposed to be on an EXTERNAL sd, right?
cellularticulate said:
So I think I just realized why this has been a catastrophic failure this entire time. It's supposed to be on an EXTERNAL sd, right?
Click to expand...
Click to collapse
Lol...yup...the small things get ya. Good luck finishing it up tonight. Finish ruu, unlock, flash custom recovery (I prefer the ph98img version of recoveries most of the time). Then load whatever ROM you want from recovery -or- continue rooting/setting up the stock ota ROM.
Sent from my Nexus 7 using Tapatalk HD
I still dont know why fastboot never worked :\ But yeah. That's literally all it was. The external SD card vs internal. I wish that was clarified somewhere. But I guess I know this going forward now!
I've got the RUU re-flashed, but I'm still stuck at the ecliptic boot screen. Ill try and do a fix permissions and see if that works.
cellularticulate said:
I've got the RUU re-flashed, but I'm still stuck at the ecliptic boot screen. Ill try and do a fix permissions and see if that works.
Click to expand...
Click to collapse
If you are stuck at the boot screen it's likely you don't have the correct kernel flashed for that rom. Did fastboot ever work for you? If not, do you have a ph98img version of the kernel for ecliptic? Snuzzo will probably chime in here shortly since i think that's his kernel...
I do not have a zip of his kernel, and fastboot still doesn't work. When I try and flash twrp and gives the mainver is old error, and I don't have time to fix this before work. Hopefully someone gives me golden advice and I can get this thing fixed. Three days now :\
Snuzzo, I know you don't do this specifically for money, but I will be donating to you. You've been a huge help.
you as well dottat.
One thing that's strange is I still think my partitions are messed up. I tried using the misctool to write an image to /sdcard2 and no matter what I tried, I couldn't find it. What's strange is when I'm in a shell, it shows this really, really weird login, and keeps kicking me OUT of the shell every couple of minutes. I'm going to try and switch back to TWRP since that what was on this phone when I got it. And yes, the phone was in working condition, things have just inherently gotten worse. http://puu.sh/2XtmZ.png
<3 y'all
OK what status are you at currently and why are you trying to flash that particular partition? Youre getting mainver is older? Hmmmm
You still got the latest twrp on here? If so, flash erez v9 then flash this
http://d-h.st/FZc
That's a dual purpose kernel zip. Do a fresh kernel flash with it. It should also set your mainver properly.
Sent from my Nexus 7 using Tapatalk HD
cellularticulate said:
I do not have a zip of his kernel, and fastboot still doesn't work. When I try and flash twrp and gives the mainver is old error, and I don't have time to fix this before work. Hopefully someone gives me golden advice and I can get this thing fixed. Three days now :\
Snuzzo, I know you don't do this specifically for money, but I will be donating to you. You've been a huge help.
you as well dottat.
One thing that's strange is I still think my partitions are messed up. I tried using the misctool to write an image to /sdcard2 and no matter what I tried, I couldn't find it. What's strange is when I'm in a shell, it shows this really, really weird login, and keeps kicking me OUT of the shell every couple of minutes. I'm going to try and switch back to TWRP since that what was on this phone when I got it. And yes, the phone was in working condition, things have just inherently gotten worse. http://puu.sh/2XtmZ.png
<3 y'all
Click to expand...
Click to collapse
If you let the RUU fun fully and you still have ecliptic boot screen showing you either didn't let the RUU fun fully or something really wonky is going on.. If you let the RUU run fully, you should have a stock rom booting by itself. Can we at least get to that point? We can probably get you around it. .but i would feel better starting from a fresh RUU.
Snuzzo said:
OK what status are you at currently and why are you trying to flash that particular partition? Youre getting mainver is older? Hmmmm
You still got the latest twrp on here? If so, flash erez v9 then flash this
http://d-h.st/FZc
That's a dual purpose kernel zip. Do a fresh kernel flash with it. It should also set your mainver properly.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
@Snuzzo - what's erez v9? tried googling. Didn't see it in the guides on here either.
Yesterday I upgraded my hboot to 2.28. Immediately afterwards, the phone would not get past the HTC white screen (I let it try for 45 minutes).
I can't get into recovery (flashes the HTC white screen, then goes to the green "circle arrows" for about 30 seconds, then to a red triangle with an exclamation mark).
In FASTBOOT, I don't get "fastboot USB" - I get "fastboot AC", and my computer can't see the device.
I'm at the end of my "know-how", and need someone to coach me through this.
Thanks in advance for any help!
dbchristensen said:
Yesterday I upgraded my hboot to 2.28. Immediately afterwards, the phone would not get past the HTC white screen (I let it try for 45 minutes).
I can't get into recovery (flashes the HTC white screen, then goes to the green "circle arrows" for about 30 seconds, then to a red triangle with an exclamation mark).
In FASTBOOT, I don't get "fastboot USB" - I get "fastboot AC", and my computer can't see the device.
I'm at the end of my "know-how", and need someone to coach me through this.
Thanks in advance for any help!
Click to expand...
Click to collapse
you may have grabbed a bad link or you are s-on and flashed improperly....luckily you are only soft bricked....if you'd like its a hassle of a process to gt it fixed but you can send it to me and i can fix and update it properly for you
REV3NT3CH said:
you may have grabbed a bad link or you are s-on and flashed improperly....luckily you are only soft bricked....if you'd like its a hassle of a process to gt it fixed but you can send it to me and i can fix and update it properly for you
Click to expand...
Click to collapse
Thanks for the offer REV3NT3CH. At this point, I'd like to do the process myself and not send the phone off. I don't mind the hassle... just not sure what to try next.
dbchristensen said:
Thanks for the offer REV3NT3CH. At this point, I'd like to do the process myself and not send the phone off. I don't mind the hassle... just not sure what to try next.
Click to expand...
Click to collapse
how familiar with linux are you....and not vmware linux....full install
REV3NT3CH said:
how familiar with linux are you....and not vmware linux....full install
Click to expand...
Click to collapse
Pretty familiar. I run Ubuntu (Mint 15) on my laptop.
dbchristensen said:
Pretty familiar. I run Ubuntu (Mint 15) on my laptop.
Click to expand...
Click to collapse
ok first in windows under device manager...is it showing any weird devices without drivers
REV3NT3CH said:
ok first in windows under device manager...is it showing any weird devices without drivers
Click to expand...
Click to collapse
No. But as I said in the OP, my fastboot (on the phone) shows FASTBOOT AC (not USB)
dbchristensen said:
No. But as I said in the OP, my fastboot (on the phone) shows FASTBOOT AC (not USB)
Click to expand...
Click to collapse
ok let me write a guide for ya
REV3NT3CH said:
ok let me write a guide for ya
Click to expand...
Click to collapse
Thanks so much!
dbchristensen said:
Thanks so much!
Click to expand...
Click to collapse
REV3NT3CH said:
ok let me write a guide for ya
Click to expand...
Click to collapse
REV3NTECH - Good news... I found a PH98 image of ClockworkMod, that gave me access to recovery. From there, was able to flash a ROM. I think I'm good.
Thanks SO much for your willingness to help. You're great!
dbchristensen said:
REV3NTECH - Good news... I found a PH98 image of ClockworkMod, that gave me access to recovery. From there, was able to flash a ROM. I think I'm good.
Thanks SO much for your willingness to help. You're great!
Click to expand...
Click to collapse
oooooh....i was writing a guide cuz i thought it was a more deeply rooted error...im currently writing like 4 guides haha...glad you got it bud
dbchristensen said:
REV3NTECH - Good news... I found a PH98 image of ClockworkMod, that gave me access to recovery. From there, was able to flash a ROM. I think I'm good.
Thanks SO much for your willingness to help. You're great!
Click to expand...
Click to collapse
DHChristensen- I've got just about the same problem. Mine occurred while trying to S-Off with Juopunutbear. I'm stuck on the Juopunutbear logo, no USB connectivity in Fastboot, and no recovery loaded.
Could you let me know where you found a PH98 image of Clockwork mod? I'm hoping I can load it from the HBOOT 2.28 that's currently on the phone.
Thanks in advance,
pilotbob3 said:
DHChristensen- I've got just about the same problem. Mine occurred while trying to S-Off with Juopunutbear. I'm stuck on the Juopunutbear logo, no USB connectivity in Fastboot, and no recovery loaded.
Could you let me know where you found a PH98 image of Clockwork mod? I'm hoping I can load it from the HBOOT 2.28 that's currently on the phone.
Thanks in advance,
Click to expand...
Click to collapse
if yours was caused trying to s-off that wont fix it....when you plug your phone in pc do you get the device QHSUSB_DLOAD. If so this will be your fix http://unlimited.io/qhsusbdload.htm ....read up on their websire...they share possible errors and how to fix when attempting to s-off
REV3NT3CH said:
if yours was caused trying to s-off that wont fix it....when you plug your phone in pc do you get the device QHSUSB_DLOAD. If so this will be your fix http://unlimited.io/qhsusbdload.htm ....read up on their websire...they share possible errors and how to fix when attempting to s-off
Click to expand...
Click to collapse
Thank you for the advice Rev3nt3ch, I don't get the QHSUB_DLOAD device, nothing at all when I connect the phone to the PC. I tried anyway on my Linux PC to run the fix you suggested, it never finds the phone connected.
I went through all the other fixes suggested by the unlimited.io people over a chat session with them, no joy.
So, it looks like I am bricked. All I can do is boot to the HBOOT menu, or let the phone boot up normally, which takes me to the Juopunutbear logo.
Again my thanks for the advice,
pilotbob3 said:
DHChristensen- I've got just about the same problem. Mine occurred while trying to S-Off with Juopunutbear. I'm stuck on the Juopunutbear logo, no USB connectivity in Fastboot, and no recovery loaded.
Could you let me know where you found a PH98 image of Clockwork mod? I'm hoping I can load it from the HBOOT 2.28 that's currently on the phone.
Thanks in advance,
Click to expand...
Click to collapse
Recovery - http://forum.xda-developers.com/showthread.php?t=1914215
Grab CWM_6.0.3.6_Vigor_PH98IMG.zip and rename it.
pilotbob3 said:
Thank you for the advice Rev3nt3ch, I don't get the QHSUB_DLOAD device, nothing at all when I connect the phone to the PC. I tried anyway on my Linux PC to run the fix you suggested, it never finds the phone connected.
I went through all the other fixes suggested by the unlimited.io people over a chat session with them, no joy.
So, it looks like I am bricked. All I can do is boot to the HBOOT menu, or let the phone boot up normally, which takes me to the Juopunutbear logo.
Again my thanks for the advice,
Click to expand...
Click to collapse
if you can still get to hboot you are not bricked...just a soft brick and this can be fixed...try the above posted method...if not you can mail the phone to me and ill fix it for you
I did a little research, Juopunutbear replaces your boot image temporarily, you need to put it back to fix your phone. What rom where you using when you attempted s-off? You need to make a PH98IMG.zip with the kernel (boot.img) from it. It's pretty easy, just need 7zip to update the zip image with the boot.img you were using. If you can't get the phone to communicate with a PC, you will need a card reader though to get the file on your SD Card.
Your other option is to keep trying controlbear and the wire trick til it takes.
mjones73 said:
Recovery - http://forum.xda-developers.com/showthread.php?t=1914215
Grab CWM_6.0.3.6_Vigor_PH98IMG.zip and rename it.
Click to expand...
Click to collapse
Thank you sir for the link. It does try to load, but gives me a Main Version is older message.:crying:
pilotbob3 said:
Thank you sir for the link. It does try to load, but gives me a Main Version is older message.:crying:
Click to expand...
Click to collapse
oooohhh ive seen the fix just scattered somewhere...i'll try to find
mjones73 said:
I did a little research, Juopunutbear replaces your boot image temporarily, you need to put it back to fix your phone. What rom where you using when you attempted s-off? You need to make a PH98IMG.zip with the kernel (boot.img) from it. It's pretty easy, just need 7zip to update the zip image with the boot.img you were using. If you can't get the phone to communicate with a PC, you will need a card reader though to get the file on your SD Card.
Your other option is to keep trying controlbear and the wire trick til it takes.
Click to expand...
Click to collapse
Thank you kindly for the research. I was just running the stock ROM. I've tried restoring the boot.img from a downloaded copy, it appears to load, but doesn't change anything.
Juopunutbear does save the image from the initial attempt in a file calle boot_backup.img. I've renamed it and tried flashing, same thing.
I think my biggest mistake was that I did not load a recovery prior to running Juopunutbear. I just unlocked the device, then went to do the S-Off procedure.