hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
did you not wipe system and data? I am not super skilled, but maybe it tried to stick the entire ROM into the left over space of the last ROM that is still on there?
It won't boot to recovery? It should boot to recovery
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
Click to expand...
Click to collapse
The error message you received is going to be the key to understanding the issue that occured. When it says unmounted, it is referring to a specific partition, either /data or /system most likely.
For starters, when it hangs on the htc white screen, this is usually either a kernel or ramdisk issue. If the kernel is known to be good, then it is probably a ramdisk issue. most ramdisk issues relate to a mismatch/incompatibility between the loaded kernel and the ROM.
First suggestion would be to reflash the ROM, clearing /cache and /data.
Second suggestion would be to restore a backup. This will confirm there is nothing wrong with your device hardware wise and you'll know it is a specific issue with the ROM you wanted to load.
Third suggestion, find the exact error, word for word, which occured in recovery and post up in the ROM thread asking if other users of that ROM also encountered, how they handled. Also feel free to post back up here.
When writing the programming behind a custom recovery, the error messages are added in there to help allow users and developers better knowledge of the exact issue so they can work to resolve them. Without the exact error message, it is similar to going to a car shop and saying, some light came on my dash, but I don't know what it was and now the car doesn't work. Fix it? Another words, it is very vague.
Hope the suggestions and tips help! Good luck!
my first instinct was to reflash the backup or new rom again but it wont boot to any rom, recovery or bootloader. it just hangs on the htc white screen
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
weezymagic said:
idk what happened but i got into the bootloader through battery pull, power+vol down. i know ive tried that in the past but this time it worked. now im restoring a nandroid from yesterday
Click to expand...
Click to collapse
are you on twrp 1.0.x ? There is s charging issue where it won't restart right because it thinks It's already in recovery
sent from my EVO 3D via XDA app
weezymagic said:
hey guys, been here since the launch of evo. rooting, flashing, everything.
today i wanted to switch roms. so i went about my normal process...
d/l new ROM
backup current ROM
backup apps
wipe cache and dalvic
flash new ROM
i got stuck on the last step. i went to flash the new ROM (nocturnal 1.3)
it said something along the lines of blah blah is already unmounted. i didnt pay too much attention to it because i was going to restart and try again. long story short, it will only boot to htc white screen and nothing else.
can anyone help me out?
p.s. im on clockwork recovery
PLEASE CLOSE
Click to expand...
Click to collapse
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Twolazyg said:
You missed a step. After you wipe dalvik and cache, you ALWAYS need to wipe /system and /data, do a factory reset to make sure, or download a superwipe tool. The ONLY time you don't need to wipe completely is when you're updating your ROM, but even then it is recommended to wipe everything.
Click to expand...
Click to collapse
Agreed^^^^^
Related
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
venkavis said:
I had a working Cyanogen 7 flashed on the gTablet. And due to enthusiasm, I updated with one of the nightly builds and started seeing some issues.
I assumed that clearing the cache and rebooting would help and ended up doing the 'Wipe Cache Partition'. Now the tablet wont boot at all. But I guess its not bricked at all since I am able to get to CWM.
What do I need now to get back to CM7?
Also my search on what the 'wipe cache partition' function doesn't give me the full picture. Now I know that I shouldn't have done it in the first place. But being affected by it I request if one the Gurus on XDA's please shed some lite.
Regards and thanks for the help in advance.
Click to expand...
Click to collapse
Hopefully a guru can answer this question. A guru I am not..
But what I think you did should not be an issue. I typically wipe data and then wipe cache partition when flashing a new ROM. sometimes I wipe cache and data just to get the ROM running from scratch again. But this should not affect booting..
One thing I think might be the problem is that you have a new kernel from one of the newer nightlys. Recently they added perhsoots May kernel. Whenever a new kernel is included in a nightly you usually need to clear dalvik cache. this is in CWM under advanced.
I hope this helps.
Tried clearing dalvik cache. No change.
Going back to stock and see.
Copied the stock ROM file and used the CWM to do the update. Now the g Tablet is gioing into a Boot loop. It Tap n Tap then displays a animated icon and after a minute repeats the same.
Tried the recovery option and its going into an installing loop again. Not sure how to get out of this.
Does anybody have this experience before?
Is this bricked now? Call viewsonic support? I am not sure if they support, They may say its nor under warranty.
Just to remind you, the last effort to resolve this is to NVFLash it...
Have you tried CWM method twice or repartition it and do it again? It's a tablet for you to enjoy your Internet, reading, video but not flashing all day long..etc
To pass it quick, if I were you, I would NVFlash it back to 3588, put back my favorite ROM, reinstall the Apps I like and start Internet browsing, converting movie (so I can watch on the road), reading news...
good luck!
rcjpth
After this I definitely agree. But seems I am stuck again. Hope this is the last time.
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Called Viewsonic support and the tech support person pointed me to below post on XDA
http://forum.xda-developers.com/showthread.php?t=1036956
When I read the article it talks about a locked boot loader. Does is mean if I use this and fix the tablet, I will not be able to do any more rooting?
venkavis said:
I followed the steps as in the below URL
http://forum.xda-developers.com/archive/index.php/t-1040434.html
My PC successfully connected to the gTablet and did the bvflash. After that I booted, it still went into the same. I am not sure if the nvflash worked at all.
Not sure what I am missing here!
Click to expand...
Click to collapse
So you also tried the alternate file, nvflash_gtablet_46_2010112600.zip? That's what worked for me, but I also have to swap partitions 7 & 8 to get CM7 working again.
Since I'm a glutton for punishment, I wiped my cache from nightly 75 and didn't run into any problem.
Just downloaded the alternate zip and flashed again. Having the same looping issue.
Seems like I Have to send it to viewsonic only. The technician said there is a $75 charge to fix.
I have finally got my phone unlocked and rooted. Now I am trying to install the quicksense ROM. I know I am doing something wrong, because all I get is the white HTC screen at start up, and thats as far as it goes. So, here is what I did, and maybe someone can help me out.
I downloaded amazing quicksense and dragged it into my sd card
I booted into recovery
I did a backup
I wiped the cashe
I went to install from sd card and chose the zipped quicksense file
I then got install from sd card complete
I then went back and rebooted phone
From here the phone freezes on the white HTC screen and does not fully boot.
I had to go back into recovery and do a restore to get my phone working again.
What am I doing wrong. Please help.
Seem like you did succeed at everything except the cleaning parts
Please try again by going into recovery and
1. wipe data/factory reset
2. Wipe cache partition
3. Go to Advance then wipe dalvik cache - after that, choose go back
4. Install rom from sdcard
5. Reboot
I will try and do what you have instructed. However I wanted to ask one question before I do this. In your first step to "wipe data/factory reset", will this reset my phone back to factory, essentially wiping all my data and everything I have on it? I know unlocking the bootloader did that, but it would suck if I had to do this every time I installed a ROM. Just want to make sure what I am up against. Thanks
ms2knights said:
I will try and do what you have instructed. However I wanted to ask one question before I do this. In your first step to "wipe data/factory reset", will this reset my phone back to factory, essentially wiping all my data and everything I have on it? I know unlocking the bootloader did that, but it would suck if I had to do this every time I installed a ROM. Just want to make sure what I am up against. Thanks
Click to expand...
Click to collapse
Hi
I am by no mean a dev so my advices is more like ... well, advice - not instructions my friends
Wipe data/factory reset mean wiping every personal datas that you had on the device and yes, this will reset your phone back to the present rom that you had on the device - in your case is the stock/factory/carriers rom.
Every time you install a new rom you should - and every dev will suggested this - wipe clean your data and whatever info that may still left on the device from previous rom - you may not need to do this when you update to the new version from the same rom. Sometimes the new version of the same rom featured too many changes then the dev will instructed user to wipe all the data. That's why we user should always read the first, second and third post to make sure we keep ourself up-to-date when flashing rom.
Personal data means your google account, emails, contact list, SMS, wifi password, bluetooth pairing and apps setting ... However, we can backup and restore most of these info using diferrent apps. Here are some app that I found helpful in term of backup:
* Gmail account for contacts list
* SMS backup for SMS and call log
* Titanium Backup for apps and it's data: This app is very useful, for example if you use it to backup your email app it will included your setup and password ect ... so after install new rom and restore a particular app, you have an option to restore the app plus it's data or data/app only
Read this thread for some useful tips on how to using Titanium Backup
http://forum.xda-developers.com/showthread.php?t=1324291
Googd luck and welcome to the Amaze
I really do appreciate your advice. I will go ahead and backup everything, and then attempt the ROM install again. Hopefully it will work this time. Again thanks.
Not a problem mate
Since you already backup your rom and QuikSense is a Sense rom anyway, it doesn't hurt to try restoring data from the backup. You can do this (after finish flashing the new rom) by go back into Recovery/Backup and restore/Advance restore/choose the backup file (in case you have more than 1 backup)/then chose restore data
I did this when switching from QuikSense rom to Senseless Rom and it work flawlessly
Worst case scenario is you will have to restore again. This will save a lot of steps.
ms2knights said:
I have finally got my phone unlocked and rooted. Now I am trying to install the quicksense ROM. I know I am doing something wrong, because all I get is the white HTC screen at start up, and thats as far as it goes. So, here is what I did, and maybe someone can help me out.
I downloaded amazing quicksense and dragged it into my sd card
I booted into recovery
I did a backup
I wiped the cashe
I went to install from sd card and chose the zipped quicksense file
I then got install from sd card complete
I then went back and rebooted phone
From here the phone freezes on the white HTC screen and does not fully boot.
I had to go back into recovery and do a restore to get my phone working again.
What am I doing wrong. Please help.
Click to expand...
Click to collapse
How long do you wait?
The first boot may take several minutes.
Do you have adb installed on your computer? If so then from the command prompt (or terminal if your running Ubuntu) type "adb shell logcat" and if it seems like it's repeating itself over and over again then your caught in a loop and would probably just need to clear the data and caches. Your problem should clear right up.
Binary100100 said:
How long do you wait?
The first boot may take several minutes.
Do you have adb installed on your computer? If so then from the command prompt (or terminal if your running Ubuntu) type "adb shell logcat" and if it seems like it's repeating itself over and over again then your caught in a loop and would probably just need to clear the data and caches. Your problem should clear right up.
Click to expand...
Click to collapse
To be honest with you, I did wait for maybe 5 min or less. I guess I thought it would boot normally. I will try again and give it some time.
Being very new to this, I am trying to learn all of this. How do I know if I have adb installed on my computer? Thanks
ms2knights said:
To be honest with you, I did wait for maybe 5 min or less. I guess I thought it would boot normally. I will try again and give it some time.
Being very new to this, I am trying to learn all of this. How do I know if I have adb installed on my computer? Thanks
Click to expand...
Click to collapse
Follow the instructions on this thread here:
http://forum.xda-developers.com/showthread.php?t=928370
Easiest way to set up ADB.
Hope this helps.
Well, I finally got it to work. My probem was that my sd card was not FAT32 but FAT. I think this was the problem I had with trying to flash clockworkmod. I did everything except the wipedata/factory rest, to see if it would work. And sure enough, I am now running Amazing Quicksense 1.5.1. Thanks for every ones help.
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
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.