ATT Padfone X, KK 4.4.2. It rooted fine, installed SuperSU, and ran great until I manually edited for the SD write. After reboot it started crashing everything after it booted up. the phone part and mms part work fine, but everything else just crashes. Couldnt get back to Super SU to unroot, Couldn't access the SD, or even the files on the phone. Tried a factory reset from within the OS, no luck. Tried a factory reset from cold boot, no luck. Tried to access the SD from cold boot, no luck. Is there any way to reflash this phone to stock?
mr_honez said:
ATT Padfone X, KK 4.4.2. It rooted fine, installed SuperSU, and ran great until I manually edited for the SD write. After reboot it started crashing everything after it booted up. the phone part and mms part work fine, but everything else just crashes. Couldnt get back to Super SU to unroot, Couldn't access the SD, or even the files on the phone. Tried a factory reset from within the OS, no luck. Tried a factory reset from cold boot, no luck. Tried to access the SD from cold boot, no luck. Is there any way to reflash this phone to stock?
Click to expand...
Click to collapse
Yes, if you have TWRP installed. See my thread in development about stock nandroid backups.
dibblebill said:
Yes, if you have TWRP installed. See my thread in development about stock nandroid backups.
Click to expand...
Click to collapse
Dibblebill you are awesome, thanks for the heads up on that! Before I read your reply I ended up taking it in today and they warrantied it no questions asked. I assume the phone was so borked that they couldn't determine it had been rooted. But I downloaded your backups and instructions in case I decide to root and SD fix it again in the future. Thanks again man, i appreciate your help.:good:
Related
So here is one for ya.
I can't access my SD Card at all with this http://forum.xda-developers.com/showthread.php?p=25816870#post25816870 rom installed. I click to mount SD card and nothing happens. In recovery I can access the SD card backups etc
I find it strange. Although I do have to ask, I have been having this weird problem. I have Clean Rom 4.3 Installed (ICS) and I have been getting some random reset's and slow this or that. So I saw 4.5 was out - It literally reset everyime your open something and I mean anything Bam reset. However I installed the above rooted bleh bleh stock os (I do not have s-off so I used the PH img) I made sure I had no other boot images on there. Installed setup got everything ready. I have gotten 3 resets in 11 mins so far so now I backed up to Clean rom 4.3 and I have no idea what to do.
I also did the following:
Flashed back to STOCK o.s.
Then Downloaded the above linked rom, cleared data (everything) installed software patch and rom reset back up and same problem. I have been flasing rom's on this phone for a while now and this is the first time no matter what that I get these crashes and resets. Did I miss something?
You really should s-off that puppy. It is pretty easy, and will get you out of messes.
Sent from my ADR6425LVW using Tapatalk 2
Jason L said:
So here is one for ya.
I can't access my SD Card at all with this http://forum.xda-developers.com/showthread.php?p=25816870#post25816870 rom installed. I click to mount SD card and nothing happens. In recovery I can access the SD card backups etc
I find it strange. Although I do have to ask, I have been having this weird problem. I have Clean Rom 4.3 Installed (ICS) and I have been getting some random reset's and slow this or that. So I saw 4.5 was out - It literally reset everyime your open something and I mean anything Bam reset. However I installed the above rooted bleh bleh stock os (I do not have s-off so I used the PH img) I made sure I had no other boot images on there. Installed setup got everything ready. I have gotten 3 resets in 11 mins so far so now I backed up to Clean rom 4.3 and I have no idea what to do.
I also did the following:
Flashed back to STOCK o.s.
Then Downloaded the above linked rom, cleared data (everything) installed software patch and rom reset back up and same problem. I have been flasing rom's on this phone for a while now and this is the first time no matter what that I get these crashes and resets. Did I miss something?
Click to expand...
Click to collapse
I assume you're always wiping data and cache.
Have to tried Fix Permissions? I don't know if this rom has it in it's settings, but using others I've corrected some weirdness by wiping the cache and then running fix permissions.
Were you seeing the same thing with the stock rom? Or just using clean rom? Might try a different rom for a bit to see if the issues follow you there.
S-OFF isn't going to help you with this. It's perfectly fine to flash your boot image outside of Aman-Ra. I do it all the time.
Are you wiping everything between flashes?
I recommend using this - http://forum.xda-developers.com/showthread.php?t=1562176&highlight=clean
Flash it first and it wipes the needed partitions clean.
If you're still on the GB firmware, you need to flash the old firmware patch after the rom install also to get SD card access.
If none of the above helps and you're still on the GB firmware, set the phone back to stock using the GB RUU, otherwise you will have to s-off it so you can do the same.
Yep full wipes between flashes. I didn't keep the stock Rom for more than about 20 mins.
I didn't see a way with the debloated stock New leak to fix permissions. But with the 4.5 clean Rom I did that and it made no difference.
Delete
Sent from my ADR6425LVW using Tapatalk 2
I've been trying to root my wife's HTC Rhyme and in my efforts, something hosed the WiFi. All I get is "ERROR" under WiFi in the wireless network settings menu. This happened to me once or twice on my incredible and a kernel re-flash fixed it. I really want to root it so that she can have the benefit of being able to completely backup everything. I've tried ZergRush, TocoRoot, SuperTool, OneClick, SuperOneClick... none of it worked. The only thing that I've been able to do successfully is unlock/re-lock the bootloader.
Is it possible to extract the ROM and/or all critical system files from a stock rooted phone and use them to restore another phone that is malfunctioning? I was thinking that if I found someone with a rooted HTC Rhyme who would be willing, they could send me whatever files I would need to completely restore the phone, WiFi and all.
Any help with at least the WiFi issue wold be appreciated. Rooting would be nice too but I don't want to be greedy.
Thanks.
I was able to install an RUU which fixed the WiFi issue, but now the phone is stuck in a boot-loop. I've flashed it three times (doing it twice each attempt) but its the same result every time. The phone boots normally the first time, then goes into loop on the next restart. Could be the wrong RUU, could be corrupted or maybe I'm doing it wrong. I don't know.
Please... Any suggestions would be most appreciated.
I fixed it.
RuLEoF2 said:
I fixed it.
Click to expand...
Click to collapse
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks!
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
RuLEoF2 said:
itandy said:
So have you finally rooted your Rhyme successfully? Which tool did you use? Thanks![/QUOTE No root, but it's working and back to No root, but it's working and back to factory condition. factory condition.
I used CWM recovery to format all partitions I used CWM recovery to format all partitions (data, system, cache, devlog, etc.) as well as (data, system, cache, devlog, etc.) as well as the sdcard. the sdcard. Once that was done, I relocked the Once that was done, I relocked the bootloader and ran the RUU. bootloader and ran the RUU. This time I went This time I went through the entire setup process for the phone through the entire setup process for the phone (activation, market account, WiFi and so on) (activation, market account, WiFi and so on) without rebooting first. without rebooting first. After the setup, I After the setup, I rebooted and I started normally. rebooted and I started normally. About 20 About 20 minutes later, I got an android OTA update of minutes later, I got an android OTA update of some kind and now its fine. some kind and now its fine.
Not sure why setting up the phone would make Not sure why setting up the phone would make a difference, but formatting the partitions and a difference, but formatting the partitions and going completely clean-slate is probably what going completely clean-slate is probably what did the trick. did the trick. Something must have been stuck Something must have been stuck in memory from the first failed attempt and it in memory from the first failed attempt and it was corrupting the following attempts in some was corrupting the following attempts in some way. way.
I'd still like to root it, but anyway... it's fixed and I'd still like to root it, but anyway... it's fixed and my wife's is glad to get her phone back. my wife's is glad to get her phone back. Happy Happy ending. ending.
Thanks to all for your assistance.
Click to expand...
Click to collapse
How did you get the ruu to run i keep getting a error 140 wrong bootloader version i tried ruu 1.26.605.11 and 1.26.605.6 i attempted to flash a ics rom and the phone got stuck on the splash screen so then i used my backup i made before i flash the ics rom and wouldnt boot so i extracted the boot.img from the ruu and flashed it to get the phone back up and running the phone is still rooted but i have no wifi no bluetooth no cam i been searching everywhere for a rhyme kernel bt no luck if anyone could help that would great
Click to expand...
Click to collapse
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....
Hey all.
So just a few hours ago, I was running rooted stock, as per the guide in the development section. I then installed twrp, and attempted to flash a ROM, which resulted in my phone not booting.
Since then, I got into recovery, attempted a factory reset (which didn't work), and ended up using Odin to restore to stock.
So now I'm sitting on the stock image, unsure if I have root. Everything seems to work fine, but is slow. Also, I cannot enable wifi (the switch goes on for a split second, then back to off).
Is there a way I can uninstall twrp, and go back to complete and total stock?
If it's relevant, I get a constant "This device has detected an application attempting unpermitted actions..." error.
Thanks guys!!!
UPDATE: It still has root access.
UPDATE 2: I'm finding some similar issues people were having with the T-Mobile version (http://androidforums.com/t-mobile-g...connect-wifi-prevention-information-help.html) though I'm not sure whether I can follow those solutions. I will wait until someone can advise me on this.
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
wolfgrrl said:
It sounds like you didn't installed the complete stock image, that the stocked rooted image is installed. Have you done factory reset?
Click to expand...
Click to collapse
I tried the factory reset option from within twrp recovery, which doesn't fix any of these issues I'm having with constant security alerts or Wifi.
Got it fixed by doing this:
http://forum.xda-developers.com/showthread.php?t=2301259
So I originally had issues with my S4 when it updated to 5.0 I got a new one from the inusrance company and i wanted to root and rom it right away. Well it took me a wile to root it, I had to find the right (or what I thought was the right) Kernel's to use. I rooted it finally with Towelroot, I then tried to install TWRP and reboot to recovery and load a Rom, however my phone will never reboot to recovery now. It will only reboot to download. TWRP does not seem to work and if I mess it with it it will reboot to download and it won't do anything ells until I use Odin to reinstall the Kernel. If I try the button combo to reboot to recovery it still reboots to download. So I think that keeps me from using SafeStrap as well.
I am at a loss, I just want to get the Hyperdrive+RLS21+KK+S4 Rom on my phone so I don't get the stupid 5.0 that ruins my phone. Is there anyone who can help me out with this? Also I did try to do a factory data reset and that did not work either as it just rebooted to download and I had to use Odin to load the Kernel again and it just rebooted to the same un-reset OS I was in.
Brad
Bshade said:
So I originally had issues with my S4 when it updated to 5.0 I got a new one from the inusrance company and i wanted to root and rom it right away. Well it took me a wile to root it, I had to find the right (or what I thought was the right) Kernel's to use. I rooted it finally with Towelroot, I then tried to install TWRP and reboot to recovery and load a Rom, however my phone will never reboot to recovery now. It will only reboot to download. TWRP does not seem to work and if I mess it with it it will reboot to download and it won't do anything ells until I use Odin to reinstall the Kernel. If I try the button combo to reboot to recovery it still reboots to download. So I think that keeps me from using SafeStrap as well.
I am at a loss, I just want to get the Hyperdrive+RLS21+KK+S4 Rom on my phone so I don't get the stupid 5.0 that ruins my phone. Is there anyone who can help me out with this? Also I did try to do a factory data reset and that did not work either as it just rebooted to download and I had to use Odin to load the Kernel again and it just rebooted to the same un-reset OS I was in.
Brad
Click to expand...
Click to collapse
You do know that OC1 is still locked down(5.0.1)?
No root, no downgrade, no ROMs, no safestrap. No TWRP unless you happen to have MDK(4.2 Jellybean)
You will have to flash a stock 5.0.1 ROM and life with it.
I had an S4 that did upgrade to OC1 I got a new S4 with my insurance that was not upgraded to OC1 it was still 4.4.2 NK1. I loaded the Kernel NC5 and used Towelroot then back to NK1 but I cant get TWRP to work and boot to recovery to flash the ROM it only boots to Download. I really want to ROM it so that it does not go back to OC1 as when it was OC1 on my old phone that I don't have it was useless, I could not make phone calls or install anything on the phone or it would just lock up and restart constantly.
I can not figure out why it won't boot to recovery, and why if I try to do a factory reset i have to reload the Kernel to make the phone work again.
Thanks,
Brad
THIS IS A TEST PROCESS!!
I just posted a set of service files to try and downgrade...I pretty sure it might work! [emoji14]
http://forum.xda-developers.com/galaxy-s4-verizon/help/testing-revert-to-nk1-t3124096
It Worked! now I just have to figure out how to re root I tried once with Towelroot and it did no work then tried to load the Kernel that Towelroot worked with and it got all bugy so i reloaded your Kernel and it was still bugy so I did the whole process over again and it worked a second time. LOL
Thanks so much,
Brad
Bshade said:
It Worked! now I just have to figure out how to re root I tried once with Towelroot and it did no work then tried to load the Kernel that Towelroot worked with and it got all bugy so i reloaded your Kernel and it was still bugy so I did the whole process over again and it worked a second time. LOL
Thanks so much,
Brad
Click to expand...
Click to collapse
TWRP will not work on anything above 4.2.2(MDK). You have to use Safestrap.
Do a FULL wipe to nc5, not the workaround. THEN towelroot, install Busybox(IMPORTANT) and Safestrap(modded version of TWRP SPECIFICALLY for devices with locked Bootloader), install Hyperdrive or ROM of choice.
Well I got all the way through, I got the Safestrap to work and boot to recovery. I did a wipe factory reset and wipe cache and Dalvik. I then try to install rom, now it says to install in a working and setup rom slot? I think that is where I have and issue. If I just try the instal it does not work as I get the error "no MD5 file found" and then "error flashing zip" Do you think this is due to the wrong Rom Slot or am I missing something that I am not doing?
Thanks so much for your help so far, I am so close and at the very last step in this whole ordeal, or at least I hope.
Brad
Bshade said:
Well I got all the way through, I got the Safestrap to work and boot to recovery. I did a wipe factory reset and wipe cache and Dalvik. I then try to install rom, now it says to install in a working and setup rom slot? I think that is where I have and issue. If I just try the instal it does not work as I get the error "no MD5 file found" and then "error flashing zip" Do you think this is due to the wrong Rom Slot or am I missing something that I am not doing?
Thanks so much for your help so far, I am so close and at the very last step in this whole ordeal, or at least I hope.
Brad
Click to expand...
Click to collapse
hmmmmmmm
Did you put the ROM on the SD card. Make sure to use the STOCK ROM SLOT!!!
Yeah, both of those things. On the SD card as a zip file and the stock ROM slot. I did try last night to flash another ROM quick to see if it would work and I got the same error so I don't think its my ROM but something I am doing wrong on the phone.
Thanks for your all your help so far,
Brad
Finally got it, took some time and lots of rework. I soft bricked it so many times I cant count them. I got this down though now, I am just playing with the rom to see what setup I like now.
Thanks so much again for your help.
Brad
Bshade said:
Finally got it, took some time and lots of rework. I soft bricked it so many times I cant count them. I got this down though now, I am just playing with the rom to see what setup I like now.
Thanks so much again for your help.
Brad
Click to expand...
Click to collapse
I think we have all been there at some point. Good job getting it all going. Takes some patience and effort. Don't forget to have some fun!
Sent from my SCH-I545 using XDA Free mobile app