So I am unlocked and running MIUI
I was in CWM and my dog bumped my arm while I was trying to go to "wipe data"..
Instead I think I went to partition internal sd.
There was no backbutton only a few options
0MB
4MB
8MB
etc
or something like that.
Since there was no back button, I just chose "0Mb" hoping it would do nothing.
Then I rebooted recovery.. but this time instead of recovery it gave me a full white text boot screen, saying "choose and option 1 through 9. You have 5 secs to choose or it will go to "BP" by default". And it listed all the options you would see if you scrolled through them with vol down, all in one list.
I tried to vol down to recovery and choose it, but when I do, it just reloads this menu. I can choose fastboot and RSD and it will load those, but recovery seems to be gone.
I also see the internal storage doesn't show up when I boot the phone and connect to PC.. only my external SD does. So somehow I screwed the pooch. I guess my best bet would be to reflash the recovery through fastboot?
hmm now my PC isn't recognizing my phone in fastboot mode.
I tried rom manager and flashing recovery from within miui.. but it just does nothing.
OK on reboot I tried Rom manager again and it works. It still has that menu on boot, but recovery works now
Did this before. Only solution I came up with is flashing the SBF and starting from scratch. Hope this helps.
Sent from my MB855 using Tapatalk
i did this exact same thing the other day... I don't know what menu it is that i accidentally got into but it wiped something and my recovery was gone... flashed an sbf and got stuck in a boot loop and finally fixed it by wiping data
ugh
get into RSD mode and then flash the stock Rom..
After installing just wipe data in Stock Recovery mode..
Thats all.. You are good to go...
Make sure you have 5gb free in the drive you Run RSD Lite..
Yea I reflashed stock SBF and now it boots stock photon tho its stuck on "Contacting Network". reboot not helping.
The other day I was trying to back out of the advanced menu and ended up with multiple partitioning options with no back button. Selected one of the options. Lost all my photos
I could have tried to recover the data but decided it wasn't worth it.
I see a topic here with my problem:
http://forum.xda-developers.com/showthread.php?t=1284956
Tho I AM on the stock sbf so not sure why it is happening.. gonna try sbf again
sub2k1 said:
The other day I was trying to back out of the advanced menu and ended up with multiple partitioning options with no back button. Selected one of the options. Lost all my photos
I could have tried to recover the data but decided it wasn't worth it.
Click to expand...
Click to collapse
Why didn't you just pull the battery?
http://forum.xda-developers.com/showthread.php?t=1555948
Akilldema said:
Why didn't you just pull the battery?
Click to expand...
Click to collapse
I was being lazy. I figured that perhaps I accidentally hit a button combo that caused the back button to disappear. So I figured that a button combo might make it come back. Well I didn't find that button combo. I immediately pulled my battery when it said formatting SD Card but at that point it was too late.
sub2k1 said:
I was being lazy. I figured that perhaps I accidentally hit a button combo that caused the back button to disappear. So I figured that a button combo might make it come back. Well I didn't find that button combo. I immediately pulled my battery when it said formatting SD Card but at that point it was too late.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1496012
This happened to me because the back button too.........
Sadly, getting the menu to go away is not the main issue, you have actually erased your PDS partition which holds factory hardware information like MAC /bluetooth adr and stuff for the PRL/Data profile updates to recognize your phone.............Flashing the PDS partition from the Atrix Forums will create the partition but we need like a dev to help us figure out a solution for editing the files to work with Sprint software updates and getting all our hardware addresses on there correctly. No amount of flashing/SBF'ing stuff helped to get it working... some users suggest taking it to Sprint..
Oh so thats why I can't update my prl and profile. I had this happen a while ago and I just flashed a custom splash screen. Gonna go back tp stock and start it all over again. And if that menu happens to come up again i'll just pull the battery.
Plancy said:
This happened to me because the back button too.........
Sadly, getting the menu to go away is not the main issue, you have actually erased your PDS partition which holds factory hardware information like MAC /bluetooth adr and stuff for the PRL/Data profile updates to recognize your phone.............Flashing the PDS partition from the Atrix Forums will create the partition but we need like a dev to help us figure out a solution for editing the files to work with Sprint software updates and getting all our hardware addresses on there correctly. No amount of flashing/SBF'ing stuff helped to get it working... some users suggest taking it to Sprint..
Click to expand...
Click to collapse
It seems like it would be possible to dd a PDS partition image from a working phone and flash it to the phone with the bad PDS parition via fastboot as long as you knew the partition it needed to be flashed to, although it would have the data of the other phone (as far as bluetooth, MAC addresses). Not sure how to go about editing in the info you need though. Just tossing out ideas
-devx
This might help...hope it does.
I had formatted my internal SD which toasted my PDS partition.
I fixed it doing this...
http://forum.xda-developers.com/showthread.php?t=1575035:)
Related
OK well I have trying my best as a noob to research for 2 days not in and out on how to fix my issue
My friend tried rooting my phone and to install a different rom. I am on 2.1 and unfortunately I got the phone used with 2.1 already on it so I don't know if it was a leaked or legit 2.1 rom, and I am learning as I go here to fix this issue as I have never new how to do this stuff nor have I ever done it.
Where I am at now:
only thing that happens when I hit power is the phone "vibrates then stays on the 3 skateboard screen" or press "volume down + power" and it goes to the Hboot screen. I go into recovery and it goes to clockworkmod and from there after trying to install any roms from the sd card it says on the last 3 lines
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
and every time I go back or power up to the Hboot screen it does not have any "update bar" (I guess if this was done right as I read on other threads there should be some type of update bar) on the right corner or any other options "for me to select" accept:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
and then with some other info above the Hboot highlighted in blue
I have tried formatting the sd card a bunch of times, I did the clearing of the "wipe data, wipe cache partition, wipe dalvikcache" as I read to do over my reading, but I see that if I go under any restore options under clockwork, no files are found for me to back up too so I am seeing he did not back up any of my info, I also have tried using 2 different ds cards.
So more less it looks like my options are to get this fixed from the only place my phone will boot to with options and thats when I press volume + and power so I guess loading whatever I need to my sd card>>if thats an option or am I screwed, I have seen many tutorials but none of them start where my particular position is stuck at in Hboot. this is my only phone and I had to buy a prepaid which is just about out of minutes, I put an add on craigslist trying to get someone I will pay to fix my issue but no luck, please I need help and I will pay u somehow to guide me through this of my exact issue, I was trying to get to rom 2.3 but if it's easier to get back to 2.1 rom then so be it.
PLEASE!~~
Please HELP!
Cheeva316 said:
Please HELP!
Click to expand...
Click to collapse
Got a solution in the making for you, just give me about 30 minutes.
Edit: Maybe 45 minutes lol, sorry i'm testing this before I have you do it to see if it works.
Ok download the following files:
http://www.mediafire.com/?njwqa7axwzyaqgb
http://www.mediafire.com/?f69cl8dc747h0l9
http://www.mediafire.com/?xg8nnqs177xggx4
http://www.mediafire.com/?qxpi5wsx5lzbhbo
http://www.mediafire.com/?4tg67hck7vh1xxs
Edit: Flash the "rootme.zip" first then follow the rest.
Now what you need to do first is extract the "nandroid" file to somewhere you can easily find it.
Now take the folder called "nandroid" along with all the other zip files you downloaded and place them on your sd card. Put your sd card in your phone and power on with volume down+end. Press volume up. Use the trackball to select "Backup/Restore". Use the trackball again to select "Nand Restore". Use it again to select "HT9BGHG01402". Use it again to select "BDS-20110125-0901". Let the restore run, then power off your phone. Turn your phone back on with just the power button, let it run (might even take up to 10 minutes for the phone to start up). Let me know if the phone boots up or not after about 10-15 minutes. This should work and if it does then we can go from there, even to getting you 2.3 if you want.
You might be asking, what the hell is he having me do ? Here's what i'm doing. I made a nandroid backup a few months ago of when I had kaosfroyov39 which is a 2.2 rom. I am going to have you flash MY backup to YOUR phone which when done right, CAN work. Anyway, let me know what happens and remember to give the phone about 10-15 minutes to boot all the way.
Cheeva316 said:
"E:Failure at line 9:
copy_dir PACKAGE:system SYSTEM:
Installation aborted.
Click to expand...
Click to collapse
( Another phone on the precipice of being ruined by someone's cobbled-together "clockwork" recovery. )
If the /system flash memory partition got corrupted in a way that left a lot of pages marked as bad pages, then the /system partition will be "short", and only small ROMs will successfully load into it, if at all. That might be the cause of the above error messages.
But - because you are using Clockwork, there is really no way to know if that is the case, or if you simply have a whole bunch of corrupted ROM files on your SD card. That's because Clockwork does not verify ROM files before it starts flashing them - which allows total garbage to be flashed to the phone. (That's why Clockwork should never be used by newbs).
Here's what I would suggest you do.
- Make sure you are keeping the phone well charged. (Leaving the phone in HBOOT mode will discharge the battery quickly, even if it is plugged in to the charger, BTW).
- Report the exact bootloader version you have - probably 1.47.0000 or 1.49.0000, but it could be something other. Please be precise.
- With the power off, eject the SD card out of the slot and see if you can boot into the normal HBOOT menu with no SD card in the slot. Report your result.
- Boot into the recovery menu and tell us what version # of the recovery you have. If you can determine the details of how your friend attempted to root the phone, that might be pertinent. Again - precise details are valuable; vague hand-waving not so much.
- The Amon_RA recovery has a mode ("USB-MS toggle") which allows you to mount the SD card to the PC. Does your "Clockwork" recovery have this feature, or are you able to put files onto the micro-SD card using a media slot on a PC?
- Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
What I would suggest you do at the moment is to find the SMALLEST Eris** ROM you can find, get it onto your SD card, verify that you didn't corrupt it, and then perform a "wipe data/factory reset" in your recovery and attempt to install it. If you get the same errors as above, then you should definitely NOT try to do a PB00IMG.ZIP or RUU installation. (The current gingerbread ROMs (e.g. GSB v1.4) are pretty small - they only use about 65% of the /system partition.)
I have a flashable "repair" file which might be applicable. It is not a "ROM" per se - it uses some low-level MTD (flash memory) repair techniques, and also flashes into place the original Amon_RA (v1.6.2) recovery, instead of whatever p.o.s. "Clockwork" recovery you currently have on the phone; but I regard it as something which should only be used as a last resort. But - without some more details and testing on your part, I don't feel comfortable about posting it up.
Let me know.
**PS I wanted to ask one more question - this is an Eris we are talking about, right? (I note you were posting in the Hero CDMA forum not so long ago).
Well I want to thank you for replying with such info but it seems that the recovery image file that I reinstalled on the phone was bad cause when it was updating the bar was going up but as it was going through each item it was updating.. I noticed "bootloader in red letters" with I believe saying "error" next to it and then same on another item it tried updating then the phone powered off and now it's dead, tried everything, no charging light comes on, computer (2 different computers) wont reconize it, it's doing nothing at all, I will try to get my hands on another battery but I am broke, but I doubt it's the battery cause I heard with a bootloader error (or damaged) then the phone won't boot up or do anything so I guess the phone is scrap for parts which sucks cause now my friend who started this deal killed my only phone me n my family had, another lesson learned...time to try n sell some stuff on craigslist..damn
Yes it's a Droid Eris...or was! damnnnn...
Again thank you for your help very much appreciated...
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Cheeva316 said:
Wish I would of read this part before I let my friend re-load the "PB00IMG.ZIP" cause thats exactly what he loaded and then it started the process what I jus described above..f***k!
Be aware that one or two people that were in situations that are very close to what you described ended up bricking their phones because they went from where you are now to attempting to use either a PB00IMG.ZIP ROM, or an RUU utility. Their phones went from bootable (in the way that yours is now) to bricks in that process.
Click to expand...
Click to collapse
Well, I am very sorry that this happened to you and my advice to you didn't reach you in time. From the details that you added, I am pretty sure that you indeed have a hard brick.
BUT - the death of your Eris can still help others avoid the same fate. If you can reconstruct the rooting process you went through,
[SIZE=+2]PLEASE LET US KNOW EXACTLY WHAT ROOTING METHOD YOU USED[/SIZE] - and then we can wave people away from it.
When I say exactly, I mean extremely specific: do you still have the download file that you used? If so, push it up to an uploader site and give a link to it. (I think you mentioned unrevoked or something). Do you still have the exact link you used to download that rooting software? Was it Unrevoked? Z4root?
bftb0
I will tomorrow as I saved all the files on my laptop n I am on my pc now, but will do try my best as I am a newb to this phone stuff
Did you try what I suggested or is it too late ?
phone wont do anything so cant do nothing...
Did you find out any more details about the rooting method you used?
might be a couple more days till I can get to it, my laptop is messing up now...all the saved info was on it
Good afternoon folks,
I had a "situation" where I found myself missing some apparently critical "bloatware" on my phone. Came up with lots of errors and a lot of functions no longer, well, functioned. Got too carried away I guess.
I had done a system backup with Titanium Backup. I initially tried just restoring some of the apps. Problem was, it just sat there saying restore. Just stuck. So I thought, hey, I have it backed up, I will do a factory reset. I did this, only then to find out that my backup was located on the INTERNAL sdcard not sdcard-ext, so all of a sudden I have no backups.
I do have access to another Electrify, if it would help. What I then decided to do was try downloading a factory rom for my phone. I downloaded "1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.rar" off of the teamuscellular.com page. I booted the phone in RSD mode, restored it (three times now actually), and every step seemed to go fine (RSD even says it finished fine). But on the last step when RSD says it is rebooting the phone, at the very end, it comes up with an error :
"Failed to boot 4
starting in rsd mode"
I have read elsewhere where people say it is related to the battery. I had a 60% charge for the first two times I did this process, the last time I used the battery from the other phone which was at 95% plus. So far I have not been able to get past this.
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
In case this might help figure out the issue, here are some details from the phone :
System version - 45.1.190.MB853.USC.en.US
Model number - Motorola Electrify
Android version - 2.3.5
Also worth noting, I did not see anything on the screen ever indicating I was "unlocked".
What I want when this is done and over with is to get the phone back and working stock, root, and make barnicle wifi work. Any advice would be most helpful, I am really kind of freaking out here.
H-E-L-P!
Thanks,
ledoktre said:
Good afternoon folks,
I had a "situation" where I found myself missing some apparently critical "bloatware" on my phone. Came up with lots of errors and a lot of functions no longer, well, functioned. Got too carried away I guess.
I had done a system backup with Titanium Backup. I initially tried just restoring some of the apps. Problem was, it just sat there saying restore. Just stuck. So I thought, hey, I have it backed up, I will do a factory reset. I did this, only then to find out that my backup was located on the INTERNAL sdcard not sdcard-ext, so all of a sudden I have no backups.
I do have access to another Electrify, if it would help. What I then decided to do was try downloading a factory rom for my phone. I downloaded "1FF-sunfire-user-2.3.5-4.5.1A_SUN_USC_19.0-19-release-keys-signed-USC-US.rar" off of the teamuscellular.com page. I booted the phone in RSD mode, restored it (three times now actually), and every step seemed to go fine (RSD even says it finished fine). But on the last step when RSD says it is rebooting the phone, at the very end, it comes up with an error :
"Failed to boot 4
starting in rsd mode"
I have read elsewhere where people say it is related to the battery. I had a 60% charge for the first two times I did this process, the last time I used the battery from the other phone which was at 95% plus. So far I have not been able to get past this.
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
In case this might help figure out the issue, here are some details from the phone :
System version - 45.1.190.MB853.USC.en.US
Model number - Motorola Electrify
Android version - 2.3.5
Also worth noting, I did not see anything on the screen ever indicating I was "unlocked".
What I want when this is done and over with is to get the phone back and working stock, root, and make barnicle wifi work. Any advice would be most helpful, I am really kind of freaking out here.
H-E-L-P!
Thanks,
Click to expand...
Click to collapse
did you install the moto drivers? if you're unlocked be sure to flash 2.3.4 not 2.3.5
Good afternoon,
I have installed the moto drivers. I am on Windows 7 64 bit (dual boot with Linux Mint Debian 64). I installed "MotoHelper_2.1.40_Driver_5.5.0.exe", and was using RSDLite5.6.
As far as I know, the phone was locked. Rooted, but locked. Some say it will actually say on the screen 'unlocked', mine does not say anything like that.
Thanks,
Just to make sure it's not a battery issue, there is free battery swap if you can run by a USCC store. But I think you're right, it's probably not that. Wish I could help you more, but it stumps me.
ledoktre said:
Another post suggested that I should pop out the battery, pop it back in, hold the vol down and power buttons, and then do a factory wipe of the /data partition. This is fine, but I cannot get it to go past the Moto screen unless I let go of the buttons.
Click to expand...
Click to collapse
From the phone completely off, hold vol-down and power. When the screen lights up, release power ONLY. Keep holding vol-down until some text shows up then release. Click vol-down to scroll through options until Recovery shows up. Click vol-up to select. Once recovery starts, navigate using vol-up/vol-down and power to select. /data will be wiped if you do a factory reset.
Hope this helps.
I'm new to the andriod side of things but am very computer savy. Can someone please help? My son has this nextbook tablet and today when he turned it on, it hangs up on the second boot image. I went into recovery but didn't want to restore to factory just yet if i didn't have too. I've read so much i am confused. We have four boys, so that means we have four of these tablet, since Christmass. This is the only one not booting for whateer reason now. What can I do? Can i pull image from one of the others and install n this one, or just certan boot files? Please help and thank you for any reply.
Grwx4dad said:
I'm new to the andriod side of things but am very computer savy. Can someone please help? My son has this nextbook tablet and today when he turned it on, it hangs up on the second boot image. I went into recovery but didn't want to restore to factory just yet if i didn't have too. I've read so much i am confused. We have four boys, so that means we have four of these tablet, since Christmass. This is the only one not booting for whateer reason now. What can I do? Can i pull image from one of the others and install n this one, or just certan boot files? Please help and thank you for any reply.
Click to expand...
Click to collapse
I had the same problem with my next 7 premium se 8gig.
Pop your sd card in.
Boot into recovery mode by pressing the power button and the volume down button at the same time.
When recovery comes up, delete the media partition, clear your cache and restore to factory settings.
Choose the option to restart the tablet.
Once it boots it should be back to life though you will lose everything on it.
Beats having a useless tablet though.
It took me only a few hours to reload all my apps and she's been running fine since.
Good Luck.
I got it to go to recover but once at recovery it says upgrading please wait and sits their.
Exact same issue...
Any luck in resolving this yet? I have google for 16 hrs so far, and tried countless methods of restoring my tablet to it's previous glory...
Any help is much appreciated. :fingers-crossed:
sd card
you mention an sd card,where do i get such an sd card?
scarsfromknives said:
I had the same problem with my next 7 premium se 8gig.
Pop your sd card in.
Boot into recovery mode by pressing the power button and the volume down button at the same time.
When recovery comes up, delete the media partition, clear your cache and restore to factory settings.
Choose the option to restart the tablet.
Once it boots it should be back to life though you will lose everything on it.
Beats having a useless tablet though.
It took me only a few hours to reload all my apps and she's been running fine since.
Good Luck.
Click to expand...
Click to collapse
Well, my problems with recoveries are sorta of a jokle by now, but I still feel compeled to share my experiences so maybe anyone can tell me what the hell is happening on my phone....
So as I said some time ago, I experienced problems with the PhilZ recovery, which I solved swapping to CWM version 6.0.3.2. The problem was the infinite bootloop of the Samsung Galaxy GT-I9300 logo, the black screen, which did not allow me to access to the recovery. But inmediatly after flashing to the old CWM the problem was gone away. Also, in a case of a possible kernel panic due to doing some stuff with Xposed modules CWM was the only recovery I could get access into.
Now, the problem is the following. Yesterday I installed the CWM Touch version 6.0.4.7, which I got from this thread http://forum.xda-developers.com/showthread.php?t=2052091. After installing it everything was normal. However, after one hour or so the phone screen wouldnt turn off when I pressed the Power Button. In fact the Power Menu appeared, but the screen, as I said, dindt get to sleep mode. To top that, after freezing for a second the phone suddenly turned off, and then get to the infamous black screen with the model logo looping and looping.
Fortunately, after pressing Volume Up+Menu+Power I could get to the Recovery, but not after quite some seconds pressing these three buttons. And in some times it would not get me to the recovery, but instead completely rebooting the phone and working again. Just to, in half an hour, freezing and looping again and again and again.
This problem happened to me with virtually every ROM I installed, being Neat ROM, Archi, and even CM11 from Temasek. Nothing would solve that problem. The only remedy I had was a temporary one, which consisted on uninstalling and reinstalling again the kernel (I used boeffla) and the problem would not disappear that way. Also, when wiping data, for some weird reason it gave an error message while wiping the /preload partition, in the Mounts and Storage menu.
Until I got home today, and then flashed through Odin the old CWM Touch version 6.0.3.2, that finally stopped the problems. I tested it by pressing the Power buton again and again and it hadnt redirected me to the black bootloop screen. Seriously, I am wakelocking my phone on an intensive basis and nothing has happened for now, and I think it probably wont happen again. Maybe it takes three seconds, maybe the Power Menu displays again, but no bootloop again.
So I ask to you, what is happening on my phone that it wont run recoveries younger than my old 6.0.3.2
IMPORTANT EDIT: THE PROBLEMS ARE NOT SOLVED YET
Some hours ago, I was chatting using Whatsapp while charging the phone on an USB charger, when it suddenly suffered the black screen bootloop again. This time was unexpected, since I was using the CWM Touch 6.0.3.2, the one supposed to work fine. So for now I feel completely finished. My phone is officialy into a unsolvable problem.
But, thinking about it, there were some things that might help you:
-This time I did not uninstall and reflash the kernel: When I got to the recovery menu, I just selected "reboot", as such, without flashing anything else, and the phone then worked as fine, booting into the ROM bootanimation screen (this time the Neat ROM bootanimation). So basically a manual reboot through Recovery got me out of this. Also, I kept using the phone until now and there werent more problems, at least for now.
-As far as I can recall, these problems started some weeks ago, when I accidentally formated the internal SDcard. I was using PhilZ Touch Recovery and flashing a ROM as usual, when I selected without knowledge the option "Format /data and /data/media (sdcard)" in the Mounts and Storage menu. I did this after doing the usual Full Wipe before flashing an new ROM, and after that I had to turn off the phone in order to insert a ROM in the external SD card to flash it through the recovery to make the phone working again. But when I wanted to get back to the recovery, I couldnt. I had to flash CWM 6.0.3.2 because it was the only recovery that let me access to the recovery menu-the already installed PhilZ wont allow me to access to the recovery menu. So in CWM I got to the External SD card and flashed a Neat ROM, and got the phone working again. And after that I reflashed PhilZ. But since then the phone started to experiment these freezes, reboots and bootloops. One happened to me when in College, and couldnt get out of it because PhilZ wont respond to the Manual Recovery command. I had to wait to get home, to reflash the CWM 6.0.3.2 recovery through Odin because that Recovery was the only responding. And in that moment it did well, and didnt have more reboot problems. Until I flashed 6.0.4.7, which is why I am here.
-Lastly, about the reason I trust in CWM 6.0.3.2: Some time ago, when flashing Blackbox ROM 2.0.2, I downloaded the Gravity Box module from Xposed, and installed it alongside with other modules, which, supposedly, caused a kernel panic problem that sent my phone into the dreaded black bootloop again. I was using PhilZ recovery, and as you may expect now, I couldnt get access to it, so I flashed the CWM 6.0.3.2 recovery, which let me access to a recovery. I too flashed TWRP, but it accessed for one second to the recovery menu, and then faded away, returning to the bootloop logo screen. So basically PhilZ and TWRP failed me during that kernel panic problem, while CWM stood the problem. And thats why I turn to this recovery when everything else fails.
And thats why I am troubled now, because this recovery is showing signs of failure
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
andrewwright said:
Try cwm 6.0.4.4 as I've used this for all sorts of Roms and have no problems
Click to expand...
Click to collapse
I used 6.0.4.7 and I had the problems previously described....I mean, I used a more updated version than the one you propose. Do you believe its gonna work better?
And thats why I will stick to 6.0.3.2 until someone tells me whats happening. If an updated version of 6.0.4.4 gives me problems...well, go imagine.
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
andrewwright said:
I can confirm that 6.0.4.4 works. I Also tested it for nandroid bk up and restore and it works. I have flashed the latest tw 4.3 and the old 4.1.2 and aokp/cm/aosp 4.4.2 and all flashes with no errors. I have 6.0.4.7 but not tested it this is why I said to you to use 6.0.4.4
Only thing I haven't tested is adb.
Click to expand...
Click to collapse
Interesting. And where do I get the 6.0.4.4? I dont see it neither in the new CWM thread nor in the old one.
Look down
here. zip so just flash in recovery
andrewwright said:
here. zip so just flash in recovery
Click to expand...
Click to collapse
I apreciate your help, but now some new problems have emerged, and I need more help, because maybe I might have a corrupted partition or such, who knows.
With this quote, I too try to bump the thread, in order to gain more attention to my new problems
If anyone is interested, please look the OP, as it has been edited to describe the new problems.
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
andrewwright said:
Best thing to do now is go bk to stock firmware with Odin and see if any problems persist. Totally stock for a few days.
Click to expand...
Click to collapse
I will try that in a few weeks, I am a bit busy by now to test anything...
Fortunately, the CWM 6.0.3.2, while not infallible, works better than the other recoveries...today I only had one bootloop problem, solved by simply rebooting from the recovery....I can keep it for one week or two, it doesnt worry me for now.
Also, there is a guide to reflash stock? Sometimes I reflashed stock, but it kept bootlooping on the Samsung animation...probably because I didnt know how to wipe data while reflashing stock. Thats a little problem I have with reflashing stock, any help is appreciated.
Odin wipes the phone while flashing. What rom are you on? Custom
Well, I have to bump this post again because I am having the same problems again.
I am using CWM 6.0.3.2 as my current recovery. Today, I was browsing the Facebook app when I pressed the Power Button. Then, a lag of 2 seconds happened, the Power Menu displayed on screen, and the phone got into the black boot screen again. But this time I could not get to the recovery. Whenever I pressed Volume up+Power+Menu there appeared a black screen featuring the CWM logo and then it returned again to the black boot screen again. So what I did was to remove the battery, then eject the Exterior SD Card (A Lexar, 32 gb) and put again the battery in its place. The phone started all normal again, and when I put again the SD Card it continued to work normally.
So, what do you think its happening? Not even my old recovery, the one which works better for me, is reliable anymore. Could this be a component of my phone failing? Particulary the emmc chip? Or its not a hardware problem? Should I sent the phone to reparation?
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
andrewwright said:
How much data do you have on ext sd? Maybe phone is scanning ext sd and if alot of data is there that maybe the cause of the reboots. Try a different sd for a few days or none at all. See if you have the problem.
Click to expand...
Click to collapse
I have almost 29 gb on the sd, but I had that data since the very first day I bought the card....thats more than one year ago. And I started having the problems since february of this year....
The problem has not reappeared. But what I still have is an insane battery consumption. See, I use apps like Facebook and Twitter, but I too use Greenify to hibernate them. It even drains too much battery by using the web browser. And I repeat, those problems trace back to February...which is the month when I accidentaly formatted the internal SD Card...
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
andrewwright said:
One year old + battery using Facebook and twitter and all the rest of them very power hungry apps are no good for battery life. Greenify uses battery, people forget that too. Remove all the apps above and test. Also if anything formatting int SD will speed up the phone not slow it down. It get rid if all the bit left over from ROMs/Recovery's/kernel's. Formatting int sd is good for the phone once in a while. Just remember to back up data first
Click to expand...
Click to collapse
Thanks! Whenever I can, I will try those tips for battery saving.
But what still puzzles me is the "Sudden reboot problem". It vaguely happens, but when it does I am basically screwed, and each time the reboots seems to get worse from recovering....Also, the reboot problems started after formatting the int sd card for first time. And, after that, I remember that, when I wiped data for installing a new ROM, it gave me "(E: unknown volume for path [/sd-ext])" or, something similar. Does this help you for identifying my problem?
OK, now I am royally screwed
I have suffered another sudden bootloop problem, and this time, even by removing the ext SD Card, phone doesnt restarts. Also, I cant access to the Recovery Menu. It does appear for a while and then fades away. But the worst part is that I cannot get into the Download Menu. When I get to the select screen, when I cant choose between Continue and Cancel, the Volume buttons doesnt work. I can not get into Continue button. And then it restarts.
So this time I can not even access to the Download Menu.
I am using the same ROM as before: Neat ROM 6.7 with CWM Touch 6.0.3.2 and Boeffla Kernel
I dont know if I can even send the phone to repair, as seen that I may have the Binary Counter...and I cant even access to Download.
Please, really, help me to get out of this, so I can factory reset this.
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
andrewwright said:
Take the battery out then hold buttons for download mode and while holding these buttons put the battery back in and pray mate. Not being able to get into download/recovery mode as you know is really not good. Maybe a jig to force it to download mode.
Click to expand...
Click to collapse
I did that, and I got into the Download Menu. But the menu was frozen as usual. I could not access to the Odin Menu. It didnt matter which option I chosed, since both of them didnt work and the menu would still be frozen, and then restarting the phone a few seconds later. I mean, I got to the screen where you can choose to get to Download Mode or to restart the phone, and it still was a stuck screen, no matter what I chose, the options did not work, and then the phone restarted again.
And I have no jig next to me. So, I am screwed. For real.
Im going to take it to the store where I bought it, which is near where I live...To see if they can do something. Otherwise...I think I will throw away this phone. Its been almost 2 years, and recently it started to fail, probably because of a crappy emmc chip...that store sells the Moto G, which is great, since I dont plan to waste a lot of money on a new phone, watching how this has ended.
And it sucks that I can not recover the data in the Internal SD
After years of great service my i717 will not boot. It shows Samsung, then this changes to a slightly fuzzy version of Samsung and just hangs there.
I am totally new to doing any modifications to phones.
I tried pressing vol up/dn then power and and it showed a screen about downloading a custom something but it didn't look like anything downloaded and this didn't help.
I then tried the genius method of just trying stuff!
I downloaded Odin 1.85.rar and cwm-i717-120305.tar.md5 and installed this as the pda option.
The phone still hangs at Samsung
But now when I hold vol up / dn and power I get a CWM-based Recovery v5.5.0.4 menu.
I put a sdcard in and chose the menu options to format the sd card, mount it and then do a back up to the sdcard.
It listed a lot of files and then rebooted.
When I mount the sd card in a PC it is blank.
I would like to recover my contacts from this phone if possible and I would like to get the phone working mostly so I can read NFC chips for some NFC development I am doing.
Please someone tell me what to do to get the phone to boot and a link to getting started information for someone totally new to phone modding.
Thanks.
What no one wants to help a total noob?
Was I too honest?
Would it have helped if I said I spent two whole days researching this?
About half of the problems with boot loop on i717 seemed to be caused by a stuck power button which obviously was not my problem.
ALL of the other suggestions I found were no help either.
So totally new to this I figured out I should download odgin, and this specific cwm file cwm-i717-120305.tar.md5 and install it with specific options.
I then tried to wipe the cache,
And wipe the dalvik cache,
both didn’t help.
I then tried to do a full back up to sd card.
It ACTED like it did the back up but the sd card when mounted on a PC was blank.
I then did a factory reset and now I have my good old ATT i717 note v1 working again!!
I would have liked to get my contacts but had no help.
This is all I really needed because now I have NXP Taginfo running reading nfc tags which my new J7 doesn’t do even though it says it has NFC support.
I would REALLY like to know why
1) CWM back up looks like it works but ends up with a blank SD card.
2) Boot HANG on second “fuzzy” "Samsung" screen, why is this and how to get a back up of contacts when CWM doesn’t back up.
3) ATT store “help” should have done a simple factory reset on the phone to avoid me having to buy a new phone. But they of course acted like I needed a new phone. This alone makes me want to switch.