OK. So I soft bricked my phone earlier, and just restored by flashing the RUU. Now that I'm trying to root back, I'm noticing that my file system is totally different from what it used to be. TWRP actually says no OS is installed, but the stock version of 4.4.2 is most certainly there and boots just fine. How can I rectify this?
UPDATED: There was actually no problem with the file system. It appears I likely had a bad download of TWRP so it wasn't recognizing the mount points.
MarkBell said:
OK. So I soft bricked my phone earlier, and just restored by flashing the RUU. Now that I'm trying to root back, I'm noticing that my file system is totally different from what it used to be. TWRP actually says no OS is installed, but the stock version of 4.4.2 is most certainly there and boots just fine. How can I rectify this?
Click to expand...
Click to collapse
What version of TWRP do you have installed? 2.7.1.1 wipes OS version from bootloader, but that doesn't affect anything. If you want OS to be shown flash TWRP 2.6.3.3. It's the most stable recovery and you won't have problems flashing ROMs with it. On the other hand, if your phone works fine, leave it as it is
Powered by non removable 2300 mAh battery
donkeykong1 said:
What version of TWRP do you have installed? 2.7.1.1 wipes OS version from bootloader, but that doesn't affect anything. If you want OS to be shown flash TWRP 2.6.3.3. It's the most stable recovery and you won't have problems flashing ROMs with it. On the other hand, if your phone works fine, leave it as it is
Powered by non removable 2300 mAh battery
Click to expand...
Click to collapse
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
MarkBell said:
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
Click to expand...
Click to collapse
I wanted to add, the only partition showing as mounted in TWRP is the Data. Can't mount cache or system. Going to restore shows my internal storage at 37 MB. Going to file manager shows I am in the folder "/." In this folder are a boot, cache, data, deve, etc, license, proc, recovery, res, root, sbin, sdcard, supersu, sys, system, tmp, usb-otg, default.prop, file_contexts, fstab.goldfish, fstab.qcom, init, init.rc, init.recovery.qcom.rc, property_contexts, seapp_contexts, sepolicy, ueventd.goldfish.rc, ueventd.rc. Most of these have nothing in them. SuperSu does have a Superuser.apk inside, but its not the SuperSu file I downloaded from Chainfire's page, and with only Data being mounted I'm afraid to flash the default one.
The other funny thing is that when I go to reboot system in TWRP, it says that no OS is installed, but like I said, the stock system boots just fine. I believe everything on my phone is installed to Data.
MarkBell said:
It was actually tdhite's 2.7.1.3 that I flashed that really screwed up my phone.
I was using 2.7.1.1 fine before. I flashed back to 2.7.1.1 after getting my phone working again with the RUU. I have a full backup of my rooted phone saved to my computer and would love to be able to restore it back through TWRP. But the actual filing system in ES File Explorer looks different.
In TWRP, I can't even get to SuperSU to become root because of the way the file system is so different.
When I was soft bricked, I may have played around in the Mount function of TWRP and screwed it up that way.
Click to expand...
Click to collapse
The file system has not changed since 4.1.2 to 4.2.2
was your old system 4.1.2 ?
You should also make it Clear you Have a Sprint HTC One
clsA said:
The file system has not changed since 4.1.2 to 4.2.2
was your old system 4.1.2 ?
You should also make it Clear you Have a Sprint HTC One
Click to expand...
Click to collapse
Yes. It's the Sprint HTC One m7. This is the most bizarre problem I have come across. And I was successfully rooted (SuperSU) with TWRP 2.7.1.1 installed prior to installing TDHITE's 2.7.1.3, which really seemed to mess things up for some reason. I used liquidsmooth custom rom, but ended up going back to the stock ROM and using Xposed framework because I do like a lot of the stock features, but I loved being able to tweak them with Xposed. Now I'm stuck on stock with a weird looking file system.
MarkBell said:
Yes. It's the Sprint HTC One m7. This is the most bizarre problem I have come across. And I was successfully rooted (SuperSU) with TWRP 2.7.1.1 installed prior to installing TDHITE's 2.7.1.3, which really seemed to mess things up for some reason. I used liquidsmooth custom rom, but ended up going back to the stock ROM and using Xposed framework because I do like a lot of the stock features, but I loved being able to tweak them with Xposed. Now I'm stuck on stock with a weird looking file system.
Click to expand...
Click to collapse
Flash recovery from here >> http://techerrata.com/browse/twrp2/m7wls
Start it choose wipe, choose format data, Reboot recovery
choose wipe / factory reset, reboot recovery
push/sideload this rom to your phone and flash it
http://forum.xda-developers.com/sprint-htc-one/development/rom-sense-6-4-4-3-stock-t2848102
Dude, we could really do some serious damage to your phone. As clsA said, you really should make it clear that it's Sprint version. Did you by any chance flash something that's not for Sprint phones? That could screw up your system.
Powered by non removable 2300 mAh battery
Is this possibly just a problem with TWRP? I actually notice in ES File Explorer that things arent' too different after all. I've got a / (Device) folder and a "0" folder which is my internal storage. It's just stuff isn't showing right in TWRP I guess, and TWRP seems to only be mounting my data partition.
MarkBell said:
Is this possibly just a problem with TWRP? I actually notice in ES File Explorer that things arent' too different after all. I've got a / (Device) folder and a "0" folder which is my internal storage. It's just stuff isn't showing right in TWRP I guess, and TWRP seems to only be mounting my data partition.
Click to expand...
Click to collapse
Go back to post 7 and do what I ask
clsA said:
Flash recovery from here >> http://techerrata.com/browse/twrp2/m7wls
Start it choose wipe, choose format data, Reboot recovery
choose wipe / factory reset, reboot recovery
push/sideload this rom to your phone and flash it
http://forum.xda-developers.com/sprint-htc-one/development/rom-sense-6-4-4-3-stock-t2848102
Click to expand...
Click to collapse
This did it. Maybe I just had a bad TWRP image flashed before? Thanks for your help!
MarkBell said:
This did it. Maybe I just had a bad TWRP image flashed before? Thanks for your help!
Click to expand...
Click to collapse
Flashing that TWRP is what got it working. I didn't follow any of the other steps. Thanks so much! Now to load my backup and restore! Thank you. Thank you. Thank you! Making a stock backup first of course. I love these forums. Seriously. Anything is possible with the fine people of XDA.
MarkBell said:
Flashing that TWRP is what got it working. I didn't follow any of the other steps. Thanks so much! Now to load my backup and restore! Thank you. Thank you. Thank you! Making a stock backup first of course.
Click to expand...
Click to collapse
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
clsA said:
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
Click to expand...
Click to collapse
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
MarkBell said:
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
Click to expand...
Click to collapse
Advanced Edit
clsA said:
Go back and hit the thanks button, it helps so others know my reputation. and you can edit your first post title to include [solved]
Click to expand...
Click to collapse
Your reputation is one of the highest here :good: :good:
MarkBell said:
I did the thanks, but I can't seem to edit the title of my first post. Title box doesn't show up when I hit edit.
Click to expand...
Click to collapse
to edit the main thread title to include [SOLVED] (go to 1st post click EDIT, at the bottom of the edit window click GO ADVANCED, then you can edit the main title)
Related
If you want the Official TWRP Recovery (now compatible with KK) for your Nexus S just check this link, there will always be the latest TWRP recovery officially out.
For now the latest is: TWRP 2.8.7.0
LINK: https://dl.twrp.me/crespo/
How to flash this? (Recommended way)
- enter in fastboot mode
- plug to your pc
- open a command prompt at the path where fastboot.exe is located
- type: fastboot flash recovery (drag and drop .img file)
- when done, type: fastboot reboot
PS: You now have a custom recovery and you are rooted. Since 2.5.0.0, TWRP roots your phone for you. Just reboot to recovery, and reboot system, if you are not rooted it will prompt you to root, just slide to accept. Let it reboot ,go to the playstore and download SuperSU.
Or if u are rooted:
- download from the playstore: [ROOT]*Rashr - Flash Tool (Playstore) / [ROOT]*Rashr - The mobile Android Flash-Tool (XDA Thread)
- download the latest TWRP.img
- open the app
- select Flash Other Recovery Image
- browse to your downloads folder
- select the TWRP.img file you just downloaded
THANKS to:
Team Win Recovery Project for this awesome custom recovery.
@DsLNeXuS (XDA username) / Ashot Mkrtchyan for the FREE app.
downloading now. thanks
Hi, I have a problem with a nandroid backup done with 2.3.1.0.
One backup done a week ago, works fine
Backup done today (successful restore) not work (stuck on boot, google and the lock)
Two question:
Is there a way to understand way stuck on boot?
If I restore /system from backup one (same rom) and /data from the last one is the same as full restore the last?
thanks
donpippo said:
Hi, I have a problem with a nandroid backup done with 2.3.1.0.
One backup done a week ago, works fine
Backup done today (successful restore) not work (stuck on boot, google and the lock)
Two question:
Is there a way to understand way stuck on boot?
If I restore /system from backup one (same rom) and /data from the last one is the same as full restore the last?
thanks
Click to expand...
Click to collapse
cant know why it gets stuck... maybe a faulty backup
u can try to grab data end system and substitute with the first one
Cascabreu said:
cant know why it gets stuck... maybe a faulty backup
u can try to grab data end system and substitute with the first one
Click to expand...
Click to collapse
i restored system from the first backup, than data from the second one.
For now works fine. All apps restored with their data.
How is done the backup? Is a dd if=/system of=systembackup ?
If so can I mount -oloop systembackup?
thanks
donpippo said:
i restored system from the first backup, than data from the second one.
For now works fine. All apps restored with their data.
How is done the backup? Is a dd if=/system of=systembackup ?
If so can I mount -oloop systembackup?
thanks
Click to expand...
Click to collapse
Dont know... i made tgis thread just to share the best recovery ever
Sent from my TH3M3D NEXUS S
Is there any changelog from 2.2.2?
Zunex95 said:
Is there any changelog from 2.2.2?
Click to expand...
Click to collapse
stability.
goomanager worked perfectly... thanks for the update
This is no good
luv2vexx said:
This is no good
Click to expand...
Click to collapse
Why? I use it in my nexus and works flawlessly
sent from my brand new Nexus 7
problems with twrp
some roms like sense4all,jb4.1.1 stock rom etc doesn't work with twrp.but works fine with cwm.
Cascabreu said:
Why? I use it in my nexus and works flawlessly
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
What should I do??
Here's what I did to fix: After restoring backup I wiped caches and installed ROM over the top. It is booting now. Thank goodness... I really didn't want to have to start over from scratch!!
Sucks that I can't rely on my nandroid backups though. Unless I am missing something.. This bug needs to be fixed!
not worth it, i reverted back to clockwork 5.8.0
Click to expand...
Click to collapse
luv2vexx said:
Cascabreu said:
Why? I use it in my nexus and works flawlessly
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
What should I do??
Here's what I did to fix: After restoring backup I wiped caches and installed ROM over the top. It is booting now. Thank goodness... I really didn't want to have to start over from scratch!!
Sucks that I can't rely on my nandroid backups though. Unless I am missing something.. This bug needs to be fixed!
not worth it, i reverted back to clockwork 5.8.0
Click to expand...
Click to collapse
Had that issue once and i reflashed the backup and it worked... i still prefer trwp, but different folks for different strokes....
sent from my not almost retired Nexus S
Click to expand...
Click to collapse
luv2vexx said:
Just tried to restore a TWRP backup, said it was successful, reboot to system and all I get is "Fastboot Mode - No boot or recovery img"
I can still boot to recovery (TWRP)....
Click to expand...
Click to collapse
I have this problem too.
I workarounded by flashing ROM's zip and then restoring backup without boot partition
yerazero said:
I have this problem too.
I workarounded by flashing ROM's zip and then restoring backup without boot partition
Click to expand...
Click to collapse
I tried again today and i can confirm that issue, but no biggie if u have the rom too... Lets hpe next version fixes it
Or we are not checking the little box on bbackup the boot partition.... Dunno
sent from my brand new Nexus 7
Cascabreu said:
I tried again today and i can confirm that issue, but no biggie if u have the rom too... Lets hpe next version fixes it
Or we are not checking the little box on bbackup the boot partition.... Dunno
sent from my brand new Nexus 7
Click to expand...
Click to collapse
I'm absolutely sure that I checked System, Data and Boot
thanks for your great work anyway
yerazero said:
I'm absolutely sure that I checked System, Data and Boot
thanks for your great work anyway
Click to expand...
Click to collapse
Thanks but i dont make these recoveries im only sharing it cuz i think apart from this issues wich turn out to be not a problem, twrp is more realiable than cwm...
sent from my brand new Nexus 7
Sorry for being late, OP updated to the latest 2.3.3.0
Now totally supports 4.2 roms
Sent from my Nexus 7 using xda app-developers app
Flashed this as instructed but when I try to boot into recovery I get the dead android guy with the red "!" icon. I'm trying to boot recovery from fastboot, is there another way it should be done?
Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
TheSignor said:
Need serious help.
I flashed dirty unicorns and data and sms wasn't working so I tried to restore my phone but TWRP didn't see anything to restore. So desperately, i saw that it still saw my ViperRom zip so i flashed that and now I'm stuck in the splash screen. I tried to get the phone back to recovery with the toolkit and it doesn't see my phone.
Click to expand...
Click to collapse
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
TheSignor said:
more info:
I just tried the button combo light trick and was able to enter recovery. but alas I am at a loss what to do now. I still can't see my backups. I'm now doing a standard wipe and reinstalling ViperRom. Please God let this work.
update: Phone is alive.......but, i'm stuck on EVDO and Goomanager doesn't seem to see any of my original stuff. I'm aware this is the 4.2.2 thing but I am not really educated on how to deal with that.
Click to expand...
Click to collapse
Look here Q14
bigdaddy619 said:
Look here Q14
Click to expand...
Click to collapse
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
TheSignor said:
Thanks. Only one question though. I just finished copying my restore from the 0 folder and pasted it, now TWRP can see it and is finally willing to restore. Will the restore solve this issue just as easily or is it that as soon as you flash a 4.2.2 is your system forever changed without this fix? I only ask because I don't want to flash that zip and create a new issue if the restore will quite literally send me back in time to before I even flashed 4.2.2.
Click to expand...
Click to collapse
TBH I only use sense roms ask your question in the 4.2.2 > 4.1.2 thread
Hi all,
I decided to post here because i'm new and I don't have permission to post in the proper thread. Anyway I'm trying to install the new rom 31.0 over my current on 12.1. It installs successfully but then I get stuck on the htc logo boot screen and yes I did the wipe data/cache thing. Can anyone help with this?
Much appreciated.
Did you update the kernel to a newer kernel? Also I would do a full wipe and then install. The two versions you are working with are very different.
spriggan17 said:
Hi all,
I decided to post here because i'm new and I don't have permission to post in the proper thread. Anyway I'm trying to install the new rom 31.0 over my current on 12.1. It installs successfully but then I get stuck on the htc logo boot screen and yes I did the wipe data/cache thing. Can anyone help with this?
Much appreciated.
Click to expand...
Click to collapse
did you confirm the MD5 sum? For ARHD 31.0 it's: 601F92B13104A373868C6C1E05972CF9
if it's not, then it's a bad download and you should download again.
EDIT: you should also select WIPE in Aroma installer!
Bootloops happen. Do a factory reset and flash again.
postfatal said:
Bootloops happen. Do a factory reset and flash again.
Click to expand...
Click to collapse
Will a factory reset erase my nandroid backup and if so how do I get the img file onto my computer?
spriggan17 said:
Will a factory reset erase my nandroid backup and if so how do I get the img file onto my computer?
Click to expand...
Click to collapse
If you don't have a functioning ROM, you'll have to enter custom recovery, adb works there. then you'll have to use "adb pull" commands to get stuff off your internal storage to your PC.
I think there's also an application called "Android Commander" which is basically a graphical file manager that acts as a front-end to adb.
nkk71 said:
If you don't have a functioning ROM, you'll have to enter custom recovery, adb works there. then you'll have to use "adb pull" commands to get stuff off your internal storage to your PC.
I think there's also an application called "Android Commander" which is basically a graphical file manager that acts as a front-end to adb.
Click to expand...
Click to collapse
I have a functioning ROM, I'm currently on Android Revolution 12.1. I just couldn't install their latest version (31.0) over my current one even after doing the data wipe both in recovery and AROMA. I re-downloaded the file and checkd the MD5 which seems to pass so I will try to install this new DL when I get home from work.
Thanks for the input guys and I'll keep you posted.
spriggan17 said:
I have a functioning ROM, I'm currently on Android Revolution 12.1. I just couldn't install their latest version (31.0) over my current one even after doing the data wipe both in recovery and AROMA. I re-downloaded the file and checkd the MD5 which seems to pass so I will try to install this new DL when I get home from work.
Thanks for the input guys and I'll keep you posted.
Click to expand...
Click to collapse
I would still recommend backing up everything to your PC, you MAY have to eventually wipe that. It's always a good idea to keep a backup of everything on your PC (or at least on a USB stick if you have an OTG).
Also remember that most likely your nandroids are in /data/media/... (which will not show up using MTP) as opposed to /data/media/0/... (which does show up on MTP), so if you want to keep them, either move them from /data/media/... to /data/media/0/... EDIT: you need a root-enabled file explorer on your phone to see /data/media/...
or use adb pull to get them off your phone.
Good luck, and remember to hit the thanks button if we helped
nkk71 said:
I would still recommend backing up everything to your PC, you MAY have to eventually wipe that. It's always a good idea to keep a backup of everything on your PC (or at least on a USB stick if you have an OTG).
Also remember that most likely your nandroids are in /data/media/... (which will not show up using MTP) as opposed to /data/media/0/... (which does show up on MTP), so if you want to keep them, either move them from /data/media/... to /data/media/0/... EDIT: you need a root-enabled file explorer on your phone to see /data/media/...
or use adb pull to get them off your phone.
Good luck, and remember to hit the thanks button if we helped
Click to expand...
Click to collapse
I got it working with a new download and clean install, but I seem to be missing the LTE icon?
spriggan17 said:
I got it working with a new download and clean install, but I seem to be missing the LTE icon?
Click to expand...
Click to collapse
It should be there, what carrier are you on, and did you select "international" in Aroma? Could also be CID related.
I have an HTC One on sprint, running a CM11 nightly. While I liked it for a while, due to business aspects, I need to go back to iphone. I am just gonna trade someone I know for my HTC for their iphone. I guess what i was wondering is what is the process of returning it back to stock? They still want root access, just not a custom ROM. I'm S-ON, HBOOT 1.56.000, Radio, 1.00.20.1100, and OS 4.06.651.4.
I'd like a step by step process hopefully (not an expert on androids, more used to iphones). But i do have some experience with cmd. I was also wondering if I turn it back to stock, will i lose all of my data (contacts, photos,etc.) I know you lose apps, but when I flashed to CM11, I backed up with TWRP, and then had to use CWM, so i couldn't restore my contacts. I do have a backup of my original ROM before i went to CM11 in TWRP, but I had to flash to CWM, so I'm not sure if it's still there.
Also, if they wanted to keep the CM11 on it, would there be any problems switching phone numbers and whatnot on it? I'd assume not because it still has an IMEI, but just wanted to make sure.
Find a flashable zip of twrp and if you didn't delete it ur backup of ur stock rooted should work...u have to have Sprint base Rom to swap phones so NO cm11 will not work when you go to trade phones
Sent from my HTCONE using Xparent Red Tapatalk 2
noXcape said:
Find a flashable zip of twrp and if you didn't delete it ur backup of ur stock rooted should work...u have to have Sprint base Rom to swap phones so NO cm11 will not work when you go to trade phones
Sent from my HTCONE using Xparent Red Tapatalk 2
Click to expand...
Click to collapse
I tried to reflash twrp. It wouldnt work. it wouldnt recognize touches.
So if I want it all stock, except for root, can I use an RUU? I know it wipes everything, but better than nothing. plus i could sync with htc manager and get everything i had back.
FireGuy2014 said:
I tried to reflash twrp. It wouldnt work. it wouldnt recognize touches.
So if I want it all stock, except for root, can I use an RUU? I know it wipes everything, but better than nothing. plus i could sync with htc manager and get everything i had back.
Click to expand...
Click to collapse
what version of twrp did you flash, should be 2.6.3.0 or higher. thus the touch problems, you don't need to ruu.(openrecovery-twrp-2.6.3.0-m7wls.img)
Aldo101t said:
what version of twrp did you flash, should be 2.6.3.0 or higher. thus the touch problems, you don't need to ruu.(openrecovery-twrp-2.6.3.0-m7wls.img)
Click to expand...
Click to collapse
I used that originally i believe. So if I re-flash my recovery to twrp, I can restore from my back up, even if I was rooted? and would i still have CM11, or stock sense?
FireGuy2014 said:
I used that originally i believe. So if I re-flash my recovery to twrp, I can restore from my back up, even if I was rooted? and would i still have CM11, or stock sense?
Click to expand...
Click to collapse
yep, you'll still have the same rom after flashing recovery til you restore a previous backup, you can back up cm 11 too.
Aldo101t said:
yep, you'll still have the same rom after flashing recovery til you restore a previous backup, you can back up cm 11 too.
Click to expand...
Click to collapse
I'm selling it and the person wants a stock rom, but also rooted. So Would I have sense or CM11 if i flash my twrp and restore my backup?
FireGuy2014 said:
I'm selling it and the person wants a stock rom, but also rooted. So Would I have sense or CM11 if i flash my twrp and restore my backup?
Click to expand...
Click to collapse
if your backup is stock sense it will be sense.i have no idea what your backup is. you should know that.
Aldo101t said:
if your backup is stock sense it will be sense.i have no idea what your backup is. you should know that.
Click to expand...
Click to collapse
I tried using the twrp manager from the play store but it says I'm not supported. 2.7.0.0 is the latest. It shows the backup i have though. Does anyone know where I can download it from and flash it onto my phone?
FireGuy2014 said:
I tried using the twrp manager from the play store but it says I'm not supported. 2.7.0.0 is the latest. It shows the backup i have though. Does anyone know where I can download it from and flash it onto my phone?
Click to expand...
Click to collapse
http://techerrata.com/browse/twrp2/m7wls is where to go 2.7.0.1 is the latest, flash this with adb fastboot, in your bootloader
Aldo101t said:
http://techerrata.com/browse/twrp2/m7wls is where to go 2.7.0.1 is the latest, flash this with adb fastboot, in your bootloader
Click to expand...
Click to collapse
would the command be fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img?
FireGuy2014 said:
would the command be fastboot flash recovery openrecovery-twrp-2.7.0.1-m7wls.img?
Click to expand...
Click to collapse
yessir
Aldo101t said:
yessir
Click to expand...
Click to collapse
should i erase my cache first?
Or just plug it up, go to bootloader, and flash it, then restore?
FireGuy2014 said:
should i erase my cache first?
Or just plug it up, go to bootloader, and flash it, then restore?
Click to expand...
Click to collapse
not sure on the cache erase some say do some say don't i'd try it without first if you have issues wipe it and reflash recovery
Aldo101t said:
not sure on the cache erase some say do some say don't i'd try it without first if you have issues wipe it and reflash recovery
Click to expand...
Click to collapse
tried to no avail. I tried and it was stuck on HTC logo for 15 minutes. I reflashed to CM11, and im downloading the RUU now to completely wipe/restore it. Unless i did something wrong? I erased cache using adb, then booted up, restored my stuff, and it said successful, but it was on the htc logo. I tried again to the same thing. then i reflashed cm11 and it worked. did i forget to do a factory reset before i restored everything? it said it wiped stuff before it restored it.
FireGuy2014 said:
tried to no avail. I tried and it was stuck on HTC logo for 15 minutes. I reflashed to CM11, and im downloading the RUU now to completely wipe/restore it. Unless i did something wrong? I erased cache using adb, then booted up, restored my stuff, and it said successful, but it was on the htc logo. I tried again to the same thing. then i reflashed cm11 and it worked. did i forget to do a factory reset before i restored everything? it said it wiped stuff before it restored it.
Click to expand...
Click to collapse
after you erased cache did you flash recovery, then reboot recovery and restore a backup
when you are on the htc logo hold the power button down til it reboots and see if it goes past the htc screen
you don't have to factory reset to restore a rom just hit restore and select the backup
Aldo101t said:
after you erased cache did you flash recovery, then reboot recovery and restore a backup
when you are on the htc logo hold the power button down til it reboots and see if it goes past the htc screen
Click to expand...
Click to collapse
I flashed recovery, then erased cache, then rebooted to recovery, and restored a backup. when it said successful, i rebooted from there, and it vibrated on bootup, but stayed at the htc screen for a while. I held the power button and rebooted. same thing.
FireGuy2014 said:
I flashed recovery, then erased cache, then rebooted to recovery, and restored a backup. when it said successful, i rebooted from there, and it vibrated on bootup, but stayed at the htc screen for a while. I held the power button and rebooted. same thing.
Click to expand...
Click to collapse
well, i don't know, i'd try 2.6.3.0 twrp and don't wipe cache, thats what i been using, what the hell can't hurt to try at this point in the game
sometimes it takes awhile on the first boot, i've had some take quit awhile, but i don't know
Aldo101t said:
well, i don't know, i'd try 2.6.3.0 twrp and don't wipe cache, thats what i been using, what the hell can't hurt to try at this point in the game
Click to expand...
Click to collapse
I'm gonna try an RUU. I'm downloading the latest one right now (4.06.651.4 i believe). I'll let you know how it works out. since i'm S-ON, all i need to do is relock boot loader and then run the RUU correct?
FireGuy2014 said:
I'm gonna try an RUU. I'm downloading the latest one right now (4.06.651.4 i believe). I'll let you know how it works out. since i'm S-ON, all i need to do is relock boot loader and then run the RUU correct?
Click to expand...
Click to collapse
yes,
I was attempting to install the SlimKat ROM, and I followed the directions by going into CWM and doing a factory reset, wiping the cache, and formatting /system. When I tried to install the ROM, though, it told me that the file was bad. Now I can't boot back into the OS! It just stops at the T-Mobile splash screen. I can still get to CWM, but I have no idea where to go from there. I tried to recover from a previous backup, but it gives me "Error while restoring /system!"
How can I get my recoveries to work?
Just to confirm:
You do have the model Exhibit T679, correct?
What version of CWM did you flash?
The way I've been flashing ROMs:
Boot into CWM
Go to mounts and storage
format /system
format /cache
format /data
Go back to first CWM screen
Go to advanced
wipe dalvik cache
Go back to first CWM screen
Choose install zip
choose zip from the location you placed the ROM
To restore your backup:
Do steps 1-5 from above
6. Go to backup and restore
7. restore from the location you saved the backup
ZHXS said:
Just to confirm:
You do have the model Exhibit T679, correct?
What version of CWM did you flash?
Click to expand...
Click to collapse
Yes, it is a T679. My version of CWM is 6.0.5.0.
So, I solved the original problem, and now I have a new one... What I found was that I was able to install one of the other ROMs (Mahdi) from my external SD card. Then, I took a look at the SlimKat zip on my computer. As I suspected, the file was corrupted. (The MD5 hash didn't match.) So, I downloaded a new copy, verified the hash, and then tried again. This time, it worked! Everything seems to have installed okay, and I am loving SlimKat so far. Except for one thing... Somehow, I unrooted my device! Titanium Backup doesn't work anymore, and it was telling me it couldn't get root. So I installed Root Checker, and sure enough, I don't have root anymore! I downloaded root-stock.zip and tried flashing it, and that didn't work. Well, I guess it wouldn't, since I don't have a stock ROM anymore?
I'm sure I could flash a stock ROM, and then root that, but then I would want to go back to SlimKat, and I'm afraid I'd just wind up un-rooting it again.
fajrero said:
Everything seems to have installed okay, and I am loving SlimKat so far. Except for one thing... Somehow, I unrooted my device! Titanium Backup doesn't work anymore, and it was telling me it couldn't get root. So I installed Root Checker, and sure enough, I don't have root anymore! I downloaded root-stock.zip and tried flashing it, and that didn't work. Well, I guess it wouldn't, since I don't have a stock ROM anymore?
I'm sure I could flash a stock ROM, and then root that, but then I would want to go back to SlimKat, and I'm afraid I'd just wind up un-rooting it again.
Click to expand...
Click to collapse
As far as I know, most of these custom ROMs already come with root.
If you installed [ROM] [UNOFFICIAL] [4.4.2] SlimKat ROM [WEEK… | Galaxy Exhibit 4G | XDA Forums one of the listed problems is:
...Awesome... said:
What's Not Working!!
2) Some reason i lost root i had to include the Su app and Root is now active again
Click to expand...
Click to collapse
Maybe wait? Or try to flash/install Su?
---------- Post added at 12:12 AM ---------- Previous post was at 12:07 AM ----------
Of if you installed [ROM][KK][4.4.4][KTU84P] SlimKat 6 UNOFFICIA… | Galaxy Exhibit 4G | XDA Forums known issue is:
jfbs said:
Known Issues
Do not enable KSM
If lacking root, enter superuser settings, then tap superuser access and select apps and adb.
Click to expand...
Click to collapse
ZHXS said:
As far as I know, most of these custom ROMs already come with root.
Click to expand...
Click to collapse
That's what I thought, too. This is why it's so confusing for me.
If you installed [ROM] [UNOFFICIAL] [4.4.2] SlimKat ROM [WEEK… | Galaxy Exhibit 4G | XDA Forums one of the listed problems is:
Click to expand...
Click to collapse
No, it's the one a little further down:
[ROM][KK][4.4.4][KTU84P] SlimKat 6 UNOFFICIAL-20140707
Maybe wait? Or try to flash/install Su?
Click to expand...
Click to collapse
That's what I'm going to try next. I haven't been able to find a source for the su binary yet, though. Just a lot of stuff for SuperSu, which requires you to already be rooted. I'm gonna try to get some sleep and look some more tomorrow. Thanks for your help.
fajrero said:
No, it's the one a little further down:
[ROM][KK][4.4.4][KTU84P] SlimKat 6 UNOFFICIAL-20140707
That's what I'm going to try next. I haven't been able to find a source for the su binary yet, though. Just a lot of stuff for SuperSu, which requires you to already be rooted. I'm gonna try to get some sleep and look some more tomorrow. Thanks for your help.
Click to expand...
Click to collapse
Ok, that ROM seems to have Superuser built in already, do you see a menu item for it when you go into Settings? The instructions seem to note that you have to go into Superuser and check a couple boxes.
Maybe it was a bad install, try formatting the necessary partitions and reflash again. Then go into Superuser and select the appropriate options.
Sometimes I also format sdcard0 after all the other formatting just to be extra thorough then install new ROM per instructions:
jfbs said:
Installation
Install at your own risk
- First time flashing CM11 to your Galaxy Exhibit (or coming from another ROM)?
Boot into existing recovery and create a Nandroid Backup!
Install at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
Reboot recovery into at least ClockworkMod Recovery 6.0.4.5 or TWRP 2.6.3.0
CWM: WIPE dalvik-cache, format: data, system, and cache. TWRP: WIPE dalvik-cache, data, system, and cache.
** Optionally back-up sdcard0 before install and format it in recovery if experiencing install issues **
Install the ROM (without gapps)
Reboot system
After system boots, boot back into recovery and install KK Google Apps.
Wipe dalvik-cache and cache. Reboot.
Click to expand...
Click to collapse
TripFX said:
FYI most people here on xda just prefer you either clicking the thanks button if you the post was useful or if it a bug related then logcats and brief description of the problem and wait patiently for someone who knows to either A) if dev - fixes it or asks for more info. B) if other user- tries to help you out if possible.
Click to expand...
Click to collapse
:laugh:
You are welcome!
ZHXS said:
Maybe it was a bad install, try formatting the necessary partitions and reflash again. Then go into Superuser and select the appropriate options.
Click to expand...
Click to collapse
Yeah, that seems to have done it. I have root again, and everything looks okay.
Thanks again!!