So i rooted my phone using HTC amaze All in one tool kit by hasoon and everything was going smooth until i tried to change fonts using font installer, nothing happened so i got on aptoide and downloaded ROM toolbox pro and used its font changer, which i think use the same font changing program , and changed my fonts, again nothing happened. i started messing(by messing around i mean typing and looking for new keys on the keyboard) around trying to figure out what went wrong and my phone froze. i shut down my phone and when i rebooted i couldn't get past the android 4g t-mobile screen. can anyone help?
EDIT-i can still get to bootloader or that menu you get when you hold power and down volume. in my panic to fix my phone i restored to factory setting but that, i believe, only made it worse as now i couldn't mount my sdcard. when i saw i couldnt do that i looked it up and found a post that said to format my sdcard and so in a desperate attempt to save my phone i did, not stopping to think that it would erase everything on it. i do have a back up of everything that was on my phone prior to this.
Just restore a nandroid, like most people would do, and you'll be good. If all else fails then you'll need to flash a Rom and if that doesn't work for you then you'll need to flash an RUU. Read the Amaze Bible if you're stuck.
Double0EK said:
Just restore a nandroid, like most people would do, and you'll be good. If all else fails then you'll need to flash a Rom and if that doesn't work for you then you'll need to flash an RUU. Read the Amaze Bible if you're stuck.
Click to expand...
Click to collapse
i cant figure this out to save my life. if you could point me to a video, or add me on skype to walk me through it, you have no idea how much id appreciat it
Double0EK said:
Just restore a nandroid, like most people would do, and you'll be good. If all else fails then you'll need to flash a Rom and if that doesn't work for you then you'll need to flash an RUU. Read the Amaze Bible if you're stuck.
Click to expand...
Click to collapse
He formatted his SD card. Isn't that were the backup is placed?
if you can get to your bootloader check to see if you can get to your recovery, if you cannot get to ur recover go back to the bootloader to FASTBOOT and use the toolkit to flash 4EXT recovery then proceed to try and factory reset your phone, or check your system file settings or repartition your sd card, you can use 4EXT's mount usb feature to connect your phone to the PC while your phone is in recovery to place a ROM on your SD card
IlHEROlI said:
So i rooted my phone using HTC amaze All in one tool kit by hasoon and everything was going smooth until i tried to change fonts using font installer, nothing happened so i got on aptoide and downloaded ROM toolbox pro and used its font changer, which i think use the same font changing program , and changed my fonts, again nothing happened. i started messing(by messing around i mean typing and looking for new keys on the keyboard) around trying to figure out what went wrong and my phone froze. i shut down my phone and when i rebooted i couldn't get past the android 4g t-mobile screen. can anyone help?
EDIT-i can still get to bootloader or that menu you get when you hold power and down volume. in my panic to fix my phone i restored to factory setting but that, i believe, only made it worse as now i couldn't mount my sdcard. when i saw i couldnt do that i looked it up and found a post that said to format my sdcard and so in a desperate attempt to save my phone i did, not stopping to think that it would erase everything on it. i do have a back up of everything that was on my phone prior to this.
Click to expand...
Click to collapse
try my guide if u have a custom recovery http://forum.xda-developers.com/showthread.php?t=2024800
Related
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
babybear293 said:
i have the evo 3d and flashed some roms and alwats did back ups but tried the miui rom and now usb does not work at all...tried restoring or flashing other roms that were already on my usb cant do commands cuz usb doesnt work can someone please help
Click to expand...
Click to collapse
can't do commands via usb, i'm reading this to mean, you don't have adb access.
after wiping the /data partition, where system settings are stored, including the toggle for adb access via, you will probably have to re-enable.
to enable adb access via usb on sense -> settings -> applications -> development -> usb debugging. this should be toggle on.
if that doesn't work, post back and we can start digging deeper but i'm hoping that'll resolve your isse!
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
thos25 said:
I apologize in advance for being lengthy, but I want to be thorough to give you a good idea of what I did. Hopefully someone will point out what I did right or wrong.
I had this same exact problem with MIUI the other day. I am not an expert on rooting/flashing, but I was able to resolve the issue with a little trial and error.
I flashed MIUI on my 3d. I wasnt too impressed with it really and flashed back to Eternity. A few days passed and I decided to give MIUI another shot and flashed back a second time. Mind you, I always do a factory reset twice, wipe cache twice, and wipe dalvik cache twice before any flash (even if it is an updated version of the ROM I am using), so I made sure to wipe everything before flashing. When I flashed I noticed the little bug on the notification bar area of MIUI and thought it was a clever way of showing debug mode was on.
After messing with it some more I realized that I just plain didnt like it and giving it any more time was not neccessary. I decided to flash back to Eternity. I booted up my phone into bootloader and tried to get into fastboot USB, but it wouldnt activate when I put my USB in. I rebooted into MIUI to make sure I didn't mistakenly turn debugging off. It was still on. I tried to get into fastboot USB a second time. Still an error. I searched XDA came across this thread. Noted that USB debug was on. Followed steps, no progress.
At this point I figured I would just try to flash eternity to see what happened without using fastboot. Froze on bootup. So I flashed MIUI back on. I then remembered hearing about Flash Image GUI on market (made by JoeyKrim who posted above me in this thread). I figured I would give it a shot.
Failed. I had Ziggy kernel from Eternity already on my SD, so I flashed that. It said it was successful. So I powered down. Then I booted into bootloader and went into recovery. I tried to flash Eternity and it froze during boot. I tried to boot up several times and always froze. I went back to MIUI figuring that perhaps the kernel really didnt flash. MIUI made it past boot, to the lockscreen, but I couldnt unlock it. Bascially I was stuck. None of the buttons worked except for power. I tried again to reboot MIUI again. Same problem.
Starting to get a bit desperate, and not being able to get into fastboot USB at all, I figured I could try to nand restore to stock rooted. Of course...still wont work since I couldnt access fastboot USB. My screen froze during boot on this as well.
So here I am stuck with no fastboot USB, a restore that wont flash, Eternity wont flash, and MIUI isnt responding. Honestly I was getting upset and had half a mind to hit the phone with a stun gun and take it to Sprint. (not my idea, but a Sprint person told me once to fry it and take it in and they would say it was a battery short which fried it). Anyhow. I then figured I would try RUU. Problem was that I heard RUU wont work unless you are locked. So I tried to re-lock, and of course couldnt do it since fastboto USB wont work.
I decided to hit the RUU anyhow and it failed saying it was Security fail. I wazs thinking of options, hit it with stun gun hopefully sprint replaced, sink it and insurance replace it, or just head to sprint to see if they could help. But much to my surprise, I tried to boot into bootloader one more time and sure enough fastboot USB was back. My recovery was gone, so I flashed CWM again and was able to put eternity back on. The only problem is that my CWM was deleted and I lost my Nand. Not too big a deal as I can always put a stock rooted rom on and use that as my Nand. Or I can always just RUU to stock, then re-root just to be certain I have a clean nand.
Alright guys. Anyone care to comment on what could have been done differently?
Click to expand...
Click to collapse
Well there is a lot going on in that post ... Not sure how my application Flash Image GUI failed. I would be more than happy to fix/resolve any bug or issue you've encountered!
Fastboot usb mode should always work. There is no setting in Android which will have any impact on fastboot usb mode (other than not allowing the device to boot into the bootloader). I generally find the best process to be, boot the device into the bootloader, plug in usb and then select fastboot.
Perhaps, once you're in the bootloader, you can also select fastboot and then plug in USB (this works best on my NS4G).
Either way, fastboot usb should always work. If you're using Windows, there could definitely be a drivers issue or Windows being finicky with the drivers and that might result in fastboot USB not working. A simple reboot of the Windows machine should clear any fastboot driver issues.
The best working method to correctly load a ROM is by properly loading the recovery to work with the HTC unlock method. HTC unlock method will only grant the recovery write access to the boot partition when the recovery image is temporarily fastboot boot'd. The command is: fastboot boot c:\android\cwm-recovery.img.
If you boot into the bootloader and select recovery from the menu, it will boot into the recovery, but the HTC unlock method will not grant the recovery write access to the boot partition. You can flash a ROM from here and restore a nand. Both will completely successfully and claim they flashed the kernel w/o any issues but the memory write lock will have prevented the kernel writes from being retained.
Also, regarding my application, Flash Image GUI, it should properly flash any EVO 3D kernel .zip file from normal Android mode as the HTC unlock method allows kernel write access while in normal Android mode.
Why did HTC block kernel write access from recovery mode? They haven't provided an answer .. we can only speculate ...
Hope that helps explain a few more steps to the process and provide greater clarity!
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
thos25 said:
thanks Joey.
Who knows. I have no idea why your app didnt work. I would also like to point out that I am not blaming your app at all. I may have simply done it incorrectly. To be honest by the time I even used your app I was pretty frazzled, so I may have done an error.
Ok. So, yes. Everytime I flash I always use fastboot USB. The command you use is different from mine though. My command is courtesy of Zedomax (HTC Evo Hacks method). CD desktop \rootevo3dnew
fastboot boot cwm-4.0.1.4-shooter.img
So, I always use that when I flash.
I have no idea why fastboot USB dissapeared. At first I figured it was a USB port error. I have heard that many people with OG Evo and 3vo's have USB port issues. So, like a good troubleshooter, I went for the obvious and switched my USB cord. No luck. Then I figured I would plug it into the wall to charge to see if it charged. It did. So I knew it wasnt the cord and it wasnt the port.
Perhaps like you said, the driver was just wonky. I ran a check and it said driver was up to date, so I doubt it.
In the end plugging it into HTC Sync to run an RUU fixed the problem. Even though the RUU didnt go through because I was HTC unlocked, it did fix the USB error and I had USB access again. From there I was able to flash back into recovery and flash back to Eternity.
And on a side note, I also learned the importance of copying my ClockworkMod file off of my SD card and onto my desktop. Since I lost the recovery I no longer had CWM on my SD card and my nand backup was gone. So now I will always keep a copy of the folder on my desktop so that I make sure to have a working NAND.
And to be thorough I decided to re-lock, then re-unlock, re-root today as well. I figured this way I would be working with a 100% clean working ROM again to have a good NAND as a basis as opposed to downloading a stock rooted ROM. Im sure it is probably basically the same thing, but I wanted to do it this way to be sure.
thanks again. Ill let you know if I have any additional issues with your app.
Click to expand...
Click to collapse
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
I had a similar issue when i was switching to AOSP kernels/roms. I rebooted my phones once or twice and it connected fine. Maybe it have something to do with AOSP since MIUI is aosp also.
joeykrim said:
I'll give you a little feedback on the process to sum up your knowledge around the edges. Everything seems correct, there are a few points.
1) CD desktop \rootevo3dnew and fastboot boot cwm-4.0.1.4-shooter.img is the same as fastboot boot desktop\cwm-4.0.1.4-shooter.img . The only difference here is where the recovery image is stored. The key part is being able to supply the fastboot binary with the correct command being "boot" instead of "flash recovery".
2)If you lose your CWM recovery, it does not always mean you have lost your nandroid images. They are stored on the sdcard card under clockworkmod directory, /sdcard/clockworkmod . Even if you switch recoveries, these files will still remain. They should never be erased unless you intentionally erase them.
3) If you really want to start with 100% clean stock ROM, running an RUU is the best way. re-lock and un-lock, all it does is toggle a setting in the bootloader and wipe your /data directory. it won't make any changes to radio, system partition, etc. an RUU will copy over most of all the partitions with stock files, completely resetting the device.
appreciate your support with my app and hope the extra details help round out the edges! good luck!
Click to expand...
Click to collapse
Thanks for the comments and lesson. I apologize for not responding sooner, but a recent death in family prevented me from really being on here too much lately.
1) I pretty much figured that. Yeah. I only try to flash using this method, that is why when my fastboot USB disapeared I thought I was really in a bad spot. Luckily I got it working again, so all was not lost.
2). Yes. I know it should remain on SD card, which was strange why I couldn't find it. However, thinking back on it, I do remember deleting some files off of my SD card on the same night. I probably just mistakenly deleted my CWM Recovery with my NAND backups. Sometimes when I double click a file to look at it, when I leave the file I see that there is a checkmark on that file. I may have just not noticed the checkmark on the CWM, went to delete another file, and mistakenly deleted CWM with it.
3) An RUU will not change a RADIO? I was under the impression that they did. Sort of like applying an OTA, but manually doing it through SYNC.
well, thanks again though. I learned some new things and appreciate it.
Flash image GUI works like a charm
Sent from my PG86100 using XDA App
i m a newbie
plz tell me how to get out of the fastboot usb mode. i m stuck with the G1 screen having fastboot usb title on the top.
PLZ HELP!!!
Not the first post a noob really wants to make...but I've been searching the forums for an answer to my problem, but can't seem to find the info on the issue I'm having. I've seen some that were close & tried what was posted there without any success. I've checked out the Don't Panic -- Please Read First, includes troubleshooting guide Thread By: om4
A few days ago, I tried to install CM10 on my 4G LTE w/S-ON / HBOOT- 1.19. I was able to unlock the bootloader & install TWRP. Everything seemed to go okay until I rebooted my phone after installing CM10. It just hung on the Cyanogenmod splash screen. I tried re-installing it & kept getting the same problem. Today, I tried to install MeanROM ICS v6.5, but it keeps saying install failed. If I let the phone boot up, it'll hang on the MeanRom splash screen. I can still get into fastboot so I know it has to be a software issue. I've been beating my head against the wall for the past few days & just don't know how to fix it. Right now I have a very expensive paperweight. I'm hoping someone can help me fix this & get my phone back up & running.
TIA
for the millionth time
flash the boot.img seperately in hboot
Get (Flash Image GUI) off the Play Store.
If yr S-ON then u have to flash the kernel separate. That's why the ROM's keep hanging.
sent from my EVO LTE
http://forum.xda-developers.com/showthread.php?t=1772769&highlight=fastboot+gui
flex360 said:
for the millionth time
flash the boot.img seperately in hboot
Click to expand...
Click to collapse
I've been trying this all day, but must be doing something wrong. I found this: http://forum.xda-developers.com/showpost.php?p=29417266&postcount=1397, but was wondering if you might have more info on option 3.
TIA
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
popper668 said:
if you know how to Fastboot, go for it, but use the Boot.img from the ROM you are flashing.
Click to expand...
Click to collapse
It's the only option I have now, so I hope I can figure it out. Wish me luck. I know it's probably something stupid that I'm missing & it's driving me crazy. lol
For meanrom make sure you have twrp 2.2.2.0 or later to be able install. The kernel installer will force the phone to reboot upon first run, this is when the kernel installs. For cm10 or other aosp based roms be sure to properly wipe phone. Cache, dalvik, factory reset, and system. Fastboot the kernel using SDK, mini SDK, uniflash, or boot image flasher. Do not use clockwork mod recovery to install roms as it is known to damage internel storage and or misc partitions.
ADB Tools Mini SDK
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
buddahj said:
Thanks for all the info!!! I'm glad I found this place!!! I was able to get my phone working again. I found this post: http://forum.xda-developers.com/showthread.php?t=1937949 from back in October and found out that I was putting the boot.img in the wrong location. Once I fixed that, I have my phone back. Now I have to get it re-activated because I had to switch back to my Hero because I wasn't sure how long this would take. I hope Sprint will activate it even though is not stock anymore.
Click to expand...
Click to collapse
have your first thanks
lol
the thanks is for using the search function lol
Well now I have another small problem. When I try to use the camera or go into gallery, it says no external storage available. Looks like I'm off to search the forums again for a fix. I'm sure it's something minor.
It looks like it's the internal SD card. Under storage in settings it shows the external card's total space & the 3 GBs used for app data, ect...
When I try and mount the SD card, it says preparing card but doesn't do anything. I think I say something about changing something in TWRP.
Forgot to mention, I can't connect the phone via USB either.
Ha, fixed my SD card/USB issues by following the directions in this thread - http://forum.xda-developers.com/showthread.php?t=1812774
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
I'm updating this for anyone else who runs into issues like this: I went ahead and formatted the SD card from within windows, then relocked the phone, reinstalled the RUU and I'm back in a workable mode
itsmattgw said:
Trying to install MeanBean...I updated the Firmware to the latest, have the phone unlocked and rooted (it says TAMPERED and UNLOCKED in the recovery screen) and did a factory reset. I have TWRP installed and can still get to the TEAMWIN RECOVERY project interface...
I was installing MeanBean and it just stuck on about 75% and stayed there. I waited for about ten minutes and figured something must have gone wrong so I didn't really have a choice but to shut it down. After starting back up when I tried to install again it said "FAILED" in red letters. I decided to re-download the ROM but now when I mount the SD CARD from within the recovery menu (to transfer the new file) my computer says that I must format the drive before I can use it and won't let me see the contents of the sd-card. I didn't want to do that for fear of bricking...so I don't really know what to do from here. I should add that I don't have a backup made in TWRP (I got the phone yesterday and hadn't installed or done anything to the OS)
Anyone know what should be done at this point?
thx
Click to expand...
Click to collapse
I had the exact same problem. I just reformatted the internal storage and that fixed a lot of my issues. I can't however get the RUU to work. Can't seem to find my phone, neither can HTC Sync. Is this just a problem caused by MeanBean? I use to run MeanBean but then switched to CM10 for a few months and was going to switch back. Never had an issue like this before.
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
Hey Guys,
I rooted my phone and was on 4.1.2. and sense 4.5.
Today i noticed in my phone storage, there is this "other storage" occupying nearly 20 gb.
So i did a factory reset and found nothing changed. The "other" memory is still 18gb.
So i went to TWRP recovery and wiped every thing, even system files ( I was not thinking properly).
Now my phone is stuck in HTC white screen. I guess i lost my OS.
I can even go to recovery, but i have deleted my backup too.
How can I get my mobile to work again?
gvcabc said:
Hey Guys,
I rooted my phone and was on 4.1.2. and sense 4.5.
Today i noticed in my phone storage, there is this "other storage" occupying nearly 20 gb.
So i did a factory reset and found nothing changed. The "other" memory is still 18gb.
So i went to TWRP recovery and wiped every thing, even system files ( I was not thinking properly).
Now my phone is stuck in HTC white screen. I guess i lost my OS.
I can even go to recovery, but i have deleted my backup too.
How can I get my mobile to work again?
Click to expand...
Click to collapse
same here, from what i'd heard its called a soft brick and, you may need to find a way to push a rom on it using fastboot and adb.
i will let u know if i find something interesting
lha18 said:
same here, from what i'd heard its called a soft brick and, you may need to find a way to push a rom on it using fastboot and adb.
i will let u know if i find something interesting
Click to expand...
Click to collapse
Got my phone to work….
As my phone was unlocked (Bootloader), I relocked it.
Then download the latest RUU from this link
Connect your phone to PC and run the downloaded file.
It even updated me to 4.2.2 and Sense 5.
Good luck.