[Q] Help with Eris and Evil Eris - Droid Eris Q&A, Help & Troubleshooting

I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen

jbergen said:
I'm having a little trouble and I'm sincerely hoping you'll help. I've tried flashing my Eris using the file, "Evil_Tazz_3.zip" and my Eris is now bricked and stuck in a bootloop. All it will do is show an animation of the sketchy letters ANDROID falling down the screen and then a smoky light following close behind it reveling the Droid itself. And it'll repeat this animation rapidly about 100 times before freezing and then restarting the whole process all over. To be frank it pisses me off because it always seems that I'm the only one who has trouble with this stuff.
My Eris is rooted and it does allow me to access the recovery screen. What am I supposed to do?
Anyways, thanks for your time.
Best Regards -Joseph Bergen
Click to expand...
Click to collapse
Whatever you do, DO NOT DO ANYTHING ELSE UNTIL BTFB0 responds to your plea for help.
Do not just start trying different solutions, DO NOT FLASH ANY RUU, if you know what that is. BTFB0 is the guy who can get your phone unbricked if anyone can. He is the expert, I won't pretend to be able to duplicate his knowledge in this area.
Be patient until he has a chance to see this. You don't have to PM him, I'm sure he'll respond when he has a chance here in public. He will ask specific questions about what version of bootloader you have, 1.47 or 1.49, and you might as well find out if it's S=OFF or S=ON.
Also, do you have Amon RA recovery on your phone and can you get to it?

Have you tried flashing anything else since your phone has gotten stuck in this boot loop? If not and you can get into recovery still, then simply wipe data, wipe dalvik, and try flashing again. Don't worry you're phone doesn't sound bricked, just like you got a bad download or an error when flashing the rom. I would probably try a different rom or at least re-download the one you want to use.
It may still be wise to wait for BTFB0 to get here and offer some more advice as I am sure he has more knowledge in this area than me. But I do feel confident that he will say the same thing as I have.

