I have a locked Moto Photon 4g, rooted. And decided to play with other ROMs to see if I could improve battery life, maybe reduce lag a little. I chose Rocko 3.0 (I know it's not supported) because it's one of two options I could find that would work with a locked device, therefore allowing me to retain 4g (I need it in my area. 3g is a dog here but 4g works well).
I used System Recovery to install it, and it seemed to go smoothly. The only things that don't seem to have gone as planned are:
1) I did NOT wipe the data or the cache's, when flashing, as I anticipated the flash process would do this. It didn't, and everything stayed intact and seems to be working fine.
2) As indicated in the video by QBKING77, there are some cosmetic differences between Rocko ROM and the stock ROM. But, missing seems to be the built in numbered percentage for the battery monitor, and the different boot options.
3) When booting re-booting, MOST of the time, i get the message "the process com.android.phone has ended unexpectedly. Please try again". I hit the "force close" button, and it occasionally comes up again a few minutes later, but then stops. It doesn't seem to do any harm, so I am inclined to leave it unless someone has a simple answer for fixing it. I have already cleared the cache and Dalvik cache, and this did not help. I would prefer NOT to wipe the device and start over just for an annoying thing I have to click past one or two times.
Any thoughts? Can anyone give me some more insight into the benefits of Rocko 3.0 (again, I know, unsupported. But, some of us want to keep 4g AND ROM).
Thanks!
I have noticed that if you do not clear everything your supposed to before installing a Rom it only causes problems. its like the previous rom and one your installing form a hybrid. I would suggest clearing data, system, cache, dalvik cache and reinstalling.
Sent from my MB855 using xda app-developers app
Go here and download the one that says FULL WIPE. Flash this in your recovery, wipe dalvik cache under Advanced, then install your rom again and report back with the results.
As far as battery, make sure that you calibrate after flashing. This means, charge your phone fully, reboot to recovery, go under Advanced again and wipe battery stats. Run your battery down till phone shuts off, plug it in while holding the power button (this will bypass charge mode, booting straight to android), charge to full battery again. Your good to go.
Acvice said:
Go here and download the one that says FULL WIPE. Flash this in your recovery, wipe dalvik cache under Advanced, then install your rom again and report back with the results.
As far as battery, make sure that you calibrate after flashing. This means, charge your phone fully, reboot to recovery, go under Advanced again and wipe battery stats. Run your battery down till phone shuts off, plug it in while holding the power button (this will bypass charge mode, booting straight to android), charge to full battery again. Your good to go.
Click to expand...
Click to collapse
Thanks. So, I downloaded Full Wipe, dropped on my SD, installed it through cwm recovery (again, I'm running a stock device), and now, my phone will only boot to the Motorola Dual Core splash screen and sits indefinitely. I went into Android Recovery and tried to reinstall Full Wipe, and it said "e: signature verification failed, installation aborted". I did a fill wipe from Android Recovery and then told it to re-install the Rocko ROM and it said the same thing, "e: signature verification failed, installation aborted". I understand this is because I am on a stock device and need to do all my installs through cwm recovery, but I can't get to it. So, what do I do now?
So, now, unless I am booting into Android Recovery, I can't boot past the Motorola Splash screen. Kinda bricked for the moment.
Any insight would be appreciated.
pelikan3 said:
Thanks. So, I downloaded Full Wipe, dropped on my SD, installed it through recovery, and now, my phone will only boot to the Motorola Dual Core splash screen and sits indefinitely. Any insight?
Click to expand...
Click to collapse
Sounds like you need to SBF back to stock. Be sure not to accept the OTA update that will probably come once back on stock.
I would suggest giving MOF Rom a try. It is supported.
pelikan3 said:
Thanks. So, I downloaded Full Wipe, dropped on my SD, installed it through cwm recovery (again, I'm running a stock device), and now, my phone will only boot to the Motorola Dual Core splash screen and sits indefinitely. I went into Android Recovery and tried to reinstall Full Wipe, and it said "e: signature verification failed, installation aborted". I did a fill wipe from Android Recovery and then told it to re-install the Rocko ROM and it said the same thing, "e: signature verification failed, installation aborted". I understand this is because I am on a stock device and need to do all my installs through cwm recovery, but I can't get to it. So, what do I do now?
So, now, unless I am booting into Android Recovery, I can't boot past the Motorola Splash screen. Kinda bricked for the moment.
Any insight would be appreciated.
Click to expand...
Click to collapse
What i sent you was just a flashable zip that tells recovery to wipe cache, system, and data. Same thing as doing it manually. When you flashing it the first time, did you immediately flash rocko rom afterwards? Thats what i was trying to get you to do, it should have booted up in Rocko afterwards.
But being stock means that bootstrap is the only recovery you can use. Its a workaround based off of CWM. You can't actually get CWM on your phone without being unlocked.
Boot into android recovery (Bootstrap), wipe system, wipe data, wipe cache, wipe dalvik, then try to install Rocko. Tell me if that works. If not, youll just need to SBF back to stock and install boostrap recovery again.
I did SBF back to stock. That was a VERY long process, but it turned out well.
For the moment, I'm going to sit, as-is, stock and unrooted, until I get a better idea of what the benefits are of the MOF ROM over stock.
Thanks!
pelikan3 said:
I did SBF back to stock. That was a VERY long process, but it turned out well.
For the moment, I'm going to sit, as-is, stock and unrooted, until I get a better idea of what the benefits are of the MOF ROM over stock.
Thanks!
Click to expand...
Click to collapse
Glad its working for ya. Make sure not to take the system update if you ever plan on unlocking or running a custom from as you won't ever be able to. But the benefits of mof is generally 1080p recording over 720, some bug fixes and bloat removal, toggles, and generally just a bit speedier and lag free. 1080p and the bug fixes can be had by taking that update. But again, you won't be able to get rid of it if you do it so make sure you're cool with that.
Sent from my MB855 using xda app-developers app
Acvice said:
Glad its working for ya. Make sure not to take the system update if you ever plan on unlocking or running a custom from as you won't ever be able to. But the benefits of mof is generally 1080p recording over 720, some bug fixes and bloat removal, toggles, and generally just a bit speedier and lag free. 1080p and the bug fixes can be had by taking that update. But again, you won't be able to get rid of it if you do it so make sure you're cool with that.
Sent from my MB855 using xda app-developers app
Click to expand...
Click to collapse
Thanks, I'm not really certain theirs much benefit to 1080p, because I'm not going to be hooking my Photon to a larger screen, where I understand the true benefit lies. I wouldn't mind a little less lag, though, it's not critical. The biggest thing for me is some kind of built in battery and wireless management that dramatically improves battery life.
But, I don't plan on going with an unlocked solution unless they find a way to preserve 4g on an unlocked device.
pelikan3 said:
Thanks, I'm not really certain theirs much benefit to 1080p, because I'm not going to be hooking my Photon to a larger screen, where I understand the true benefit lies. I wouldn't mind a little less lag, though, it's not critical. The biggest thing for me is some kind of built in battery and wireless management that dramatically improves battery life.
But, I don't plan on going with an unlocked solution unless they find a way to preserve 4g on an unlocked device.
Click to expand...
Click to collapse
Bummer, cause the real battery improvement comes with using custom kernels and getting rid of all those perpetually syncing items (motoblur).
Related
Ok so I rooted and RoM'd my phone a long time ago with Cherryblur which apparently is no longer supported or updated. It has been so long that I forgot what I did and did not do to get cherry on it. Yesterday I spent most of the day researching how not to brick my phone. Today after doing everything I could find, I am stuck at the motorola screen. It is unlocked on the moto screen, has fastboot and adb installed, I can get into recovery and what seems to successfully recover the cherryblur install just results in a bootloop at the custom animation that is past the motorola screen.
I was trying to flash CM7 (tried neutrino as well) non nightly when this happened. After spending all day on here bouncing around while I was at work I found a fruitcake that seems to be the only thing that will allow my phone to boot which of course I cannot send the link to. Its titled [Fruit Cakes] XDA Re-Release [feb\18\2012] if you need to see it. What am I missing, I have clearly searched and searched these great forums (I do love to research, but find I'm at an impasse now) and am not sure what I need to do to proceed. That fruitcake updated my phone to 4.5.91 and I'm pretty sure I was 4.5.2 from the Cherryblur previously.
Thanks for any help!
Update: After getting fruitcake to work, I figured maybe this fixed my previous issues and tried to install CM7 again. Same story, not moving past the first Moto screen. So I tried recovery of the fruitcake and now the M screen comes up, waits a bit, then looks like it's going to load and starts to flash for about a second on, then off for 2-3, then on and so forth. I reflashed fruitcake after this and it is still working as a new install.
You are probably only softbricked. Do you know what "recovery" software you are using? If you are using romracers or one of the better respected recovery software packages, you should be able to use fastboot (if you have a windows machine) to wipe the relevant partitions on your phone and start again. Essentially, you will want to reinstall cherryblur (or install a new ROM - Neutrino, Nottachtrix, CM9s are all excellent) from your sd card. To do this, you will boot to fastboot and run "fastboot -w" from your pc. Then boot to recovery, and wipe cache, and dalvic for good measure, then install cherryblur or another package from the zip file. This will hopefully square you away and get rid of the boot loops.
My guess is that you did not wipe your partitions completely before attempting a new install, and may be having problems with ext3 vs. ext4 formatting between rom versions. Good luck to you.
Thank you for the reply!
Originally I'm pretty sure it was CWM, through the process of backing stuff up I installed Rom Toolbox from market and that seemed to have changed something? (Not sure here...) The text changed color from what I thought was white to blue and it looked a tiny bit different. The only thing I did not do was the fastboot -w, but I did download the link from [Batch] FFW - Fastboot Full Wipe and ran the fastboot from there, which was supposed to do a full wipe from what I read. Fastboot was previously installed on the phone.
I downloaded the 1.1 version which apparently may not be able to wipe the webtop, though when watching the text during the wipe it seemed to go through. Would you recommend me going to romracers, is it possible that my recovery software is borked somehow or just not compatible with the newer roms? If I got to RomRacer will the process of doing that just get rid of the current recovery software I have on the phone or will I run into issues? As far as the dalvik and cache I did run those, though the instructions for the CM7 said to do that after the install which felt backwards....
Oh yes, and I can't reinstall cherryblur, that rom is gone - you can't even download it anymore. I am doing this because I recently purchased a lapdock and the cherryblur was not doing so hot on it so looking to install a good clean rom (with a nice GUI) that works well on the lapdock as well. Yes, I will put an OC'd kernel on it as well, battery life has never been more than a day on my current rom and I am reading that the newer ones have over 1 day life on them so you could say I'd be used to the battery drain on the 1.3 kernels.
I see...that's frustrating. I think given your situation, I would probably not attempt to go from Blur to CM (at least while attempting to get the phone running again). If I were in your shoes, I would do the following...other more knowledgeable folks may steer you in varying directions, but I have been in your shoes before, and this should work. I am assuming you have use of a PC...if not, this won't be helpful.
1. Install ROMRacers recovery using these instructions: http://forum.xda-developers.com/showthread.php?t=1204500
2. Download Nottachtrix 1.3.1 to your SD card using your PC if necessary, and you will probably want to download the webtop 2.3.6 at the same time. These can be found here: http://www.nottachtrix.com/forum/
3. Boot into fastboot (hold volume down on power up, until fastboot appears, then hit volume up, and use a DOS prompt to do the fastboot commands through the USB on your PC), and do a fastboot -w, then fastboot -reboot.
4. This time boot into recovery by holding volume down on powerup, and hitting volume down seven times (I think) until you see the word recovery, then hit volume up.
5. Use recovery to wipe cache partition, then go to advanced and wipe dalvic cache, and then select factory reset/wipe data. Some of these steps may be duplicative, but I am a belt and suspenders kind of guy.
6. Now go to "install from sd card" and select the Nottachtrix build that you put on your external SD, and make selections using the cool Aroma installer. Once this installs, you can install the newer 2.3.6 webtop (if you need it).
7. Reboot when complete, and you should have the latest stock build in working order, and then you can repeat the process to install Neutrino, CM9 or whatever. Feel free to fire back any questions.
Good luck to you, and if this helps, please hit the "thanks" button!
Ill give this a shot when I get home, darn work blocking the download links for mediafire..... The fruitcake is driving me nuts, no notification bar (my biggest complaint) unless I use ADW launcher, which has for some reason no way for me to get into my texts..... Broken apps, and a real stock feel that is just making me grit my teeth lol.
Can't wait to have a nice ROM on my phone again. Glad the fruitcake got me back up and functional though!
So far so good! Had the notification bar problem like others with the 2.3.6 issue and found that fix (disable email notifications....). When / if I can 'thank' I will! And will keep you updated when I get the time to flash another rom.
Good news that you are back rolling again. Let the ROM flashing addiction continue
So, CM7 is pure sexy - and an OC'd kernel to 1.3 makes me so happy in both CM7 and Nottachrix. Wish I would have done it sooner, I wouldn't have been spending so much time searching for a new phone because my atrix was annoyingly laggy. Lag? What is that? Also, undervolting is AMAZING for battery life, for the first time since owning the phone I did not plug it in last night and even though my usage was in the light to medium area, im still at 66% after 22 hours off charger ! Can't wait to play with CM9.
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Thanks for the reply!
I didn't check the MD5 last night but I did just now and it matches.
I did a cache wipe the first time but not a system wipe. Then I started getting more desperate and tried reinstalling w/ system wipes and factory resets, but it didn't change anything.
No, I didn't change the ROM. Doing the Bootloader unlock exploit was about the absolute maximum of my technical abilities! The only thing I know I did wrong was that I didn't downgrade to the old boot version the first time (mainly because the wifi thing sounded inconsequential and I didn't want to learn the procedure if I didn't have to).
Anyway, I just tried Ultimate KangBang and it seems to work--no error messages so far. I don't know what I did wrong, but hopefully this keeps working!
IceDragon59 said:
Even though it explicitly stated you didn't need to do a backup, I did one anyway, to prevent something like this from happening. Always do a backup.
Did you verify the MD5Sum of ViperLTE?
Did you go to Recovery and Wipe -> Factory Reset and Wipe -> System both twice before trying to install the ROM?
Did you change anything in the ROM before attempting to load it?
There are lots of questions we could ask to ascertain the root of the problem, but these three are among the most important.
Wi-Fi won't work without the old boot.img, and from what I can tell, that's the only thing. It doesn't give critical errors.
Click to expand...
Click to collapse
andybones said:
I'm thinking since you are new to root you were un-aware the need to wipe before installing a rom.
im thinking that is the issue.
Click to expand...
Click to collapse
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
franklin411 said:
Yes, I took a short-cut that didn't quite work out. I didn't want to wipe the system because I wasn't sure if my pictures would be wiped too, but then when everything died I tried wiping everything and reinstalling and it didn't seem to improve anything. I did end up losing my pictures too. Oh well. Maybe it's just a combination of stuff I did to try to get things working (there was some trial and error in unlocking the bootloader but I did get that to work finally, and then more trial and error with the ROMs).
I guess the best thing to do is leave the phone the heck alone as long as it's working, for now. I just don't know why nothing seemed to work--I thought factory reset/fresh ROM would do it.
Click to expand...
Click to collapse
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
in the future it is always good practice to backup(nandroid) your current ROM. I have been burned too many times, always do a nandroid before you do anything in recovery.
your photos are normally saved to the SD, flashing ROMs or wiping the system will not delete them
andybones said:
If UKB ROM works then Viper ROM will too, installing the boot.img is very simple it's one command
I can help you with that if you'd like
in recovery before installing ROM, do a wipe of, (I go in this order, but it doesn't matter.)
1) Factory Reset
2) System
3) Cache
4) Dalvik Cache
then install the ROM
just DO NOT do External storage (unless of coarse u WANT to wipe your SD-Card.)
as long as you don't wipe External Storage you won't lose anything that's on your SD-Card.
Click to expand...
Click to collapse
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
franklin411 said:
It worked this time! Maybe the difference was that the boot.img file I downloaded was called "boot_signed.img" or something. I had no idea what it was supposed to look like, so I installed it that way and it didn't work. Then I tried renaming it to "boot.img" this morning and installing viper, but that didn't work. And then I restarted and installed UKB, and it worked. Just now I wiped and tried again with Viper and it's working fine. Maybe I did something this morning that caused it not to take properly when I tried with Viper, and then I reset and it worked.
Thanks for the help!
Click to expand...
Click to collapse
na the name has nothing to do with it. it can be named whatever.
im guessing the wipe worked.
franklin411 said:
Hi all,
I have a Droid incredible 4g (stock, unrooted/unlocked, w/ the recent OTA update). I saw the Bootloader Unlock exploit in the developer's forum so I gave it a go, and it worked fine. Then I installed the Viper 1.0 ROM, but I haven't been able to get it to do anything after successfully booting except run through a loop of errors such as "Unfortunately, the process android.process.acore has stopped working." After I click "OK" on about 10 critical errors, it self-reboots and does the whole thing again.
Unfortunately, I didn't do a backup this time, so I have nothing to restore (first time I haven't done a backup, but also the first time I've ever had any kind of an issue w/ a ROM). I tried using the HTC Android ROM Update Utility 1.0.5.2011 that I found in the dev forum, but that didn't work either. Finally, I installed 2.17.605.2 Verizon Global Sense4.1 Android 4.0.4. It's a lot more stable than Viper was and the phone is basically usable, but I still get lots of critical errors. So this morning I went back to the forum and saw that I needed to downgrade to the old 1.43.605.3 kernel. I tried that and then reinstalled Viper 1.0, but it seemed to have no effect--still stuck in a critical error/reboot loop.
I realize that's the risk of playing with ROMs and I should have done a backup, but anyone have any ideas on how I can get my phone back and running?
Thanks!
Click to expand...
Click to collapse
weird, i was having the same problem with the same processes stopped working. i wiped cache dalvik and system but not factory reset. once i factory reset, it worked fine. i figured a system wipe would have been enough....
I browsed through the general q&a and i am not finding exactly what i am looking for, so please hold the yelling if i missed it. but i am not against being told where to go....
background info....I purchased a DNA off of EBay and i turned it on, and got it going. The SW version is current, stock rooted and the phone is S-Off. The phone still had some of the guys pictures on it, so i jumped in to recovery (CWM touch recovery) and wiped the phone, cache, and restarted. When i did the phone hung, and never booted, so i held the power button down, it then rebooted, checked the apps and all was good. his pics are still on the phone.....going through the phone and wiping (backup and reset) and it's the same thing....
So my question is, what can i do to get the phone back to square one, fully clean but still keep the root and s-off? the reason i am asking is when i wiped it wouldnt boot properly. should i reflash a stock rooted rom? whats the best way to wipe the internal memory? i have rooted and rom'd going back to the original droid, but the HTC's always intimidate me. So please any suggestions they would be welcome. I want to get it stock, then make a perfect good backup, then start trying some roms.....
Thanks in advance!
So I read up a little more, and decided that the best thing to do was Format the SD card. After i did that, i wiped everything again and after it boots, it still just hangs. Then i hold power down and it restarts and i get the "android is upgrading screen" then i am fine. So i am still concerned that it never boots properly. So my question still stands..... should i download another stock rom, or is there something else i should do?
mooseknuckles said:
So I read up a little more, and decided that the best thing to do was Format the SD card. After i did that, i wiped everything again and after it boots, it still just hangs. Then i hold power down and it restarts and i get the "android is upgrading screen" then i am fine. So i am still concerned that it never boots properly. So my question still stands..... should i download another stock rom, or is there something else i should do?
Click to expand...
Click to collapse
if you wipe the phone in recovery ( im assuming /data, /cache, /dalvik, and/or /system) you would have to flash a new ROM on top of that, because you are wiping the entire thing. i dont think you can do a regular wipe in CWM and expect it to boot after that. but, yes, for what you want, formatting /sdcard would probably suffice.
[indiferenc] said:
if you wipe the phone in recovery ( im assuming /data, /cache, /dalvik, and/or /system) you would have to flash a new ROM on top of that, because you are wiping the entire thing. i dont think you can do a regular wipe in CWM and expect it to boot after that. but, yes, for what you want, formatting /sdcard would probably suffice.
Click to expand...
Click to collapse
I don't think cwm wipes the rom by selecting factory reset in it.
Sent from my HTC6435LVW using xda premium
It doesn't, and if he had wiped system it never ever ever would have booted even after resetting it 9001 times.
Wiping data, factory reset, same thing different terms for different versions of recoveries, technically wiping data would delete sdcard with /data/media but usually doesn't. Format SD and a factory reset/data wipe would be what he's looking for, but it not booting afterwards is an issue pointing to something else.
I'd suggest looking at your current ROM version then getting a rooted version and flashing it then seeing if it persists. Any ROM will do, really, I just said that way if you want to stay on that version of sense.
Tapatalked from my HTC DNA - ReVolt
I could use some advice on any options I have for trying to salvage this Rezound. Here is what I know:
The Symptoms:
-Was completely stock and actively used phone
-Charging port began misbehaving. I believe it may be loose/damaged. It will only charge reliably on one particular USB cable (an Amazon Basics, but only one of my dozen or so of those)
-Started randomly rebooting
-Did a factory reset, seemed to help for a while, then it started rebooting again
-It started getting stuck in a bootloop. HTC screen up ~2s -> black ~0.2s -> HTC screen up ~28s -> black ~5s -> repeat. Does this for a variable amount of time, sometimes minutes, sometimes hours before it will actually boot all the way into the OS
-If it does boot, it usually does not last long before it reboots and will typically get stuck again
The Facts:
-I can into bootloader with no issues
-Because I can get into bootloader, I went ahead and unlocked and flashed TWRP 2.6.3.0
-I can get into TWRP and use all of it's functions reliably
-I decided to try wiping data and cache then system several times, flashing a custom ROM (Global_OTA_RED_DESENSED-v1.0) in TWRP and then flashed boot.img with fastboot, but the new ROM has the same issue. In fact I've yet to boot all the way into the ROM
-Does the same thing with the SD card and SIM card removed
My Guesses:
Based on the fact that it is rock solid in the bootloader and in recovery, I thought that it was possibly corruption on system or boot, which is why I tried to install a custom ROM. Now I'm leaning towards bad memory, either where system or boot reside, possibly data or even RAM, perhaps caused by electrical damage from the charge port issues. I just don't understand why I've not seen any sort of read/write errors while doing anything with fastboot or recovery.
At this point I don't know what to do beyond throwing it out. If anyone has any fresh ideas for salvaging this thing, I'd appreciate it.
If not, any ideas for replacing are also appreciated. A new phone isn't really in the budget at the moment, particularly because I desperately want to get away from Verizon (most likely will lose unlimited data if we I start swapping and don't really have $600-$700 to throw around at the moment. I have 4 lines to move and the Rezound line is on contract, so I'm sort of feeling the rock one side and a hard place on the other.
Thanks in advance, folks!
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
acejavelin said:
Because you are staying in ICS at the moment and not playing with JB/KK, try booting up Amon Ra recovery, it has an option to wipe/format the /boot partition (TWRP does not) so wipe that and everything else (except external SD) at lease twice... then, assuming you are on HBoot 2.28 and 0123/0124 radios, flash this and the boot image: http://forum.xda-developers.com/showthread.php?t=2260154 it is a completely stock build with full bloat, only root is added, and see if it comes up. This ROM is my go to ROM for issues when an RUU is not possible.
Click to expand...
Click to collapse
Thanks for the suggestion. I had let the phone sit turned off all afternoon to charge and tried this after work. I grabbed Amon Ra from http://forum.xda-developers.com/showthread.php?p=37362226, made sure to wipe boot in excess and installed the ROM you linked. It booted up on the first try unlike the last ROM, and I've been able to load some things on it and delete some bloat for a bit with no reboots. I've even powered off and went back into recovery to do a backup, and had a successful reboot afterwards. I don't know if it was wiping boot that did it, but I hope it holds. I'll keep you posted, and either way, thanks again.
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
"Haus" said:
Still going. Getting a random reboot here and there, but I've yet to have it get stuck while booting. Now I'm trying to decide if I want to take my chances and try to get S-off.
Click to expand...
Click to collapse
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
acejavelin said:
Are you still on the stock ROM from above? You will need to unlock with Linux if you are, otherwise you will need a custom ROM (actually, an unsecure kernel) to use rumrunner for Windows.
Click to expand...
Click to collapse
I'm still on the stock ROM. Unfortunately it quit booting again.
"Haus" said:
I'm still on the stock ROM. Unfortunately it quit booting again.
Click to expand...
Click to collapse
Hmm... Honestly looking like a hardware issue... Sorry bro
Sent from my Nexus 4 using Tapatalk
Hey All,
I've upgraded my 925F to Official MM 6.0.1. Rooted it through kernel Xspace and then installed recovery TWRP_3.0_MM_S6_by_ManhIT
My only concern is when I'm in TWRP I can't reboot, it just freezes.
I can nandroid backup no problem just the reboot part freezes TWRP.
Anyone else had this problem? is there another TWRP to be used?
nb : I tried clearing cache + dalvik, freezes still happen before rebooting.
thanks for ur help.
kaemon said:
Hey All,
I've upgraded my 925F to Official MM 6.0.1. Rooted it through kernel Xspace and then installed recovery TWRP_3.0_MM_S6_by_ManhIT
My only concern is when I'm in TWRP I can't reboot, it just freezes.
I can nandroid backup no problem just the reboot part freezes TWRP.
Anyone else had this problem? is there another TWRP to be used?
nb : I tried clearing cache + dalvik, freezes still happen before rebooting.
thanks for ur help.
Click to expand...
Click to collapse
Try this TWRP form arter... this is the only TWRP being use by many of us here.. you flash it through odin or recovery...
I had the same problem and i solved changing my kernel
Inviato dal mio SM-G925F utilizzando Tapatalk
fabiok81 said:
I had the same problem and i solved changing my kernel
Inviato dal mio SM-G925F utilizzando Tapatalk
Click to expand...
Click to collapse
The issue is not the kernel... its the recovery that doesn't work when reboot to system is touch and is freezing..
Go to advance then terminal
Write reboot
Easy!
Yes i know the iusse is about the recovery but it seems because there is not compatibility between some recovery and some kernel. I tried various recovery 3.0 and i have always a kind of freeze. The TWRP... by Manhit for example gave me freeze with xspace kernel but not with hacker kernel. I don't no the reason....
Inviato dal mio SM-G925F utilizzando Tapatalk
same but different
Hi All,
I'm experiencing a freeze in TWRP after about a few seconds, the whole recovery stands still and this happens every time.
I flashed the Xspace kernel which hasn't help.
The TWRP from arter97 works great, except it doesn't allow me to copy files to my PC using MTP, message says unexpected error.
yet, the ManhIT and Original TWRP allow me to copy data but both of them freeze up after a few seconds which causing the copying to fail.
Reasons I'm doing this is because my SM-G925F start looping and I've tried flashing stock so many times to no avail.
I'm sure all i need to do is data/ factory wipe and my phone will boot fine, I just really need some data before I do that.
Is there perhaps a different kernel I can try?
or if anyone has any suggestions that would be very much appreciated.
Regards
wahwahward said:
Hi All,
I'm experiencing a freeze in TWRP after about a few seconds, the whole recovery stands still and this happens every time.
I flashed the Xspace kernel which hasn't help.
The TWRP from arter97 works great, except it doesn't allow me to copy files to my PC using MTP, message says unexpected error.
yet, the ManhIT and Original TWRP allow me to copy data but both of them freeze up after a few seconds which causing the copying to fail.
Reasons I'm doing this is because my SM-G925F start looping and I've tried flashing stock so many times to no avail.
I'm sure all i need to do is data/ factory wipe and my phone will boot fine, I just really need some data before I do that.
Is there perhaps a different kernel I can try?
or if anyone has any suggestions that would be very much appreciated.
Regards
Click to expand...
Click to collapse
Try with hacker kernel. Wipe cache but not data
callumbr1 said:
Try with hacker kernel. Wipe cache but not data
Click to expand...
Click to collapse
Thanks for your response callumbr1.
I've attempted two different kernels:
g925-hacker-echoe-kernel-V14.zip
hacker-kernel-S6-Universal-V12.zip
Above mentioned problems persist.
Since arter97 TWRP is not freezing on me, if I run a back up on the Data only. Then perform the wipe, the backup should still be there, correct?
and lets say I flash the stock ROM again if necessary and I'm able to boot the device.
Would it be possible to restore that data back up at all ?
or perhaps copy that back up to my PC and access/extract the files with a separate application?
Many Thanks
wahwahward said:
Thanks for your response callumbr1.
I've attempted two different kernels:
g925-hacker-echoe-kernel-V14.zip
hacker-kernel-S6-Universal-V12.zip
Above mentioned problems persist.
Since arter97 TWRP is not freezing on me, if I run a back up on the Data only. Then perform the wipe, the backup should still be there, correct?
and lets say I flash the stock ROM again if necessary and I'm able to boot the device.
Would it be possible to restore that data back up at all ?
or perhaps copy that back up to my PC and access/extract the files with a separate application?
Many Thanks
Click to expand...
Click to collapse
I think best thing to do is get an otg storage adapter that plugs direct to phone. They are cheap.
Then run the backup of data and store on otg storage. Then you have it safe and it can be restored at a later time with restore option in twrp.
Or you can always do a full nandroid backup.
Can you get onto the phone now? Does it boot up?
Is there anything specific you need off the phone? To be backed up?
callumbr1 said:
I think best thing to do is get an otg storage adapter that plugs direct to phone. They are cheap.
Then run the backup of data and store on otg storage. Then you have it safe and it can be restored at a later time with restore option in twrp.
Or you can always do a full nandroid backup.
Can you get onto the phone now? Does it boot up?
Is there anything specific you need off the phone? To be backed up?
Click to expand...
Click to collapse
I plan on getting one of those, they seem extremely useful. A colleague has one which I plan to use tomorrow if they remember to bring it, I will then do as you suggest.
Never done a full nandroid back up before but will do some searching on that.
Phone still hangs at the Samsung splash screen.
And its really only pictures and some videos that I want, contacts would be nice too.
PS, this happened when I plugged my device into the PC to charge it was at about 5%, and I was making use of side sync to control the device when it just shutdown. I thought maybe the battery died so left it to charge a bit, it eventually tried to boot up by itself and its been looping ever since. Was really strange cause it gave me no issues prior to this. When I tried to get to the recovery it would hang at the "installing updates" section once I flashed the stock ROM I was able to get to recovery to wipe the cache but no luck.
Thanks for your suggestions much appreciated.
wahwahward said:
I plan on getting one of those, they seem extremely useful. A colleague has one which I plan to use tomorrow if they remember to bring it, I will then do as you suggest.
Never done a full nandroid back up before but will do some searching on that.
Phone still hangs at the Samsung splash screen.
And its really only pictures and some videos that I want, contacts would be nice too.
PS, this happened when I plugged my device into the PC to charge it was at about 5%, and I was making use of side sync to control the device when it just shutdown. I thought maybe the battery died so left it to charge a bit, it eventually tried to boot up by itself and its been looping ever since. Was really strange cause it gave me no issues prior to this. When I tried to get to the recovery it would hang at the "installing updates" section once I flashed the stock ROM I was able to get to recovery to wipe the cache but no luck.
Thanks for your suggestions much appreciated.
Click to expand...
Click to collapse
They are really useful, one of the best things ive ever bought regarding my phone. I use it daily now.
As for nandroid backup, it basically backs up absolutely everything including the firmware and data and all partitions. I always do it before flashing or modifying anything. Then if anything goes wrong, you just flash back your nandroid backup.
Can i ask before this happened did you use google photos? If so and sync was on they will all be saved. If you dont use it i reccomend you to use it from now on incase this ever happens in future.
See how you go making the backup when you can then if you need help regarding flashing the stock and getting the phone working ill help
callumbr1 said:
They are really useful, one of the best things ive ever bought regarding my phone. I use it daily now.
As for nandroid backup, it basically backs up absolutely everything including the firmware and data and all partitions. I always do it before flashing or modifying anything. Then if anything goes wrong, you just flash back your nandroid backup.
Can i ask before this happened did you use google photos? If so and sync was on they will all be saved. If you dont use it i reccomend you to use it from now on incase this ever happens in future.
See how you go making the backup when you can then if you need help regarding flashing the stock and getting the phone working ill help
Click to expand...
Click to collapse
Good day callumbr1
I never made use of google photos, not the biggest fan of cloud storage to be completely honest but I do see its benefits when it comes to times like these. lol
as for the device, last night I flashed a custom recovery (arter97) and made use of the SkipSoft Android ToolKit to pull my photos, videos and documents through the adb protocol. That being said, I have the data I wanted so all is well there.
However, after wiping the cache and doing a data / factory reset. I reflashed the stock ROM, it all goes swell until the android pops up with a message displaying " installing system updates". It gets to 32% changes to erasing then restarts , and this happens constantly no matter how many times I flash it or restart the device.
I read on another forum that my devices is probably dead and it could be the mother board. Any thoughts?
You think maybe a custom ROM would bring it up?
wahwahward said:
Good day callumbr1
I never made use of google photos, not the biggest fan of cloud storage to be completely honest but I do see its benefits when it comes to times like these. lol
as for the device, last night I flashed a custom recovery (arter97) and made use of the SkipSoft Android ToolKit to pull my photos, videos and documents through the adb protocol. That being said, I have the data I wanted so all is well there.
However, after wiping the cache and doing a data / factory reset. I reflashed the stock ROM, it all goes swell until the android pops up with a message displaying " installing system updates". It gets to 32% changes to erasing then restarts , and this happens constantly no matter how many times I flash it or restart the device.
I read on another forum that my devices is probably dead and it could be the mother board. Any thoughts?
You think maybe a custom ROM would bring it up?
Click to expand...
Click to collapse
Thats good about your data :good:
As for the little android guy and the installing updates then erasing, this normally happens. It happens every single time i restore and normally boots fine just after its not normally an issue. After yours says erasing does it then just reboot and restart the process of erasing constantly?
What i would suggest first is to flash a different stock ROM, preferably one with newest bootloader.
After flashing, boot to recovery and wipe dalvik cache. If it gets as far as the samsung logo just leave it as the first boot can take a while... like 30 minutes.
If that doesnt work try to flash a custom ROM. I reccomend CarHD ROM. I uave used it for quite some time and no issues.
It deffinately does not sound like motherboard issue. Normally you would have many issues and errors on boot prior to having main board issues.
See how you get on and keep me updated.
callumbr1 said:
Thats good about your data :good:
As for the little android guy and the installing updates then erasing, this normally happens. It happens every single time i restore and normally boots fine just after its not normally an issue. After yours says erasing does it then just reboot and restart the process of erasing constantly?
What i would suggest first is to flash a different stock ROM, preferably one with newest bootloader.
After flashing, boot to recovery and wipe dalvik cache. If it gets as far as the samsung logo just leave it as the first boot can take a while... like 30 minutes.
If that doesnt work try to flash a custom ROM. I reccomend CarHD ROM. I uave used it for quite some time and no issues.
It deffinately does not sound like motherboard issue. Normally you would have many issues and errors on boot prior to having main board issues.
See how you get on and keep me updated.
Click to expand...
Click to collapse
It doesn't say erasing after the first time. Right after the flash it will reboot to the blue screen with the android, it displays Installing update with a percentage bar which gets to 32% then that disappears and shows erasing, then again it shows installing update with no percentage bar. The android guy has a two arrows on his chest spinning which eventually stops. The device then reboots. It goes back to the Android guy but this time it shows "installing system update" without the percentage bar, it will then freeze again then reboot. That will continue forever until the battery dies.
After flashing though I can't seem to get to recovery to wipe the cache, I hit the buttons as I always do, but the blue screen and android always appears.
This is the stock ROM I'm currently using:
https://www.sammobile.com/firmwares/download/105085/G925FXXU4DPJB_G925FXFV4DPJ2_XFV/
Do you perhaps have a link to that custom ROM? would it work fine with the service provider here in SA (Vodacom) ?
And well at least that is some good news, I'm not too keen on having to take this into a shop and pay for parts.
wahwahward said:
It doesn't say erasing after the first time. Right after the flash it will reboot to the blue screen with the android, it displays Installing update with a percentage bar which gets to 32% then that disappears and shows erasing, then again it shows installing update with no percentage bar. The android guy has a two arrows on his chest spinning which eventually stops. The device then reboots. It goes back to the Android guy but this time it shows "installing system update" without the percentage bar, it will then freeze again then reboot. That will continue forever until the battery dies.
After flashing though I can't seem to get to recovery to wipe the cache, I hit the buttons as I always do, but the blue screen and android always appears.
This is the stock ROM I'm currently using:
https://www.sammobile.com/firmwares/download/105085/G925FXXU4DPJB_G925FXFV4DPJ2_XFV/
Do you perhaps have a link to that custom ROM? would it work fine with the service provider here in SA (Vodacom) ?
And well at least that is some good news, I'm not too keen on having to take this into a shop and pay for parts.
Click to expand...
Click to collapse
Thats pretty much exactly what happens to mine after restoring or flashing but mine boots up.
Flash the firmware again but in odin options uncheck auto reboot. This time after flashing, the phone should stay off. Then you can boot to recovery.
If that doesnt work, whilst it is on the blue screen with android guy hold only vol down and power, phone will reboot, as soon as the screen goes off switch to recovery combo and this should force it to recovery.
https://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519/page1427
Here is the link to custom ROM, it will work fine on your phone. You need to flash this through TWRP. If you need steps on how to do this please tell me.
callumbr1 said:
Thats pretty much exactly what happens to mine after restoring or flashing but mine boots up.
Flash the firmware again but in odin options uncheck auto reboot. This time after flashing, the phone should stay off. Then you can boot to recovery.
If that doesnt work, whilst it is on the blue screen with android guy hold only vol down and power, phone will reboot, as soon as the screen goes off switch to recovery combo and this should force it to recovery.
https://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519/page1427
Here is the link to custom ROM, it will work fine on your phone. You need to flash this through TWRP. If you need steps on how to do this please tell me.
Click to expand...
Click to collapse
Man I think I'm just going to try the custom to see if it works.
Would I need to flash a custom kernel or can it be stock?
After flashing the kernel with twrp I'm going to assume I would follow the same step.
1. flash TWRP custom recovery
2. copy .zip file to sdcard
3. go to recovery, install , select the .zip
Is that it or am I missing anything else when it comes to flashing ROMs through the recovery?
wahwahward said:
Man I think I'm just going to try the custom to see if it works.
Would I need to flash a custom kernel or can it be stock?
After flashing the kernel with twrp I'm going to assume I would follow the same step.
1. flash TWRP custom recovery
2. copy .zip file to sdcard
3. go to recovery, install , select the .zip
Is that it or am I missing anything else when it comes to flashing ROMs through the recovery?
Click to expand...
Click to collapse
Thats it.
Before installing rom go to wipe in TWRP, wipe data, dalvik, cache and system.
You dont need to flash a kernel though.
However when flashing carhd rom aroma installer will go through some choices, from there you can choose to install arter kernel. I reccomend doing this rather than keeping stock kernel.
Remember once installer complete and rom is installed leave it a while if it hangs on samsung logo screen. It can take a while to boot.
callumbr1 said:
Thats it.
Before installing rom go to wipe in TWRP, wipe data, dalvik, cache and system.
You dont need to flash a kernel though.
However when flashing carhd rom aroma installer will go through some choices, from there you can choose to install arter kernel. I reccomend doing this rather than keeping stock kernel.
Remember once installer complete and rom is installed leave it a while if it hangs on samsung logo screen. It can take a while to boot.
Click to expand...
Click to collapse
Currently waiting on the custom to download, don't have the quickest internet connection.
while I've been waiting, I've tried the stock ROM again.
something I forgot to mention before, which has happened a few times:
During the blue screen with the droid stating installing updates.
it switches to a screen with a big yellow triangle two dots below it and a dead droid.
After this I get to recovery, I wiped the cache and its getting to the samsung logo but freezes and then restarts all over again.
I'm just curious if you know what the yellow triangle thing means?
wahwahward said:
Currently waiting on the custom to download, don't have the quickest internet connection.
while I've been waiting, I've tried the stock ROM again.
something I forgot to mention before, which has happened a few times:
During the blue screen with the droid stating installing updates.
it switches to a screen with a big yellow triangle two dots below it and a dead droid.
After this I get to recovery, I wiped the cache and its getting to the samsung logo but freezes and then restarts all over again.
I'm just curious if you know what the yellow triangle thing means?
Click to expand...
Click to collapse
I think it normally means a failed update. Sometimes there are instructions to use smart switch other times it just means the update failed.
Try with the custom ROM and keep me updated.