Hello,
Please save me from a child who saw me working on her potentially new tablet and possibly broke it
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip which I assume was a JB upgrade from CW7. TWRP started with the SGT7 file, and simply sat there for 30 minutes on install. It would not move, figured I was stuck - so I hard-powered the device off, booted with the CWM recovery SD card I made using this process (BTW the CW7 and 10 roms and Gapps were on a 2nd SD card), so booted into CWM recovery card, tried to flash SGT7 file that way since it worked so well on the cm-7-TEAM-B-BETA1-signed.zip file from earlier - it says it succeeded, however the gapps failed (indicating BAD - dunno why) but figured I could at least boot the device - I was very wrong.
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
After this mess, as it turns out, I do still have recovery (TWRP 2.1.4 I think is the version) - I tried using it to reinstall the cm-7-TEAM-B-BETA1-signed.zip along with its gapps, but despite a success message, the endless boot problem continues. I tried basically starting over with the guide to reinstall cm-7-TEAM-B-BETA1-signed.zip, but same result, successful install of the zip, but still endless boot loop.
I have 2 questions please:
I have a friend with the exact same device (16gb) - and he has TWRP as well - if I asked him to make a full backup of everything of his, could I then use mine to restore it to my device and possibly get a working unit?
If the answer to the first is NO, can someone point me to a potential means to get out of this so I don't have to wear the dumbass medal of shame in front of my daughter? LOL. Thanks in advance.
funnel71 said:
Hello,
Please save me from a child who saw me working on her potentially new tablet and possibly broke it
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip which I assume was a JB upgrade from CW7. TWRP started with the SGT7 file, and simply sat there for 30 minutes on install. It would not move, figured I was stuck - so I hard-powered the device off, booted with the CWM recovery SD card I made using this process (BTW the CW7 and 10 roms and Gapps were on a 2nd SD card), so booted into CWM recovery card, tried to flash SGT7 file that way since it worked so well on the cm-7-TEAM-B-BETA1-signed.zip file from earlier - it says it succeeded, however the gapps failed (indicating BAD - dunno why) but figured I could at least boot the device - I was very wrong.
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
After this mess, as it turns out, I do still have recovery (TWRP 2.1.4 I think is the version) - I tried using it to reinstall the cm-7-TEAM-B-BETA1-signed.zip along with its gapps, but despite a success message, the endless boot problem continues. I tried basically starting over with the guide to reinstall cm-7-TEAM-B-BETA1-signed.zip, but same result, successful install of the zip, but still endless boot loop.
I have 2 questions please:
I have a friend with the exact same device (16gb) - and he has TWRP as well - if I asked him to make a full backup of everything of his, could I then use mine to restore it to my device and possibly get a working unit?
If the answer to the first is NO, can someone point me to a potential means to get out of this so I don't have to wear the dumbass medal of shame in front of my daughter? LOL. Thanks in advance.
Click to expand...
Click to collapse
I don't know if restoring from backup will help, lets keep that option for later.
If you are able to enter twrp, I suggest you flash a cwm 6 flashable .zip, I think the older twrp had some bugs. I use cwm6.012. Now enter that, and flash only the cm10 Rom, don't worry about gapps now. Then factory reset and reboot device.
Let me know what happens then.
I don't believe it's bricked, its probably a cyanoboot issue. What happens if you hold the n button, then select first option? It looks like device is not finding the Rom, hence rebooting.
Sent from my ST27i
When you say flash a CWM 6 flashable zip I assume you mean CWM recovery, to which I do have recovery on an SD card as well as TWRP internal, and I do believe I did try flashing the 10 back in as you indicated, and even tried flashing the 7 back in as you indicated - it showed success, but left me in the same boot loop. I can certainly try again - unsure what the actual version is on the SD card because I'm not at home to check it, so I'm at the disadvantage, but thank you for reading this and trying to help, very much appreciated - will try again and get back to you.
funnel71 said:
When you say flash a CWM 6 flashable zip I assume you mean CWM recovery, to which I do have recovery on an SD card as well as TWRP internal, and I do believe I did try flashing the 10 back in as you indicated, and even tried flashing the 7 back in as you indicated - it showed success, but left me in the same boot loop. I can certainly try again - unsure what the actual version is on the SD card because I'm not at home to check it, so I'm at the disadvantage, but thank you for reading this and trying to help, very much appreciated - will try again and get back to you.
Click to expand...
Click to collapse
Also, in recovery, go into mounts and storage, mount system partition, then try flashing the Rom.
Do not format anything in mounts and storage.
Sent from my ST27i
OOOO...that's one thing I did NOT try... When I was in recovery, system and sd card were unmounted by default...I mounted the SD card so it would find the ROM zips, but did not mount system, thinking "it will do that on its own when it's ready"...wonder if that was unmounted, why I'd get a success message off of trying to flash the GB zip...oh well, good suggestion, will try asap, ty
funnel71 said:
OOOO...that's one thing I did NOT try... When I was in recovery, system and sd card were unmounted by default...I mounted the SD card so it would find the ROM zips, but did not mount system, thinking "it will do that on its own when it's ready"...wonder if that was unmounted, why I'd get a success message off of trying to flash the GB zip...oh well, good suggestion, will try asap, ty
Click to expand...
Click to collapse
It should mount system by default, but no harm mounting it manually.
Do not mount sdcard, unless it doesn't show the zip files.
Sent from my ST27i
That is why I mounted SD, because it didn't have it mounted, and I could not see anything, especially the zips...OK will try this later today, TYVM.
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
FWIW I had huge problems when trying to use TWRP. It didn't see my sd-card as it should, and I have heard others having similar issues. I didn't try too much, but went on with CWM instead, following the steps I posted here:
http://forum.xda-developers.com/showthread.php?t=2081981
(At one point while struggling with TWRP I messed up bad enough to get into a boot loop. I solved it ny running the repart.img that is mentioned here and there)
I'm sorry, what is that repart img? Is that the "unbrick your nook using ubuntu" thing I saw in dev but can't download? Do you happen to have it somewhere? LOL
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
No, it's not the Ubuntu thing. It's the one in this article:
http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Just wanted to throw this out here from the original post on this thread too.
Dang, But all's not lost, If you can get into TWRP like you say do a full wilpe of everything and try to reflash CM7, If that doesn't get you going I would recommend starting over to insure all is well. It's actually hard to really "brick" a NT and there are many good threads here but I have used this one and it's pretty simple to get you back to factory 1.4.3 http://raywaldo.com/2012/06/how-to-un-brick-a-nook-tablet-8gb-or-16gb/
Lets go from there, I'll be around to help except between 3:30 - 5:30 CST, But will do what ever I can to get ya up & runnin.
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
funnel71 said:
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
Not exactly sure what goin on in there but if you can get to a recovery menu then it's possible to just fact/dalv/cache wipe ect to clean the garbage and try a fresh install. (maybe) but the back up plan is sure to work if that doesn't
funnel71 said:
Thank you kind sir. I've been given a number of ideas, so will be sure to try them. I assume when you say full wipe of everything, you're referring to system, data, and all caches?
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
Click to expand...
Click to collapse
No do not wipe anything in mounts and backup. Formatting the bootdata, factory partition and some of the other partitions WILL brick your device. Only cache partition can be wiped (do factory reset)
Sent from my ST27i
funnel71 said:
...
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2037368
Very well written, and all was going well up until the very last step which was to use TWRP to flash sgt7-10-20121124-UNOFFICIAL-acclaim.zip and gapps-jb-20121011-signed.zip ...
The state I'm in now - endless boot loop. I get the "hold N for menu" boot screen (guess that's cyanoboot), but it will cut off after about 10 seconds and start again. If I hold N, I have 3 lit options (out of about 7 - the other 4 having to do with EMMC are ghosted) - EMMC normal, EMMC recovery, and start fastboot.
...
Click to expand...
Click to collapse
You can either:
Try flashing CM10 again, using a much less circuitous process such as the one described at http://forum.xda-developers.com/showpost.php?p=35669871&postcount=1; or,
Try restoring to stock using the info/tools from https://github.com/succulent/acclaim_recovery_sdcard.
And in case you're tempted to use any of the so-called "unbrick" tools/methods, first read http://forum.xda-developers.com/showpost.php?p=37515697&postcount=31
SUCCESS!!
OK, equipped with 2 SD cards, 2gb for boot into CWM v6012 recovery and 16GB with JB ROM, GAPPS, and updated CWM 6027 recovery for EMMC...
Attempt #1
Booted into CWM SD recovery via PC usb
Swapped SDs to the 16 with the roms and new cwm emmc recovery
Flashed CWM emmc recovery - success (so now twrp that I had should be gone)
Reboot into system and held N to get to cyanoboot menu & selected internal emmc recovery - success, now in CWM 6027 emmc recovery
Selected install zip from sd card (16 still inserted), flashed sgt7-10.1-20130131-0219-acclaim-meghd00t.zip - success
Selected install zip - flashed gapps-sgt7-10.1-20130131-0219-acclaim-meghd00t.zip (I renamed it to match the other, but it's what came with it in the dev post I got it from) - success
Selected to wipe cache, then went to advanced and wiped dalvik cache - success on both.
Hmm, no main menu, it indicates it wiped it, but stayed still at that point, held power button to power off, turned back on, held N to get back into cyanoboot menu just to view its appearance, seemed normal, selected internal EMMC normal..black screen for several seconds, cyanogen loopy design spins (getting a tad happier), will just let this spin for a while... sure beats seeing a bootloop...
5 Minutes later, still getting the loopy design spin, assuming it's unable to boot, did a hard poweroff, removed SD, started again, this time just letting it run, got the cyanogen spin thing again... assuming it will not boot after 5 minutes.
Attempt #2
Repeated the same process as 1, only this time flashed TWRP recovery 2.2.2.0 into EMMC
Using TWRP, flashed the same jb rom and gapps - reboot
Exact same result.
Attempt #3
Decided to change SD cards the ROM and gapps is being loaded from, because I've heard to use a class 4 card, and the 16GB is a class 10 - changed to an old class4 512MB card - repeated the above process - whoa, twrp is gone, but I didn't flash emmc recovery...is that in the ROM perhaps?? Oh well, tried to flash with this older SD card - Ooo, getting farther, the loopy thing changed shape and now is in the center of the screen (slightly excited) - I may have it!!
Going through set up now!! Going to call this portion a success. Other problems should probably be a new thread as this was resolved...
Ultimate cause - too good of an SD card???? Seriously? Oh well, got er done. thanks to all of you for the ideas. They truly helped.
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
Sent from my NookTablet using Tapatalk 2
asawi said:
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
Sent from my NookTablet using Tapatalk 2
Click to expand...
Click to collapse
Point well taken, thanks much. I was backwards
Sent from my ASUS Transformer Pad TF300T using Tapatalk 2
asawi said:
Just noticed something in your description. You should do the wiping before you flash the ROM not after.
...
Click to expand...
Click to collapse
Actually, data/cache/dalvik cache just need to be wiped before first boot of the new ROM.
Of course the order doesn't matter! I really must stop reading the forum (or at least stop writing!) in the middel of the night! (I'm in Sweden). My brain moves slow enough even at it's best... Sorry!
Related
I am trying to fix my recovery partition and am not sure if I did or not. The process that the stock recovery goes through seems awfully short. Here's what it does.
Factory Reset screen
Are you sure?
Clearing Data: (5 - 10 seconds)
n screen (rebooted)
Shouldn't there be a "restoring factory software" screen or something like that?
The main reason i am doing this is so i can unroot. Indirects unrooter app fails partway through and i think this is because of the recovery partition.
old_fart said:
so if the period of time is directly proportional to the size of the data area... then logically its right cause that chunk is 'not' all that big.
Click to expand...
Click to collapse
what?
as to the op, did you flash clockworkmod recovery to your device at one point?
Cubanluke88 said:
what?
as to the op, did you flash clockworkmod recovery to your device at one point?
Click to expand...
Click to collapse
Yes.
Also, I forgot to mention this is an 8gb.
I used indirects app to flash CWM recovery http://forum.xda-developers.com/showthread.php?t=1458630 I didn't realize it was only for 16gb. (in my defense it doesn't say that anywhere in the thread).
Then still not knowing it was for 16gb i used that app to flash it back to stock recovery. Which ,i'm told, put the 16gb recovery on my 8gb nook.
So i followed veronica's instruction http://forum.xda-developers.com/showthread.php?t=1570022 to use adb to fix the partition. It seemed to work properly. Its just that, as i said in the OP, running recovery seems very quick.
My ultimate goal is to unroot, but the unrooter app doesn't work for me (possibly because recovery isn't right) and flashing the BN 1.4.2 zip doesn't work either (possibly because recovery isn't right)
eggwardo said:
Yes.
Also, I forgot to mention this is an 8gb.
I used indirects app to flash CWM recovery http://forum.xda-developers.com/showthread.php?t=1458630 I didn't realize it was only for 16gb. (in my defense it doesn't say that anywhere in the thread).
Then still not knowing it was for 16gb i used that app to flash it back to stock recovery. Which ,i'm told, put the 16gb recovery on my 8gb nook.
So i followed veronica's instruction http://forum.xda-developers.com/showthread.php?t=1570022 to use adb to fix the partition. It seemed to work properly. Its just that, as i said in the OP, running recovery seems very quick.
My ultimate goal is to unroot, but the unrooter app doesn't work for me (possibly because recovery isn't right) and flashing the BN 1.4.2 zip doesn't work either (possibly because recovery isn't right)
Click to expand...
Click to collapse
I'd try 8 failed boots (from off push and continue to hold power until screen is black) on 9th. allow NT to boot and I think you will see different results. This of course assumes you used the 8gig partitions when using veronica's instructions.
Good Luck!
Note: If not positive about which recovery (8 or 16) you used do not do this. Go back and use the 8gig.
One reset only erases data the other invokes recovery and is said to actually return to box-stock.
eggwardo said:
I am trying to fix my recovery partition and am not sure if I did or not. The process that the stock recovery goes through seems awfully short. Here's what it does.
Factory Reset screen
Are you sure?
Clearing Data: (5 - 10 seconds)
n screen (rebooted)
Shouldn't there be a "restoring factory software" screen or something like that?
The main reason i am doing this is so i can unroot. Indirects unrooter app fails partway through and i think this is because of the recovery partition.
Click to expand...
Click to collapse
Once I had time I did both resets and you are right. One only says clearing data and ends, the other says clearing data then restoring factory data and does take longer. Sorry for the delay but I was running CM9 and needed time to set everything up for the testing.
To start, the other day I installed cm9 .04 with cyanoboot w/ twrp. Everythings been fine. Running cm9 mostly until I need something it can't do, then flash cm7 backup. Last night I was using twrp to compress the backups of each. During one of the times (I don't remember which rom I was running) after everything was compressed, wiped, and restored, I began getting the cyanoboot boot loop where when it restarts it goes to the cyanoboot screen and before you can press the n, it runs revovery. I noticed it runs to E9 and the next time shows E0. I tried the dd thing I saw at the end of the cyanoboot thread while in recovery from a booted cwm sdcard. I did it twice. Adb showed it running the process. At the end, I wasn't sure what to do, so once I tried reboot recovery and the next time I tried reboot. Each time it goes to cyanoboot starting recovery.
Any ideas on what to do? Should I flash cwm recovery? If so, then my saved backups are useless. Is there another way to force cyanoboot to run the rom installed on emmc instead of going to recovery?
Thanks ahead of time for any insight.
Sent from my PG06100 using xda premium
there is this utility app on the play store called :
4EXT Recovery Control
https://play.google.com/store/apps/...GwsMSwxLDEwOSwiZXh0LnJlY292ZXJ5LmNvbnRyb2wiXQ..
.
and honestly, i am too stupid to understand if it would or would not be of any help.
old_fart said:
there is this utility app on the play store called :
4EXT Recovery Control
https://play.google.com/store/apps/...GwsMSwxLDEwOSwiZXh0LnJlY292ZXJ5LmNvbnRyb2wiXQ..
.
and honestly, i am too stupid to understand if it would or would not be of any help.
Click to expand...
Click to collapse
Please stop posting entirely unhelpful information. If he can't boot into internal emmc how do you expect him to use this app, even if it is something that could be helpful?
---------- Post added at 01:03 PM ---------- Previous post was at 01:01 PM ----------
@ OP:
Your device is going straight to internal recovery? Perhaps try restoring your backup again? Or flash cm9 fresh?
Also, what do you mean by "compressing" recoveries? I haven't really working with TWRP before, so not sure if this is something unique to it or if you're just using a different term for something I am familiar. with.
I tried several different versions of the backups, both compressed and uncompressed. Tried fresh installs of cm7 and 9. Still nogo. I've been looking at adams ubuntu unbrick. I may try that. I was hoping there might be a quick fix.
Oh. And yes, its boot looping to internal twrp recovery. I can get a cwm recovery sdcard to boot.
Twrp gives you several options in your backups. You can select what parts you want backed up (system, data,etc), md5 or not, and compressed or uncompressed. Compressed takes longer but the size is hella smaller.
I prefer twrp for several reasons: touch ui, more options, file manager and more. But, as stated in the dev thread, its got bugs. Call me hell bent for disaster, but even if I have to flash another recovery or even start fresh from unrooted stock, I'll go back to cyanoboot and twrp.
Sent from my PG06100 using xda premium
ok. i downloaded adamoutlers ubuntu recovery. i ran it by the instructions. when it tried to boot, i got a black screen with some squiggly lines on the volume button side of the screen and then it did the normal bootloop process. before this, i was able to use a boot sdcard and install cwm to emmc. it doesn't have cyanoboot coming up anymore. but i still get the bootloops to recovery. i don't know if the adamoutler download was corrupted. i haven't been able to find an md5 sum for it. i've downloaded it again, and plan on downloading it a third time. i'll then compare the md5 sums of all 3.
i'm beginning to worry that i may have a damaged internal storage.
i also tried albertwertz recovery rom before the ubuntu recovery.
if anyone has more input, i would be grateful.
EDIT:
i ran md5 check sum on all three downloads. all were the same: 97befcb53ee04306c59d24b0ddd26ceb
i presume that's right, or i got three identically screwed up downloads.
if someone would check that i would appreciate it.
i'm about to try aspipatel's windows 7 method. i used it to unroot before.
I tried flashing the Mean Bean rom. I'm not a noob when it comes to flashing, but I made a noob mistake. I just got my phone and forgot to image before I wiped and tried flashing. The rom was stuck at "format /system" for 20 minutes. I held down the power button, and now, since I didn't image the stock, I can't start the phone (it gets stuck at the white screen) and now when I try to install the rom again, the zip is missing.
I have no idea what to do next. I am downloading all of the ruu files and I'm going to run each one until one works, but I'm not sure if that's even going to fix the problem.
Any help would be more than appreciated.
jkoch25 said:
I tried flashing the Mean Bean rom. I'm not a noob when it comes to flashing, but I made a noob mistake. I just got my phone and forgot to image before I wiped and tried flashing. The rom was stuck at "format /system" for 20 minutes. I held down the power button, and now, since I didn't image the stock, I can't start the phone (it gets stuck at the white screen) and now when I try to install the rom again, the zip is missing.
I have no idea what to do next. I am downloading all of the ruu files and I'm going to run each one until one works, but I'm not sure if that's even going to fix the problem.
Any help would be more than appreciated.
Click to expand...
Click to collapse
Try going into recovery then mount SD card in settings put the Rom back then repeat the flash process
Sent from my EVO using xda premium
And all of the RUUs I've downloaded from Shipped-Roms (in the Jewel category) haven't done anything. I keeping "Unknown Error"
Please, I need help.
This happened to me....do what gmoe says.....if the Rom doesn't show up factory reset everything ABSOLUTELY everything and then reboot into recovery it'll tell you there's no os and then mount the usb again drop in the Rom and flash and you should be A okay
Sent from my EVO using xda premium
jkoch25 said:
And all of the RUUs I've downloaded from Shipped-Roms (in the Jewel category) haven't done anything. I keeping "Unknown Error"
Please, I need help.
Click to expand...
Click to collapse
Click the link in my sig you will the RUU you are looking for
Sent from my PoS MoPho
gmoe65 said:
Try going into recovery then mount SD card in settings put the Rom back then repeat the flash process
Sent from my EVO using xda premium
Click to expand...
Click to collapse
Can you expand a little bit? I went into settings and there wasn't anything there to mount. I went into mount and marked "mount SDCard," and I went back to install and nothing popped up. I do have a ROM on my SD card, but its not the same rom. Its a rom I know that works.
EDIT: I noticed it was wanting to use an internal SD card, not an external. Switched it, and bam, works. I'll let you know if it flashes properly. Thank you for the help. This forum is the best, without a doubt. Never lets me down.
jkoch25 said:
Can you expand a little bit? I went into settings and there wasn't anything there to mount. I went into mount and marked "mount SDCard," and I went back to install and nothing popped up. I do have a ROM on my SD card, but its not the same rom. Its a rom I know that works.
EDIT: I noticed it was wanting to use an internal SD card, not an external. Switched it, and bam, works. I'll let you know if it flashes properly. Thank you for the help. This forum is the best, without a doubt. Never lets me down.
Click to expand...
Click to collapse
Np dude :thumbup: just remember if your s-on you have to flash the Kernel first
Sent from my EVO using xda premium
Got it to flash properly. Thank you again everyone, especially gmoe65!
Do you have any data you need or can you do full wipe? if that is possible this is a easy way to flash a ruu. 1 download the ruu from this link http://forum.xda-developers.com/showthread.php?t=1744700&highlight=how+to+root the one that is titled PJ75IMG.zip 2. you will need to put it on your external sd card somehow ( easy way would be taking it out of phone and putting it in a different one then move it using that phone, or mabye using twrp recovery if possible make sure it is the external sd though), make sure you put it on the root of the external sd card. 3. boot into bootloader and the file should be recognized and it will ask you if you want to processed click volume up for yes this will bring you back to stock ics and it will also flash a image to the phone. hope this helps
I have searched and I've found no answers for this. I picked up my phone today and it was unresponsive. I pulled the battery to restart it, would get to the white HTC screen then nothing. Went to recovery TWRP 2.3.2.3 and was greeted with a long list of "E: unable to..." everything. Can't mount system, emmc, data etc. Cannot restore, cannot install, cannot wipe. PH98IMG.zip does not load from sd card. I am pretty sure it's not a formatting issue.
Am I the proud owner of a brick? Any help is appreciated.
I had this problem, I could only fix it by formatting the SD card in the stock rom. If everything is not working and you can't flash the ruu or get in your ROM, you can try factory reset in the bootloader and try a SD card wipe in the ROM after reset to fix the partition. I have only tested fixing the SD mounting issues with stock ROM SD card wiping
That's my idea. Hope I helped :thumbup:
Sent from my ADR6425LVW using xda app-developers app
fastboot flash the latest amon-ra 3.16 recovery and see what happens. Your recovery is outdated.
http://forum.xda-developers.com/showthread.php?t=1339679
To me, sounds like you got the recent OTA while on a custom rom. If you don't mind me asking which one was it?
Snuzzo said:
To me, sounds like you got the recent OTA while on a custom rom. If you don't mind me asking which one was it?
Click to expand...
Click to collapse
I was running Wildstang's CM10.1. Had just updated to the 030513 update about 4 hours before the levy broke. It appeared to operate fine after reboot. Even used the phone to make an audio recording.
Also, for full information, I am on the most recent firmware (HBOOT 2.27 and most recent radios) and full S-Off.
wildstang83 said:
fastboot flash the latest amon-ra 3.16 recovery and see what happens. Your recovery is outdated.
http://forum.xda-developers.com/showthread.php?t=1339679
Click to expand...
Click to collapse
Easier said than done for me, but I will try it out when I get home tonight. Thanks.
It concerns me, though, that the Image CRC in HBOOT comes up as all zeros for Boot, System and Data, and they are not mountable under any circumstances apparently. Any idea why that would happen?
Well let me explain my predicament. The other day I flash somex's something explosive rom after a wipe of the everything I need to wipe ( Data,Cache,Davlik) When it was finished flashing I got to rebooting. I ended up with a blank, yet illuminated screen ( if that makes sense) I waited about 20 minutes. After coming to the conclusion that the ROM doesn't work I did another wupe of everything needed. Then i flashed JoseGalre's ROM since it has aroma it told me that it had an error and coundln't finsih the instalation. I wiped again and reflashed, same error. I wanted to see what would happen if it let it boot up w/o recovery and it ended up in a boot loop. I tried to go back to 4ext and it seemed to load up just fine but half way through the startup it ends up back in the bootloop. I ran Hasoon's all in one kit and flashed TWRP and it worked just fine until I flash a rom. It seemed to be working just fine then it suddenly crashes and we're back in the loop. I've been trying to fix for the last few days but to no avail. I marked the title as urgent because my parents are going out of town for the weekend and I really need a phone. They havn't a clue that it doesn't work becausse they get home before me. Any help would be appreciated a great deal.
I've had something similar happen and freaked out my phone was down for half a day.
Try booting into the boot loader by holding vol down and power boot into recovery, wipe everything then format everything except SD card and try restoring a backup. Hopefully you made one or two in the past.
Sent from my HTC Amaze 4G running Evervolv jellybean 4.3
Illstatic said:
Well let me explain my predicament. The other day I flash somex's something explosive rom after a wipe of the everything I need to wipe ( Data,Cache,Davlik) When it was finished flashing I got to rebooting. I ended up with a blank, yet illuminated screen ( if that makes sense) I waited about 20 minutes. After coming to the conclusion that the ROM doesn't work I did another wupe of everything needed. Then i flashed JoseGalre's ROM since it has aroma it told me that it had an error and coundln't finsih the instalation. I wiped again and reflashed, same error. I wanted to see what would happen if it let it boot up w/o recovery and it ended up in a boot loop. I tried to go back to 4ext and it seemed to load up just fine but half way through the startup it ends up back in the bootloop. I ran Hasoon's all in one kit and flashed TWRP and it worked just fine until I flash a rom. It seemed to be working just fine then it suddenly crashes and we're back in the loop. I've been trying to fix for the last few days but to no avail. I marked the title as urgent because my parents are going out of town for the weekend and I really need a phone. They havn't a clue that it doesn't work becausse they get home before me. Any help would be appreciated a great deal.
Click to expand...
Click to collapse
I don't think you wiped properly. You needed to format ALL PARTITIONS. I can't stress that enough lol.
Edit: Go into bootloader first. Hold volume down then hold power as well. Choose recovery and format all partitions. If that works you're good! :thumbup:
Use the toolkit and flash 4ext. And make sure whenever you flash Roms that you format all partitions.
If that doesn't work you need to flash a RUU, get it back to stock, it will still retain S OF. Then flash 4ext again. Your problems should be fixed for sure if my first method doesn't work.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hey guys it completly out of the question to format my internal storage so keep that in mind
GB or IC RUU and which one?
You don't have to format internal storage just data, cache, system, and boot
Sent from my HTC Amaze 4G running CyanogenMod 10.1
Illstatic said:
Hey guys it completly out of the question to format my internal storage so keep that in mind
GB or IC RUU and which one?
Click to expand...
Click to collapse
Just choose format all partitions.
If you want to use a ruu use the T-Mobile ICS RUU.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So i changed the name of the RUU i download to PH85img.zip and use the all in one tool kit to flash it. The black htc loading screen came up. I waited until it finished and then the bootloader came up with a list of things it head to unzip and then load. After all of that was finished it gave me an error. After reading a message that you should get an error ( i now realize this was at another stage) so i though nothing of it and rebooted. A black screen with 4 warning triangles came up. I let it load all day and when i got home i plugged it back in and I noticed it looked like it was unplugging after securing the charger in I came the conclusion that it wasn't holding a charge and dying on the battery. Normally I would leave it alone but when you plug in the charger it turns itself on. I've began living with the fact that my phone is bricked. But any help would be appreciated.
BTW is there a way to get data (music pictures contacts) that were saved on the internal storage?
Probably should have gone with full caps on the PH85IMG.zip
It's easier just to put the zip on your external sdcard and gone in to bootloader.
Sent from my HTC_Amaze_4G using xda app-developers app
chevycowboyusa said:
Probably should have gone with full caps on the PH85IMG.zip
It's easier just to put the zip on your external sdcard and gone in to bootloader.
Sent from my HTC_Amaze_4G using xda app-developers app
Click to expand...
Click to collapse
So is there anything that I can do when I plug it in it wont boot or charge at all so am i truly bricked or is there still hope
Illstatic said:
So is there anything that I can do when I plug it in it wont boot or charge at all so am i truly bricked or is there still hope
Click to expand...
Click to collapse
Should be hope, check out the unbricking project...
http://forum.xda-developers.com/showthread.php?t=1627882:cowboy: