Related
Hi, I've had lot's of problems with my HTC recently, no adb access etc, device not being recognised and recovery playing up, ie not being able to wipe install roms etc... however I fixed the recovery issue and managed to do a nandroid backup, I put on I think it was 1.5 HTC sense hero rom... and recently realised that i can only flash 1.5 roms, not 2.1 anymore? would any developer know what would of caused this problem? Any 2.1 rom just locks on the Hero logo, and I've left it for over an hour in some cases and nothing happens. Again, I used to be able to put on any custom rom.... I'm all out of ideas.
wipe
did you wipe? what recovery image you using etc etc?
1. post in the correct section.
2. remove the ext4 partition from your sdcard, or change it to ext2 or ext3.
3. get adb logcat, otherwise this is like the question "my car won't run, can anybody tell me why?"
I have wiped numerous times... sorry for the "my car won't run type question etc...." just that I've done my research, gooogled, posted detailed info previously on here and another forum, I even fixed my own problem of the recovery image, without fixing that I would have nothing. But anyway the card is partitioned with swap, ext2, fat32 using the latest Amon_Ra image 1.6? something... i've spent weeks trying to resolve this and learnt a lot along the way.
Obviously not where to find the adb logcat... don't worry I'll google it.
Apologies for posting in the wrong forum, if it can be moved could a mod do so?
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Thanks for your reply, I will approach this method again at some point and give it a try, but I think I read somewhere that I couldn't do it for whatever reason, but I'll look into it again seeing as you've had the same issues. Thanks.
bonesy said:
i had this problem with my magic,Using the goldcard method to downgrade and starting from scratch will fix this
Click to expand...
Click to collapse
Actually I believe I didnt attempt this because I was no longer able to get my HTC hero working with ADB, as soon as I plug the device in, it comes up as device unrecognised, so I think goldcard method it out.. :-(
on the risk of offending you again (even though i am trying to help here...): you did not provide really much valid info. for most things you just said "doesn't work". what happens if you start by pushing home+power? saying the recovery doesn't boot up tells what does NOT happen, for a diagnosis we need the info what DOES happen.
anyway, if i get you right your recovery is now working. now repartition your sdcard (ext2 and fat, NO swap), do a full wipe, then install the rom you desire to use, then move the log to sdcard ("other" in recovery). reboot your phone and execute "adb logcat > c:\logcat.txt" on your pc. if it doesn't boot up after five minutes stop logcat with ctrl-c and post the two logfiles (recovery.log and logcat.txt). you need to set up adb, if you have problems with that sort them out, there is no way to get any information about your problem without the log.
oh, and about the goldcard: i don't know too much about goldcard'ing, but i can't see how this should help here. my strongest guess is that the swap partition interferes with the boot process...
No worries no offence taken. Pushing Home+Power works and takes me to recovery. Back+Power takes me to bootloader and USB Bootloader device is recognised, so I am able to get Fastboot.
Just recently installed stock rom, to see if that solved the USB and ROM issues but no such luck, re-rooted, put anom latest recovery back on, and went on to do what you have advised to help.. i've attached only the recovery.log in zip format only, as when doing adb logcat command use mentioned(after installing new rom), all I get is "waiting for devices" whilst the phone is stuck on the Hero logo, I waited about 10 minutes, exited from the adb, and the log file was empty as I guessed. I've tried every possible way that I found on the web to try and get the ADB function working again and I realise this is important to get some info.. but I've ran out of ideas for that.
Maybe the recovery(attached) may show something, all I noticed is that the cache and something else was not wiped for some reason? If you or someone has time, have a look through maybe someone knows what is going on.
Thanks for your help and patience
Tuesday night I loaded CM7, and then the Market wouldn't update my apps so I decided I would restore BAMF 1.5. After doing so, the Market just gave me "Fails" trying to update, and I could not access recovery, as I was going to do a complete wipe and reflash. Most of Wednesday, an extremely helpful & knowledgable member, Mattgyver83, tried diligently to help me rectify the situation, but to no avail. We tried to Fastboot, tried flash_image, tried fix permissions...shoot, I practically wore out adb..anyway, I ended up reverting back to stock and unrooted. I used jcase's method to revert back to stock, and that was painless, and successful. I decided last night to try rooting again, thinking a fresh root would solve my issue of not being able to access recovery. Root was successful, but I still cannot access recovery, through rom manager, or through bootloader. When I attempt it my Tbolt goes to white HTC screen, and stays there. All functions of my phone now work, and all aspects of root work, except I cannot flash anything. Rom manager shows I have clockwork recovery, but I just can't get to it.
Sorry for the long ramble. If anyone has had this issue, or if anyone knows a fix, I would appreciate it. Otherwise, I wait for Gingerbread.
Thanks
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
travishamockery said:
Happened to me with CM7 builds. For some reason they were erasing the recovery. Just have to reflash the recovery in Rom Manager and you'll be all set in the future.
Click to expand...
Click to collapse
Tried that, but thanks. Still just goes to white HTC screen, and stays there until I do battery pull.
jr4000watts said:
do what i do pull batt leave out for a min, then put the batt back in and connect usb right away.
Click to expand...
Click to collapse
I can get to bootloader, just not able to get into recovery.
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
monolithic said:
I'm stabbing in the dark at this, but this did work for me with my Droid...
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Ie. Flash recovery and wait until the confirmation pop-up/message only takes a few seconds to pop up. If the message takes longer than 5 seconds or so, re-flash recovery and repeat until the confirmation comes up quickly.
This sounded retarded to me, but I was at the end of my rope so I tried it. It worked like a charm.
M.
Click to expand...
Click to collapse
Thanks, but that didn't work. I think something in my os got lost when I restored BAMF from CM7.
Yea I spent a good few hours yesterday trying to help Orio out and we attempted a ton of things to try and fix the recovery issue, this post should offer a bit more insight to the methods used, this is running off memory;
adb reboot recovery failed
Reinstall latest Rom Manager apk and Flash CWM
flash latest rom manager via fastboot (CWM only)
(fastboot flash recovery /sdcard/recovery-clockwork-3.0.2.5.img)
**did not do fastboot erase recovery first**
"return to stock safely and properly" XDAthread by jcase
return to stock image [RUU], reroot, try again
try to boot into recovery via hboot
manually installed fix_permissions.sh script and busybox on rooted stock, ran.. didnt fix
tried to see if flash_image method would work, didn't
All of the above have failed and we basically tried almost all combinations. Not once would this phone get back into recovery, even after flashing the appropriate RUUs which include either stock android or CWM recovery. The only thing we have not currently attempted which might be the last thing left is to do is manually install the nandroid.sh script and do an advanced restore of the recovery image only from a nandroid backup on SD. I would rather not go down this method as it could have an undesired result, I have done it to restore a G1 back in the day but not 100% if its gonna work on a tbolt. Thankfully his phone boots, and we can get into hboot, but yea.. pretend recovery just doesnt exist at all...
Curious if anyone has any knowledge above what we have already tried.
monolithic said:
I had a similar issue with my Droid. Someone recommended that I flash recovery multiple times before trying to reboot. The comments were basically that you need to flash recovery 3-5x until the flashing process is a mere few short seconds. Evidently that is an indication that the flash has occurred correctly.
Click to expand...
Click to collapse
I recall the same thing and its a good thought however that was mostly a generic error due to a CWM update and CM6 (I think) but either way flashing an RUU should override this shortcoming and im pretty sure that issue was worked out in CWM as well.
Not to be rude, but I don't think this question belongs in the development section.
Orio56 said:
I can get to bootloader, just not able to get into recovery.
Click to expand...
Click to collapse
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
hogowner said:
do you still have the P zip file for the radio (baseband) on your SD card? if you do....try to delete it...then hold power and volume down button down....then see if you can get into recovery....
probably not going to work...but it is worth a try......
Click to expand...
Click to collapse
Thanks, but no, I deleted that after loading it. I actually reverted back to stock/unrooted last night and rerooted and the problem still remains. It's quite strange.
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
shelooga said:
maybe i missed it if someone suggested this but what about flashing an older version of CWM?
Click to expand...
Click to collapse
That is what I was going to suggest. In ROM Manager at the very bottom try and flash an older version.
Sent from my ADR6400L using XDA Premium App
SUCCESS !!!
I fixed it !
Apparently, when I loaded up cm7, files showed up about the same time on my sdcard in clockworkmod download file. I deleted those files, and reflashed clockworkmod in rom manager, (which this time took like 3 - 4 minutes), and rebooted into recovery and it worked...did it again, just in case it was a fluke and it worked.
All is well now...the planets are realigned !!!
Thanks everyone for your ideas and especially thanks to mattgyver83 who helped me for something like 4 hours yesterday. Exceptional kindness !!
mods...you can close this thread.
GREAT NEWS!!!! CONGRATULATIONS!!
THANKS FOR REPORTING BACK!
This may help out other members with the same problem!!
now go ahead and start playing with your T-BOLT again!
That's a very odd solution. My first two things to try would have been:
1) fastboot:
fastboot erase recovery
fastboot flash recovery C:\some\local\path\recovery.img
You can't, well, probably shouldn't, flash a recovery from the /sdcard. When in fastboot mode I don't think the sdcard is even mounted. Either way, I think fastboot needs the img file on the local file system.
2) Create a PG05IMG.zip file with the recovery.img file in it, and flash that through HBOOT. Although this should have been done in some form or fashion when you downgraded or re-rooted, so YMMV.
Daughter handed me her phone today and said it "turned off and would not turn back on"... I could use some help figuring out what went wrong and how to fix it. I have flashed many roms, built a few from source, installed recoveries, rooted devices, etc. Though not a complete noob, I do have no formal training on this stuff and consider myself a novice compared to many here at XDA.
The phone was unlocked and rooted using Hasoon2000's HTC Rezound All In One Tool Kit about 1 month ago...
The rom that was fully functional for the past month, until today, is Liquidsmooth JB v2.9 Official vigor. It has worked exceptionally for her, until today. AT this point, if you pull the battery and then put it back in - it will boot to a white HTC screen for a few seconds and then go BSOD indefinitely. The only way to get any action after that is to pull the battery and try again... You can use the power & volume down to get into fastboot (if I pull out the external sd card) or into recovery (if I leave the external sd card in place).
Here's what the status on the fastboot screen shows:
*** TAMPERED ***
*** UNLOCKED ***
VIGOR PVT SHIP S-ON RL
HBOOT-2.28.0000
RADIO-2.23.10.0123r/2.23.10.0124r
OpenDSP-v14.6.0.7708.00.0507
eMMC-boot
Here's where I'm stuck at trying to get it back up and running - I do not think it is hard bricked:
1) I can boot into recovery and was able to open TWRP 2.5.0.0 and move around in it. However, it seemed to be saying there is no internal memory on the phone (cant mount or open) cache, data, system, sdcard (internal), NO ROM. I can not wipe any of the above partitions or format either...but it does see everything on the external sd card, though you can't flash anything to the internal sdcard or system, etc... Therefore, I decided to try another recovery, so...
2) Eventually I figured out how to fastboot flash a new recovery (after lots of reading here on several forums) and managed to get CWM Touch v6.0.3.6 Installed... it also does not see the system, cache, data, sdcard (internal)... but it does see my external sd card, as did TWRP. Again, no flashing to internal memory or formatting of the aforementioned partitions...
3) I have tried to fastboot flash boot.img from the aforementioned rom - fastboot flash boot boot.img - which appears to work, yet there is no change in status after rebooting or pulling the battery. Same problems exist...
4) I have tried fastboot flashing the RUU - fastboot flash ruu radio.img - appeared to do something, but still no change in status...
5) I have tried fastboot flashing the system image - fastboot flash img Liquid.zip (I changed the name of the file in an act of desperation trying various methods I read about online) - appeared to do something, but still no change in status...
6) If I boot into recovery, ADB can see the device and shows it in recovery mode. I have tried to ADB INSTALL the rom and boot.img - no luck there either (though I could be doing something wrong)...
7) If I boot into recovery, my windows 8 computer sees the external sd card of the device if I mount it as a USB MASS STORAGE device, but does not see the internal sdcard.
8) I have tried using Hasoon2000's tool to do various things and had no luck with making any more progress than using fastboot or adb.
9) I have tried to fastboot boot several different recoveries, but could not get any of them to boot up... though the process looked like it was working and rebooted - and just stuck at the white HTC screen...
I have been hacking away at this phone for about 7 hours now, reading forums, trying many things (some of which are listed above), and I've run out of ideas...
If anyone has any experience with this situation and knows of a positive solution that does not involve me flushing this thing down the toilet, I'd be really appreciative of your detailed advice. Though I have some basic experience, I can get lost quickly if you skip the details in any suggested solutions.
I appreciate any help or advice you may have to offer. I'm not thinking it's bricked - I just don't know enough to have the solution and have been reading for hours... getting a bit delirious at this point.
Thanks for you time...
It honestly sounds like some partitions are corrupt or damaged. Try using amon ra and see if it can see the internal partitions, if it can, format ext3 then ext4. Fstrim can corrupt the partition and amon ra can fix that.
If that doesn't work, you might be SOL as there is no full ruu for global OTA at the moment which may be your last resort. If you are on the recent OTA, which by your hboot, sound like it, you'd need S-off to RUU.
Sent from my Infected Rezound using xda app-developers app
Its deffinately not bricked...being able to boot to bootloader is a good thing...But as Uzephi said your best bet is to S-Off to make any further progress...that way it makes it easier to do things...fstrim especially used by LagFix app has caused this error in the past and what Uzephi said i will second to...in recovery you can try converting from ext4 to ext3 and back to ext4 and try wiping the internal within the recovery and that may fix it...if it doesnt there is a few fastboot and adb command tricks for formatting...however with s-off downgrading or upgrading the ruu is possible which may fix it also...i ran into this error once actually shortly after i modded my rezound the first time while it still only had sense...luckily i s-offed and was able to throw a few tricks at it
Guys, THANK YOU both for throwing some ideas at me... I will try as you both suggested and give an update once I'm done.
I will see if I can figure out how to s-off this thing... Then,
I will fastboot flash amonra and see if I can reformat internal with it.
If neither work, I will research adb and fastboot reformatting the internal memory.
Thanks again... This give me some more things to work on today. I will keep you posted.
Sent from my GT-I9505G using xda premium
still stuck...
So, I have spent the better part of my day working on this phone and still no luck...
From what I can tell reading various posts through the forums, I can't do the s-off thing without having the stock ruu installed... (If I'm understanding things correctly, which it is entirely possible I'm missing something obvious here...) I also run Ubuntu 12.04 on my computer in a 64bit virtualbox environment (windows 8 64 bit is my native os)- which 64 bit virtual Ubuntu seems to not be compatible with doing s-off.
I also can't get amon ra to install via fastboot flash or fastboot boot - again, entirely possible I'm missing something obvious.
I have gone over and over flashing and re-flashing twrp and cwm, trying various things to no avail... After being up late last night working on this and up early this morning, I'm officially throwing in the towel (for now). I'm really tired and a bit frustrated.
Of the dozen or so android devices that my family owns, I have rooted every one of them and installed roms, built a few fully functional roms from source, installed recoveries, etc... I have never run in to such a thing.
I still don't think it's bricked, but I'm feeling like the fix is above my head. If anyone thinks of something that I might be able to try, I will check back in a little later today. I need to get some work done around the house right now.
Thanks again for your help.
dandroid7 said:
So, I have spent the better part of my day working on this phone and still no luck...
From what I can tell reading various posts through the forums, I can't do the s-off thing without having the stock ruu installed... (If I'm understanding things correctly, which it is entirely possible I'm missing something obvious here...) I also run Ubuntu 12.04 on my computer in a 64bit virtualbox environment (windows 8 64 bit is my native os)- which 64 bit virtual Ubuntu seems to not be compatible with doing s-off.
I also can't get amon ra to install via fastboot flash or fastboot boot - again, entirely possible I'm missing something obvious.
I have gone over and over flashing and re-flashing twrp and cwm, trying various things to no avail... After being up late last night working on this and up early this morning, I'm officially throwing in the towel (for now). I'm really tired and a bit frustrated.
Of the dozen or so android devices that my family owns, I have rooted every one of them and installed roms, built a few fully functional roms from source, installed recoveries, etc... I have never run in to such a thing.
I still don't think it's bricked, but I'm feeling like the fix is above my head. If anyone thinks of something that I might be able to try, I will check back in a little later today. I need to get some work done around the house right now.
Thanks again for your help.
Click to expand...
Click to collapse
you can s-off straight from windows...i was actually able to do it on windows 7 64 bit. you can still find the latest ruu and flash it via a ph98 img file Hasoons toolkit has the appropriate files for the s-off tools...besides just flashing twrp did you use any of the format/convert/ or wipe sd card methods within them...also amon ra does have a ph98 img you can install through the bootloader itself....if worst comes to worst you can always send it to someone who can....not saying verizon but someone like me.who has done this before.
REV3NT3CH said:
you can s-off straight from windows...i was actually able to do it on windows 7 64 bit. you can still find the latest ruu and flash it via a ph98 img file Hasoons toolkit has the appropriate files for the s-off tools...besides just flashing twrp did you use any of the format/convert/ or wipe sd card methods within them...also amon ra does have a ph98 img you can install through the bootloader itself....if worst comes to worst you can always send it to someone who can....not saying verizon but someone like me.who has done this before.
Click to expand...
Click to collapse
I have an old beater pc that has windows 7 32 bit on it... I can try it from there. Am I supposed to just run s-off as juopuntubears instructions, eventhough I would be using a windows pc? Actually, I may still have a dual boot of Ubuntu 12.04 running on that machine... I'll have to take a look at it and see.
As for the latest RUU - I have downloaded "global_ota_radio_PH98IMG" that I found off the xda forums and it said it is the latest radio. I have tried to fastboot flash it and also to flash it through hasoons aiotk, neither seemed to get me functional. I also put it at the root of my sdcard, and though it appeared to be doing something when I boot into fastboot, I still have the same issues as I started with (nothing showing up on the internal memory). The version of Hasoons toolkit that I have does not appear to have any s-off features. I will have to look at older versions, I recall seeing something somewhere on xda with that feature.
As for TWRP and CWM, since they can't mount the internal partitions - they don't format or convert anything - since they fail to mount them.
I have also tried to install amon ra through the bootloader, to no avail.
I'm going to research the aiotk with s-off tools as well as check out my old pc to see if I can s-off through win7 or my dualboot Ubuntu (if it is still there)...
I do appreciate you helping point me in the right direction.
dandroid7 said:
I have an old beater pc that has windows 7 32 bit on it... I can try it from there. Am I supposed to just run s-off as juopuntubears instructions, eventhough I would be using a windows pc? Actually, I may still have a dual boot of Ubuntu 12.04 running on that machine... I'll have to take a look at it and see.
As for the latest RUU - I have downloaded "global_ota_radio_PH98IMG" that I found off the xda forums and it said it is the latest radio. I have tried to fastboot flash it and also to flash it through hasoons aiotk, neither seemed to get me functional. I also put it at the root of my sdcard, and though it appeared to be doing something when I boot into fastboot, I still have the same issues as I started with (nothing showing up on the internal memory). The version of Hasoons toolkit that I have does not appear to have any s-off features. I will have to look at older versions, I recall seeing something somewhere on xda with that feature.
As for TWRP and CWM, since they can't mount the internal partitions - they don't format or convert anything - since they fail to mount them.
I have also tried to install amon ra through the bootloader, to no avail.
I'm going to research the aiotk with s-off tools as well as check out my old pc to see if I can s-off through win7 or my dualboot Ubuntu (if it is still there)...
I do appreciate you helping point me in the right direction.
Click to expand...
Click to collapse
juopuntubears s-off method is meant for windows...for the latest ruu all you need to do is make sure it looks like PH98IMG.zip and place it to the root of your external sd card then run in bootloader and it will go through the process of install from there. I havent seen the other all in one kit in action but juopuntubears method is what i used....im pretty sure its somethjing very simple but i would load the ruu first n see where we go from there....my guess is your internal sd card was either in the middle of a reformat and was interrupted or if lagfix was used it caused the error or files were improperly deleted or the possibility of someone trying an s-off method on the s-on device....ive gotten the tampered message before and that usually means a improper hboot flash method was used
I have no clue what would have caused this issue, but my 13 year old daughter uses the phone as a WiFi only android device for Facebook, instagram, pinterest, etc... It is not even hooked up to a phone provider. She was sitting on the couch using it, her brothers were nearby using their tablets... One minute its working, the next minute it turns off...
The only thing I can think of is that I had installed goomanager when I unlocked, rooted it, and flashed a recovery and ROM. I'm wondering if she may have gotten a notice of an update for her rom or gapps through goomanager and let it start the update process without knowing what was going on... If she stopped it in the process of an update, I could see this happening somehow... I don't use goomanager much, so I'm not even sure if what I'm saying is possible?
I have a long week ahead of me with work... Not sure how much I will get to this until next weekend. Hopefully I can give it a bit of time in the evenings... But I have some extra training to do this week...
Thanks again. I will update this thread once I have taken additional steps. I do really appreciate your help.
Sent from my GT-I9505G using xda premium
dandroid7 said:
I have no clue what would have caused this issue, but my 13 year old daughter uses the phone as a WiFi only android device for Facebook, instagram, pinterest, etc... It is not even hooked up to a phone provider. She was sitting on the couch using it, her brothers were nearby using their tablets... One minute its working, the next minute it turns off...
The only thing I can think of is that I had installed goomanager when I unlocked, rooted it, and flashed a recovery and ROM. I'm wondering if she may have gotten a notice of an update for her rom or gapps through goomanager and let it start the update process without knowing what was going on... If she stopped it in the process of an update, I could see this happening somehow... I don't use goomanager much, so I'm not even sure if what I'm saying is possible?
I have a long week ahead of me with work... Not sure how much I will get to this until next weekend. Hopefully I can give it a bit of time in the evenings... But I have some extra training to do this week...
Thanks again. I will update this thread once I have taken additional steps. I do really appreciate your help.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Ya that may of done it...it is a possibility....again if all else fails someone can work on it for you....me personally id do it for you free of charge and you can trust me...i hate seeing people without and to be honest mine was completely hard bricked to no return and Neo has done me a great deed of help so im passing along the karma...but by the sounds of it yours isnt hard bricked which i know is fixable
10-4... I may take you up on your offer at some point THANK YOU for the kind offer.
I'm pretty stubborn... I may figure this out yet. S-off seems like my next conquest to overcome. Fortunately this isn't my work phone or anything, so im less stressed about having an immediate fix. My daughter will survive without it...
As well, I still don't feel like its hard bricked, so I know there is a solution out there to resurrect it from the dead. I just have to learn how to do it. That's what I love about android and the community of great people out there to learn from.
My line of work is construction management... But I'm an android ninja in training at home These android challenges cause me to learn and grow in new ways. Critical thinking, logic, problem analysis... Its all part of learning android. I enjoy the challenge and opportunity to learn from people like yourself who are willing to teach people like me, who would otherwise have no way to learn a thing like android.
Thanks again. Time to crash for the night....
Sent from my GT-I9505G using xda premium
dandroid7 said:
10-4... I may take you up on your offer at some point THANK YOU for the kind offer.
I'm pretty stubborn... I may figure this out yet. S-off seems like my next conquest to overcome. Fortunately this isn't my work phone or anything, so im less stressed about having an immediate fix. My daughter will survive without it...
As well, I still don't feel like its hard bricked, so I know there is a solution out there to resurrect it from the dead. I just have to learn how to do it. That's what I love about android and the community of great people out there to learn from.
My line of work is construction management... But I'm an android ninja in training at home These android challenges cause me to learn and grow in new ways. Critical thinking, logic, problem analysis... Its all part of learning android. I enjoy the challenge and opportunity to learn from people like yourself who are willing to teach people like me, who would otherwise have no way to learn a thing like android.
Thanks again. Time to crash for the night....
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
well your internal memory is borked but phone isnt bricked...hard bricked is when your phone wont even boot to the bootloader but reads as a certain different device in device manager...ill look into many other ways to fix this for you and i do hear you on being stubborn...im the same way when it comes to this sorta stuff and push myself to learn more....great devs learn and come from that same influence and drive to do so
Can you restore your partitions? Or can you not because you can't format them? If you can't, I suggest just flashing a stock RUU from you bootloader, being very careful though, you don't wanna get bricked. From there you can just flash your recovery and restore what you can, hopefully. Do you want a link to the RUU?
Sent from my ADR6425LVW running EclipticRezRavampedV9 (Lunar Kernel) using xda app-developers app.
Because I'm s-on right now, I don't believe I can flash an ruu, can I? I'm pretty sure I can't go backwards to an earlier ruu being s-on. Also I thought I read there is not a full ruu available of the current one I have on the phone. I could be wrong to all of the above, but I thought I read this somewhere recently.
I have been reading about s-off, but have not had time to do it. I also am unclear if it is even possible to do s-off in the current state the phone is in.
I can't format because it won't mount any internal partitions. I dont know how to restore a partition... But if the internal memory won't mount, I'm not sure if a restore would work.
I'm willing to try stuff, just not today... Had a reeeaaally long day. If you want to send me a link for an ruu or have any other ideas, I am interested in getting past this issue. But it may not be until this weekend that I have time to get back to it.
Thanks.
Sent from my GT-I9505G using xda premium
dandroid7 said:
Because I'm s-on right now, I don't believe I can flash an ruu, can I? I'm pretty sure I can't go backwards to an earlier ruu being s-on. Also I thought I read there is not a full ruu available of the current one I have on the phone. I could be wrong to all of the above, but I thought I read this somewhere recently.
I have been reading about s-off, but have not had time to do it. I also am unclear if it is even possible to do s-off in the current state the phone is in.
I can't format because it won't mount any internal partitions. I dont know how to restore a partition... But if the internal memory won't mount, I'm not sure if a restore would work.
I'm willing to try stuff, just not today... Had a reeeaaally long day. If you want to send me a link for an ruu or have any other ideas, I am interested in getting past this issue. But it may not be until this weekend that I have time to get back to it.
Thanks.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
if your on hboot 2.28 that is the most recent up to date leaked radios...however the most up to date full ruu comes with 2.27...if you are s-off its kind of hard...a user posted in the threads earlier that he completely removed his external card and his windows was able to detect the 2 internal partitions...and he formatted the 10.5 gb fartition and worked flawless...if all else fails...how well do you know about using linux and or a linux based rescue disk for partitions
Holy cow - its alive!!!
THANKS to everyone who has been helping point me in the right direction.
I'm now close to functional again... bootlooping at the splash screen for a rom is much better than no internal partitions on the device...
I relocked the bootloader using hasoon2000s all in one kit...
After doing much research, I was finally able to flash a PH98IMG file that someone had posted here on the xda forum that was here (said it works for S-on):
http://forum.xda-developers.com/showthread.php?t=2250494
http://d-h.st/BIj - had to rename the file to PH98IMG and flash from sd card in bootloader/hboot.
Once I did that, I unlocked the phone again using hasoon2000s all in one kit, then installed amon ra recovery.
I flashed a new rom via amon ra recovery.
I then fastboot flash boot boot.img that I pulled from the new rom
I now see paritions on the internal memory when I'm in recovery, and the splash screen of the new rom is bootlooping... I'm soooo close to being functional again.
I'll let you know when I get passed the bootloop...
dandroid7 said:
THANKS to everyone who has been helping point me in the right direction.
I'm now close to functional again... bootlooping at the splash screen for a rom is much better than no internal partitions on the device...
I relocked the bootloader using hasoon2000s all in one kit...
After doing much research, I was finally able to flash a PH98IMG file that someone had posted here on the xda forum that was here (said it works for S-on):
http://forum.xda-developers.com/showthread.php?t=2250494
http://d-h.st/BIj - had to rename the file to PH98IMG and flash from sd card in bootloader/hboot.
Once I did that, I unlocked the phone again using hasoon2000s all in one kit, then installed amon ra recovery.
I flashed a new rom via amon ra recovery.
I then fastboot flash boot boot.img that I pulled from the new rom
I now see paritions on the internal memory when I'm in recovery, and the splash screen of the new rom is bootlooping... I'm soooo close to being functional again.
I'll let you know when I get passed the bootloop...
Click to expand...
Click to collapse
Use CWM or TWRP for flashing. Amon ra is known to have flashing/wiping issues. And did you clean wipe? Even though you have RUU you still need to wipe.
Sent from my Infected Rezound using xda app-developers app
Thanks for the info... I never used amon ra before, I read about it being buggy.
I actually wiped everything, repartitioned it, then flashed ROM with amon ra, then fastboot flashed boot image.
I have to get up a 4am... So I'm calling it quits for tonight. I have another long day tomorrow... I'm feeling like I'm in the home stretch now. Tomorrow I will switch back to twrp 2.6 or cwm touch 6 and see what happens. I will do a full wipe, flash ROM, then fastboot flash the boot image.
Fingers crossed...
Thanks again. I'm always learning here on xda and other android forums. I really appreciate your kindness in pointing me in the right direction and giving me ideas of things to try. I did a ton of reading to get this one figured out as far as I have, though I'm still not done yet.
I will touch base again once I do the things above.
Sent from my GT-I9505G using xda premium
dandroid7 said:
Thanks for the info... I never used amon ra before, I red about it being buggy.
I actually wiped everything, repartitioned it, then flashed ROM with am on ra, the fastboot flashed boot image.
I have to get up a 4am... So I'm calling it quits for tonight. I have another long day tomorrow... I'm feeling like I'm in the home stretch now. Tomorrow I will switch back to twrp 2.6 or cwm touch 6 and see what happens. I will do a full wipe, flash ROM, then fastboot flash the boot image.
Fingers crossed...
Thanks again. I'm always learning here on xda and other android forums. I really appreciate your kindness in pointing me in the right direction and giving me ideas of things to try. I did a ton of reading to get this one figured out as far as I have, though I'm still not done yet.
I will touch base again once I do the things above.
Sent from my GT-I9505G using xda premium
Click to expand...
Click to collapse
Hey i may have found a fix...another user had the same issue and fixed it by using TWRP and wiping emmc first. Once he did that he wiped the internal sd card. Should then work... Format afterwards just to be safe.
K good to know. Have a great night... I will give it a rip tomorrow... I'm pretty stoked to have gotten this far today.
Sent from my GT-I9505G using xda premium
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
OnlyEYEShine said:
Good afternoon, !!!
First and foremost , I want to thank you all in advance for ANY and help, time & consideration with my current issue. I will try my best to be clear, and give all relevant info here in my first post. Please bear with me, I am pretty good when it comes to following directions, but i havent been able to find a CLEAR solution to this yet, and worried about further screwing up my phone.
** I use a mac. I currently dont have access to a PC, so i am looking for a mac remedy if possible.
I have an HTCONE m7. Tmobile.
- Bootloader - Unlocked
- S- ON
- Rooted
I kept getting a OTA software update notice for 5.14xxx, i understand the install kept failing due to the bootloader being unlocked and/or root. So after being annoyed for not able to get it, i began googling ways to get the update but to no avail. So i decided to do CM11, & recovery which i installed with no problem via, Cyanogenmod Installer.
After doing so, i realized i lost my Tmobile Wifi Calling (Yes, my own fault for not further checking that scenario before doing cm11), The wifi calling is needed 10000%, due to bad service in my apartment. Prior to finding out that cm11 doesnt contain the tmobile wifi calling , I attempted another system update thru the phone, (I assume it was updating cm11).
This is where the problem began, phone rebooted to Cyanogenmod simple recovery ,
1st few times that i tried = "apply update" > choose from internal storage , i searched different folders for the "update" file, but to no avail. The phone wouldnt start up, or install anything , and will just stay on the simple recovery. I even attempted an adb sideload. But couldnt figure that out correctly either.
After a few failed attempts, I tried wiping the phone, cache, factory reset etc. now the phone still stays on simple recovery, and all folders are gone, except for an o/ folder, that contains a clockworkmod folder, which contains nothing.
So now basically,Do i have to eventually get back to STOCK on this phone, to regain tmobile wifi calling ? IF So i need the easiest, mac friendly route to go .
Again, i thank you ALLLLL in advance, & my apologies if this is in the wrong section. Please note ive done my fair share of googling , and reading up on this. But consistently run into a problem.
Click to expand...
Click to collapse
What's the radio version that is installed? Should be viewable on the bootloader screen at the top. That will help determine which RUU you need to get back to running again.
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe
If it matches the numbers/letters after the Radio_ part there, then that is the file you need. Let me know, and I can download it for you and extract the rom.zip from the exe and upload that. Then you can use fastboot commands to install it on the phone. If your radio version does not match that, please post and we'll see if there are other options.
I don't believe that flashing another rom would work right now since all the storage and such got wiped, but it might be possible to use adb while in recovery to push a rom to the internal storage and install it and then use fastboot to install the boot.img from the rom in bootloader mode since you are S-On.
es0tericcha0s said:
What's the radio version that is installed? Should be viewable on the bootloader screen at the top. That will help determine which RUU you need to get back to running again.
http://www.androidruu.com/getdownlo...50.20_10.40.1150.04_release_324846_signed.exe
If it matches the numbers/letters after the Radio_ part there, then that is the file you need. Let me know, and I can download it for you and extract the rom.zip from the exe and upload that. Then you can use fastboot commands to install it on the phone. If your radio version does not match that, please post and we'll see if there are other options.
I don't believe that flashing another rom would work right now since all the storage and such got wiped, but it might be possible to use adb while in recovery to push a rom to the internal storage and install it and then use fastboot to install the boot.img from the rom in bootloader mode since you are S-On.
Click to expand...
Click to collapse
Hey there , i ended up making a 2nd thread, in the HTCONE section.. I am currently trying a fix that someone just posted. http://forum.xda-developers.com/htc...date-issue-t2898480/post55889272#post55889272 I will try your fix next, if this does not work =0) Thanks again !! DEFINETLY APPRECIATE IT !!
IF mod can close this thread to avoid confusion, it would be appreciated.