Well, the OP merely said that he is having trouble with a specific ROM; he didn't mention failures during flashing; so, his problem could be as simple as having failed to "wipe" before flashing his ROM.
jbergen:
If you can boot into a custom recovery, your phone is not "bricked". It's not even soft-bricked; it's just not booting into the main OS correctly.
Providing as much detail as you can is helpful to people that are offering help to you; in particular, the following pieces of information:
- What recovery is on your phone? (Amon_RA, Clockwork? What version #?)
- When you are flashing the ROM file with your recovery, do you notice any "E:" messages?
An "E:" at the beginning of a line on the screen means that an error occurred!
- Are you having this same trouble on more than one ROM, or is this the only ROM you have tried since you rooted?
- What method did you use to root the phone?
- Did you use the "Wipe data/factory reset" menu item before you flashed the ROM file?
- Did you make any Nandroid backups that you still have on your SD card? If yes, did you attempt to restore one? What was the result? (BTW, every rooted phone user should be making Nandroid backups before they flash ROMs - no exceptions.)
- Do you have a media card slot or USB card reader device that will allow you to copy a different ROM file onto your SD card? -OR-
- Do you know how to "mount" the SD card onto the PC when your recovery is booted? (On Amon_RA, it is called "Toggle MS-USB" or something like that; it's also in the Clockwork menu somewhere too)
Given the information you have provided, there are any number of things that could be going on. I would suggest downloading a different ROM to your PC (let's say the stock HTC Eris March 2011 ROM), and then transferring it to your SD card. Then,
- Verify the exact size of the file and/or MD5 signatures of the file (if the developer provided it).
- make sure your phone is well charged
- perform a "Wipe data/factory reset" from the recovery menu
- Flash the ROM file from the recovery menu - and pay attention to the screen to see if there are any `E:' errors
- If there are errors, there is no point in attempting to boot the phone
- If there are no errors, boot the phone.
- Report your results here - and answer the questions that I asked.

Related

No longer able to update to custom 2.1 roms??

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

I cannot access recovery anymore

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.

[Q] Noob Issues

Yes I am new to rooting droids, but I am not illiterate in this subject. However, I am pregnant, and over emotional and possibly losing my mind because I can't get my phone to work. (Sounds like a noob issue right?!)
I have a droid 2, latest update, blahblah.
I rooted it, no problem, got good instructions from here, downloaded ROM manager, and Bootstrap. I downloaded Liquid Dream ROM. Flashed Clockwork, and rebooted. ROM seemed to download onto the device fine, finished rebooting and now it plays the Liquid Dream animation on start up over and over. Currently I am in reboot mode but I am stuck, I don't know where to go from here (because I am a noob, I know). So I'm hope full that someone with a lot more knowledge on this can help me out, so I don't totally lose my mind. Thanks for your time future person who helps me! (I hope)
did you wipe all the data/cache and davlik prior to installing a new rom. When ever changing roms, you need to clear out the old data.
go into fastboot, clear data/cache and under advance clear dalvik.
try that.
ChelseaLynn__ said:
Yes I am new to rooting droids, but I am not illiterate in this subject. However, I am pregnant, and over emotional and possibly losing my mind because I can't get my phone to work. (Sounds like a noob issue right?!)
I have a droid 2, latest update, blahblah.
I rooted it, no problem, got good instructions from here, downloaded ROM manager, and Bootstrap. I downloaded Liquid Dream ROM. Flashed Clockwork, and rebooted. ROM seemed to download onto the device fine, finished rebooting and now it plays the Liquid Dream animation on start up over and over. Currently I am in reboot mode but I am stuck, I don't know where to go from here (because I am a noob, I know). So I'm hope full that someone with a lot more knowledge on this can help me out, so I don't totally lose my mind. Thanks for your time future person who helps me! (I hope)
Click to expand...
Click to collapse
Well, something probably didnĀ“t upload ok. So, what you have to do know is: make sure the .zip file in the sdcard is not corrupted. In order to make sure of that, you can try to download it again (you will need an sdcard reader). Then, when you have already the .zip file in the sdcard, boot into recovery. From boot loop the best way is to boot the phone pressing power + volumen down, then choose recovery from the hboot menu. Once you are in the CWM recovery menu, do a wipe data / factory reset. wipe cache partion and format system.
When that is done, you are able to flash the zip file from install .zip from sdcard choice. That should work and get your cell back to life.
It might be Clockwork. There have been some issues with it. If none of the above suggestions work, try getting Amon Ra.
If ClockWorkMod does not work you can try flashing the 4EXT recovery...works smoothly at least in my Inspire 4G.

[Q] Unexpected Brick

About a month ago I rooted a HTC EVO 4G LTE, installed the recovery with touch screen and Cyanogenmod nighties.
It worked great, including tethering on Sprint.
Last week an update to latest Cyanogenmod was made. Phone worked normally, until today when screen stopped responding completely (physical buttons were working), including after rebooting. On a second reboot phone was stuck on a boot loop.
Went into bootloader mode and tried to go to recovery. It would boot loop again. Noted that it said UNLOCKED S-ON (I thought it was supposed to be S-OFF). I tried flashing the boot.img from latest Cyanogenmod. Nothing. Tried reseting from the menu. Tried more things. Nothing worked. So I downloaded and used the latest version of RUU after fastboot oem lock. RUU was successful (no error, phone no longer displays HTC developer message), however it's still stuck on the boot loop. I thought RUU would restore it completely.
What am I missing?
Read here
http://forum.xda-developers.com/showthread.php?t=2084633
And here
http://forum.xda-developers.com/showthread.php?t=2097150
#Root-Hack_Mod*Always=SG3
I followed the instructions.
Then I tried all RUU that I had and always got Error 140.
Finally, found in a rooting pack RUU_JEWEL_CL_JB_45_S_Sprint_WWE_3.15.651.16_Radio_1.12.11.1119_NV_2.87_003_25007_release_299302_signed.exe which worked to restore.
However, the phone is still in the same state. What do I do?
How long did you give the phone to boot.? Also did you flash the firmware zip after you relocked your boot loader?
#Root-Hack_Mod*Always=SG3
Phone is RELOCKED.
What I did:
Code:
fastboot oem rebootRUU
fastboot erase cache
fastboot flash zip jewel_jb_ota_firmware.zip
Then used that RUU to restore. After this I left the phone without touching it for about ten minutes, but it keeps restarting (never passes booting stage).
Try this. Remove your sd. Then back up all your data. Then format it threw your PC and return it to factory defaults. Then put it back in your phone and redo the steps. Also were did you get the ruu your using from ?? Also if that fails to work look here
http://forum.xda-developers.com/showthread.php?t=2045935
And try the firmware zip with the stock recovery. Then run the ruu. Hope this helps.
#Root-Hack_Mod*Always=SG3
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Same result after trying without SD card. Also I did flashboot flash zip
Code:
PJ75IMG_3.15.651.6-firmware.zip
from the link you provided without help.
PepeJones said:
Does it matter if the SD is in?
So, I took out the SD card, repeated those three steps and I should use RUU again.
The RUU is from 3.15_RUU_PLUS_ROOT.zip.
I'm going to try again now with no SD.
Click to expand...
Click to collapse
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
laie1472 said:
Yes the sd card should be in your phone. Also your trying to go back to stock so using the ruu that's stock with root might be the issue given your phones current state. I'll try and find you just the stock ruu with no root, unless you have one or if you know were one is download it and run it. Also when I posted about the SD card you were only supposed to remove it to "back up your data" and then "format" it. After you have formatted it then place it back into your phone. I'm not aware of any potential issues with running a ruu without the SD card being in the phone, however I would strongly suggest always running the ruu with the SD in the phone. Its what I've always done. Also make sure that your battery is over 75%. And did you flash the one with the stock recovery? There are several firmware zips on that thread but the one with the stock recovery is the one I suggested you try. And I'm not sure what the "without help" post is about. I'll help you as much as I can and I'm sure if I don't reply to you right away that there are more than enough knowledgeable members in this forum to help you as well. Take in mind that phones are so easy to screw up but it might take some time to get it back up and running. But troubleshooting is all part of the process.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
PepeJones said:
I'll try it again with the SD card in the phone. No, the RUU I'm using it's in a pack for rooting and updating. I don't think it's modified at all. I don't even think RUU can be altered and signed anyway. I'll search for another RUU again.
Yes, the one that I flashed is
Code:
PJ75IMG - Firmware zip with hBoot and stock recovery (signature intact)
http://d-h.st/sKO (MD5: 0d8f9d65e29c1c824654bf88b9438f15)
and I had enough battery. (It was supposed to be without luck not without help).
So, I'll flash the above mentioned PJ75IMG, then use the RUU (I'll search for one that's in no pack, but I'm confident it's not altered) - all this with the SD card inside.
Thanks for your help.
Click to expand...
Click to collapse
You can't flash a PJ75IMG.zip unless you are S-OFF and the file you posted above is not an RUU it's just the updated firmware
It didn't work.
So I followed the steps from this link.
After using HTCDev to unlock the phone and I try to open RabiesShot, it reboots the phone but it's not able to connect. Sometimes the phone goes in a loop, sometimes the phone boots (it did boot twice). However, even when it booted, the screen didn't work at all, which is the original problem.
Right now the phone is ON but the only thing that works is the power and volume buttons (screen and soft buttons do not work). I've also noticed the phone reboots alone.
Any ideas left?
(This is my friend's phone. Anyway, I'll convince anyone to stay away from HTC. Nexus is so much better than this...)
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
laie1472 said:
Its not the phone its the user. I've never heard of a phone hacking itself. So usually the fault is the owner of the device and not the device itself. And In this case I'd say its user error. Also I'm lost as in what your doing at the moment. I thought you were trying to go back to stock? Now you post says your basically trying to obtain s-off. If this is the case then you make it extremely difficult to try and pin point what's actually the issue with your firends phone because you jump methods. So at this point exactly what are you trying to do ? Are you trying to go back to stock to gain s-off ?? Also if you come here to receive help with your issue you should always try the posted methods first so the member that's helping you is aware of what steps your taking and what your going to do. If not then it becomes difficult to help you.
#Root-Hack_Mod*Always=SG3
Click to expand...
Click to collapse
Not hacked itself, just not working. At least, that's what I've been told. Right now I'm trying to make it stock, but since what you proposed didn't work I tried different things such as obtaining S-OFF (no success).
The comment regarding HTC wasn't necessarily related to this case but in general. Just look how miserably is the process to just obtain root and unlock the bootloader. And in many cases is not even possible until some exploit is found. Why...? HTC used to be great.
I'm just trying to get this phone work again. Initial idea was to go stock, since it seems logical that it should be straight forward.
So I tried everything you have posted, including the last instructions you left me (backup everything off SD, deleted everything and inserted SD in the phone, then repeated the process).
Thanks for your help.
I understand your frustration about the issues with the phone in its current state. However if done correctly gaining root/s-off can be achieved in less that an hour. I do realize the fact that even if guides are followed to the exact directions that issues still occur. But that's the risk you take when you modify you phone. Your aware of this I'm sure. However that's why xda is a great website. Not only can you get the software to modify your phone, you can also get help in case the process didn't go the way it should have. You can't dispute the fact that there are more than a few members with the evo-lte who had no problems at all with gaining root or s-off. As far as the steps I suggested there was no guarantee that they would work its just the process of trouble shooting to see what will work. If you don't mind can you post the exacts steps you took before you tried to achieve s-off ? Also can you post the links to the exact ruu and firmware you last used as well.? Also if the phone is on try powering it down and attempt to boot into the boot loader. If your successful then try factory reset.
#Root-Hack_Mod*Always=SG3

[Q] Encryption prevents custom ROMs being used

OK so let me start off with, great site. I have read a ton of information.
First: Siyah 4.3.3 (Latest) Kernel which now has been put to AJK v1.48s
ROM; SHOstock3 v2.5.9
PreMod Settings: SGS2 AT&T SGH-i777. Started with GB > AT&T OTA (KIES) 4.0.3 > AT&T OTA WIFI 4.0.4 (caused huge freaking headaches with battery, charging, turn off the phone loop, battery draining, etc.)
Issues:
Original Issue posted in this thread (viewing Single Post) http://forum.xda-developers.com/showpost.php?p=39350619&postcount=18
Creepy offered something to try. That never worked as all I was able to do was download mode or stare at the Samsung Galaxy S2 Splash Screen. Well, I took to his download repository and other links and used his One-Click Recovery to stock GB Rom to make part of my phone usable, using this link here: http://forum.xda-developers.com/showpost.php?p=18859438&postcount=199
While it is Gingerbread at least my phone is usable. I want to try his STOCK ICS method but that mentions the eMMC super-brick bug.
So this is what I have tried so far. I have tried installing Siyah 4.3.3 nomswap for my kernel using Mobil-Odin Lite. That works but it never reboots or actually says finished. What it does do is stay at the wicked purple splash with the yin yang symbol. I left it like that last night until I woke up this morning and it never changed. So I rebooted the phone and the Kernel is on there. I reboot into recovery so that I can install SHOstock3 v2.5.9. That goes off flawlessly except here the last few times it won't reboot when I go to the GO BACK. It sticks and doesn't do anything. Rebooting shows the SHOstock3 Engine Boot Animation. Once it stops it goes to ask me for the encryption password. Well I put in my password (was the same one to the unlock screen) and it reboots and you see the nifty Samsung animation logo and then goes to the Samsung Galaxy S2 Animation Logo and then just stays there. It really pisses me off.
So after all that I finally put a new Kernel on there,AJK 1,48s. Pretty cool it loads up and then reboots. Well AJK shows up after the light-blue bar fills up and then goes black and the 4 touch sensitive row keys are lit up for a bit before going dark but the phone is still on. So I rebooted to recovery (CWM now with the Kernel) fixed tweaks, went to advanced and saw all sorts of options. Tried clearing caches for ROM 2 and restarting,no effect. I removed ROM 2 and went through reboot and nothing. Restored ROM 2 and nothing. Re installed SHOstock3 v2.5.9. Did the same thing after install and not backing out when I hit GO BACK. Rebooted, same scenario that happened before with requiring password. Entering password does the same thing with a reboot and then staying on Samsung Splash Screen. If I Don't enter the password and reboot,same thing happens. So after being irritated and pissed off I ran Creepy's One-Click Fix again and paid attention to the phone and noticed it mentioned not being able to access the AT&T section or partition or something like that. So while part of my phone works under normal circumstances I want to figure out how to remove that encryption part of the phone and get full access (even though full memory and space are shown under Windows 7 and the files on the phone). The password I put on there isn't taking and I don't know if using PC methods for removing encryption (which could take awhile I know) needs to be employed (and if so which methods) or if that part is just screwed and I can't put on any other kernels or custom ROMs. Perhaps tell me where I messed up. Should I try swapping the ROMs from Advanced setting in CWM Recovery? Can I try a different ROM (kernel didn't seem to help)? I have done several factory resets dalvik cache wipes cache wipes formats,etc. and it is still there. I can say that before the whole encryption debacle (even though I was encrypted I did get in my phone after encrypting it) my pin unlock for my SIM wouldn't work and I actually SIM locked my phone. Had to go to AT&T and get a new SIM and was up and running. I put a 4 digit pin lock for the SIM (it let me do it) and when I went to unlock it after a reboot, it wanted an 8 pin for the PUK and wouldn't take what I put. I tried to change the PIN but to no avail. Once that happened I guess it snowballed. Any help is appreciated. I have searched and tried some things that looked to match my issue but none have totally helped. I do have ADB set up on my wife's laptop which I use to restore my phone to GB Stock ROM. I haven't been able to reboot the phone into Bootloader to do any fastboot commands as when I tried to do it the commands just sent the phone into normal reboot (though adb reboot recovery does boot to recovery). I Haven't tried booting to the bootloader using the new Kernel though so I will wait for confirmation or additional information before I try. Thanks guys.
Eagle
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Thank you so much creepy. I will give that a try later and see how it goes. I hope the information I gave actually gives enough info. I know folks usually want enough. Ill post back my findings.
Eagle
quick follow up and what I tried
creepyncrawly said:
Couple of comments. Siyah 4.3.3 (and ajk) kernels are for 4.x ICS and JB so that explains why your stock Gingerbread system would not flash after you installed it. If you flash back to stock Gingerbread again, and then flash a custom kernel, use a kernel that is compatible with Gingerbread if you want to boot the system.
After doing a little research, it seems that a wipe data/factory reset will not clear the encryption, but a format data will. This information is not from a Samsung forum; it's from the Droid DNA forum. I'm thinking that the same thing may apply to the I777. See the thread here.
It might be worth a try anyway. Flash stock plus root Gingerbread, install mobile odin or mobile odin lite, and use it to flash Siyah 2.6.14. Boot into recovery and go to the Mounts and Storage section. There you can format data, (and all the other partitions, separately.)
Click to expand...
Click to collapse
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
WarEagleUS said:
Hey Creepy, I have a quick follow up and want to tell you what I have tried.
So I had already used Kies to move to AT&T v 4.0.4 ICS on my phone when I read your post. Rather than flashback again to GB I went ahead and put Siyah 4.3.3 on my phone. Went great, rebooted and installed quick and everything. Well I rebooted into recovery and went to mounts and storage and formatted the data and all that there and even formatted the secondrom data and all that. Did it a couple times to make sure everything was clean and good to go. Even put AJKs kernel on there after I ran the cleanrom script and it went flawlessly. I did factory resets and wipes and all that and installed SHOstock3 v2.5.9 and started up great. Well it got past the animation and the damn Password for encryption popped up. Well I put the wrong password in and it rebooted without the SAMSUNG screen and went through the boot ani and back to the password for encryption screen. I put the right password in, it reboots and you see the Samsung logo flash quickly and then it sticks on the Samsung Galaxy S2 Splash screen. I don't know what is holding it up from going forward unless when I messed up the first go around and it deleted everything if it didn't take out the bootload command or what have you. So I don't know if this idea will work but I am going to flashback to GB and put the siyah version on there that you linked and see if that will work.
One tihng, when Iencrypted the device the first go round, I onlydid the used data and area not the whole thing. Is this affecting it somehow? Any other ideas to try? I figured a full data format would remove the encryption but it never pops up saying all encryption will be removed. What I need is access to that area of the phone if I could just mount it on the computer. Is it possible after formatting the data, or before, that I should mount internal USB, DATA, etc and try another format/wipe or at least mount them to see if they can be used? Thanks for the help. For anyone else viewing this post (which actually is a lot) any help or ideas are appreciated. I am thinking I may need to format everything and get ahold of Samsung to see if they will reset my phone for me. I just wonder if the PIN lock on my SIM card that got locked when it wouldn't take my PIN didn't mess something up as well.
Eagle
Click to expand...
Click to collapse
Should I try TWRP instead of CWM and if so where should I grab it from?
Status Update
So this is what I have tried so far as of this moment.
I reflashed using your Stock + Root Gingerbread ROM.
Wiped DATA and everything in recovery menu several times.
Used Kernel Wipe and ROM Nuke for extra cleaning power.
Reinstalled the Kernel AJK and SHOstock3 ROM
Haven't installed any themes though I had Johns Blue and Villians Poison Base Theme (I believe that is what it is) on there when this all went down. Should I put them back on there?
Password still pops up. So what it looks like is that unless I stick with the unencrypted portion of the phone, I am screwed with any custom ROMs as the correct password has the phone restart and then stick at the Samsung Galaxy S2 Splash Screen. Apparently I still cannot access that area of the phones memory to wipe it at all no matter what I do. I need to access it somehow. Really driving me crazy and thinking I may need to talk with AT&T(as Samsung told me to earlier this morning lol) and see what they can do.
One thing I do notice is when I use your stock root program it actually removes the encryption or decrypts the section of the phone for the stock ROM to go on the phone which is cool.
Eagle
Any other things to try from anyone is greatly appreciated.
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
WarEagleUS said:
would restoring my original EFS before this whole process help or is the encryption section totally blocked off?
Click to expand...
Click to collapse
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
creepyncrawly said:
Been away all day. Sorry, I can't offer any other suggestions, but I have no experience with encryption. As you said, what you need to know is where the encryption is stored in memory so you can wipe or format that and restore it to original. If you can get to the right person, probably not level 1 tech support, then maybe you can find out. Somebody somewhere knows the answer to this.
Click to expand...
Click to collapse
Thx bro. yeah I need to run some forensic tools and see if I can mount the whole phone system on my PC and run the tools.
creepyncrawly said:
I have no idea whether the encryption is stored there. What kind of efs backup did you take?
Click to expand...
Click to collapse
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
WarEagleUS said:
a full efs backup. I made two or three actuakky using advanced efs, nitrality, and recovery.
Click to expand...
Click to collapse
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
creepyncrawly said:
A little research indicates that there is quite a bit of stuff stored in efs besides carrier specific data. So maybe encryption could be in there. Of those tools, nitrality for sure and maybe advanced efs should be able to restore the entire efs partition. If you are comfortable with the risk - a damaged efs would render the phone useless - then you might try this to see if it clears up the encryption issue. BTW, you should learn how to back up the efs partition yourself using terminal and linux commands.
Click to expand...
Click to collapse
Yeah I should have used ADB to do that from the get go. I should have used the wife's laptop like I started to instead of my WIN 8 machine has it seems to be finicky with Android SDK (the portion at least needed to run ADB). Linux commands really aren't much different than terminal and I have done both. I was actually trying to get fastboot commands to work but my bootloader wasn't cooperating and for the life of me I couldn't find how to unlock it. I may try restoring that EFS. If nothing else I would love to be able to format that EFS and replace it with my original copy though as you said a damaged EFS may actually cause issues (who knows if it is damaged). I do know that I am fixing to chat with AT&T support. I hope I don't have to drive down to Hoover, AL to the repair facility. I would rather them send me a phone and send this one back. I am on stock 4.0.4 ICS from AT&T and any root that may be on there (though I doubt there is now) I can remove and what not
Thanks for the advice and insight Creepy. I know you tried like hell to get me an answer but in doing research on here with other problems I found out some useful information going forward my friend.
Eagle
Well, looks like I will be getting a special early upgrade and the wife will as well. I will be keeping this phone, however, to mess with this and see if I cannot get this problem fixed. Thanks Creepy so much. I appreciate your research and help more than you know. If possible I would love to keep this thread open for a while just in case I figure this out and fix the issue. It may take me a week or so but I will get back to messing with it again.
A side note. You don't need the whole sdk to get adb. You can download just the files you need from my signature.
Sent from my SGH-I777 using xda premium

Categories

Resources