I was trying to install a new rom on my Desire Z, following the directions here, but something went wrong somewhere and now I can't mount /data. I don't want to go any further in the rom installation process, as I'm afraid to brick my phone. The same thing happened to me while upgrading my Windows 6.5 phone (unexpected problem during rom install) and I ended up with a brick (corrupt bootloader).
I have found several threads here discussing the same problem. However, all of them use highly technical language and seem to be advice from experts to other experts. There are a lot of terms I don't understand or only understand partially, like nandroid, parted, hboot, and so on. Everyone assumes too much. Can anyone explain the procedure in terms a novice can understand?
gromky said:
I was trying to install a new rom on my Desire Z, following the directions here, but something went wrong somewhere and now I can't mount /data. I don't want to go any further in the rom installation process, as I'm afraid to brick my phone. The same thing happened to me while upgrading my Windows 6.5 phone (unexpected problem during rom install) and I ended up with a brick (corrupt bootloader).
I have found several threads here discussing the same problem. However, all of them use highly technical language and seem to be advice from experts to other experts. There are a lot of terms I don't understand or only understand partially, like nandroid, parted, hboot, and so on. Everyone assumes too much. Can anyone explain the procedure in terms a novice can understand?
Click to expand...
Click to collapse
"Mount" data to flash a rom? You sure? Looking at the link you provided just says place on sd, wipe, flash. Where exactly are you stuck or am i just missing the obvious.
The /data corruption occurred halfway through the upgrade process. I'm not sure what to do, so I stopped and asked for advice. I kept going the last time I had a problem, and got a bricked phone for my trouble.
The only "data" I see in that guide (Same one I used in fact), is the comment bout doing a "Factory Reset/Wipe Data" which is what it says, says nothing about /data/ partition, just to do a full wipe.
Naturally you do this from recovery, not from within an app or while the phone is still booted into normal usage.
So, wiping the phone will fix everything? And then install cyanogen? Sorry, just want to be totally completely sure.
Aye, indeeed, as KB said, full wipe, then flash new rom.
OK, thanks! I was just reeeealy nervous about the "wipe the phone" part. My phone still sort of works now, most programs not available, but Google Maps and the telephone still work...the most important parts of the phone as I travel a lot.
gromky said:
OK, thanks! I was just reeeealy nervous about the "wipe the phone" part. My phone still sort of works now, most programs not available, but Google Maps and the telephone still work...the most important parts of the phone as I travel a lot.
Click to expand...
Click to collapse
Factory Reset/Wipe will only clear the internal partitions ( /system /data /cache ) , and additionally if you choose Dalvik Cache, then that as well is usually good to do with a brand new rom.
It will not wipe your radio, hboot, recovery, etc, just the system-related areas for roms.
Generally speaking:
Factory Reset + Wipe Cache/Dalvik Cache
Flash CyanogenMod
Flash the Google Apps Zip specific to that CM version (as CM doesn't come with Google Apps by default)
Reboot
Just remember that doing a backup before doing anything to your phone like above is available, as a factory reset and such will wipe contacts and settings and so forth unless you got a google account setup to restore them (or using something like Titanium Backup on an already rooted phone).
OK, I was following the rooting guide, as that must be done before installing cyanogen. I performed all the steps to "reboot". Md5 #2 & md5 #3 matched. Upon rebooting, I can't use su from the terminal (permission denied). I also tried "cd /sdcard && ./su" and got the same thing. Does this mean the rooting didn't work? Or can I proceed with wiping the device regardless? After I wipe the device I won't be able to perform the rooting steps again...and will likely have a brick...just totally paranoid here.
gromky said:
OK, I was following the rooting guide, as that must be done before installing cyanogen. I performed all the steps to "reboot". Md5 #2 & md5 #3 matched. Upon rebooting, I can't use su from the terminal (permission denied). I also tried "cd /sdcard && ./su" and got the same thing. Does this mean the rooting didn't work? Or can I proceed with wiping the device regardless?
Click to expand...
Click to collapse
I followed that one as well. And I assume you rebooted after that point.
Did you continue forth and factory-reset/wipe and then install CM7 over your stock install?
Basically the downgrading/etc makes the phone exploitable, and then the rooting portion puts you back up to a engineering hboot and such that is unlocked with S-OFF, from there you either flash a pre-rooted ROM (i.e.: CM7 etc), or you root an existing stock (which would have gotten wiped from the hboot replacement).
If you already flashed CM and can't do su via adb then it's possible that under "Security" or "Development" in your phones system memory that su is restricted to "app only" and you may need to change that to "app and adb".
You shouldn't be running su from /sdcard (since that's not a linux style partition, and /sdcard is a no exec area). The su binary should already be installed to system in CM.
Clarification If you did not yet reboot (i.e.: Step #7 and onward), and then wipe/flash cyanogenmod (or another pre-rooted custom rom), then proceed with the steps, otherwise you're just working with a half-processed phone and naturally nothing would work in that state.
kbeezie said:
I followed that one as well. And I assume you rebooted after that point.
Click to expand...
Click to collapse
Yes.
Did you continue forth and factory-reset/wipe and then install CM7 over your stock install?
Click to expand...
Click to collapse
You mean hold "down" and boot into recovery, and immediately do these steps? No, I did not. I let the phone boot as normal, to try to run su to verify if the rooting process worked or not.
I suppose my question should be: how can I verify that the rooting process worked, and I'm ready to wipe? The su on /sdcard was pushed there by adb and used during the procedure. From the guide:
adb push su /sdcard/
adb push Superuser.apk /sdcard/
Basically the downgrading/etc makes the phone exploitable, and then the rooting portion puts you back up to a engineering hboot and such that is unlocked with S-OFF, from there you either flash a pre-rooted ROM (i.e.: CM7 etc), or you root an existing stock (which would have gotten wiped from the hboot replacement).
Click to expand...
Click to collapse
I didn't downgrade, I still have my stock rom (phone bought from Hong Kong so it's one of the Asia roms) which temprooted just fine with visionary.
gromky said:
Yes.
You mean hold "down" and boot into recovery, and immediately do these steps? No, I did not. I let the phone boot as normal, to try to run su to verify if the rooting process worked or not.
I suppose my question should be: how can I verify that the rooting process worked, and I'm ready to wipe? The su on /sdcard was pushed there by adb and used during the procedure. From the guide:
adb push su /sdcard/
adb push Superuser.apk /sdcard/
I didn't downgrade, I still have my stock rom (phone bought from Hong Kong so it's one of the Asia roms) which temprooted just fine with visionary.
Click to expand...
Click to collapse
Don't use Visionary unless for some strange reason your phone came with Froyo (2.2) on it (it's an outdated method, and has a high brick rate). Given that you may have an asian rom etc, I would just go ahead and do a factory reset /wipe via recovery, and flash CM7 or a pre-rooted stock rom found here on the XDA forum for the best result.
I think even one of the AOKP or Adromudus comes with Pinyin input support already if you need it.
It did have Froyo. I have uninstalled visionary per instructions before performing all these steps. But since I only get one shot at rooting correctly, I want to make absolutely positively sure the process worked before I do something irrevocable like wiping the entire phone, only to discover I can't install a new rom because the phone isn't rooted.
I use third-party programs (GO keyboard) for all of my Chinese needs, and they've worked fine so far.
gromky said:
It did have Froyo. I have uninstalled visionary per instructions before performing all these steps. But since I only get one shot at rooting correctly, I want to make absolutely positively sure the process worked before I do something irrevocable like wiping the entire phone, only to discover I can't install a new rom because the phone isn't rooted.
I use third-party programs (GO keyboard) for all of my Chinese needs, and they've worked fine so far.
Click to expand...
Click to collapse
Rooting is at the rom/kernel level. But in order to flash a new custom kernel would need an unlocked bootloader which you already did with S-OFF.
So you would either flash a pre rooted rom like almost everything available via the developer section here (via recovery not hboot) or a stock rom then root that.
If you do everything via recovery you are less likely to accidentally lock/unroot the phone since recovery normally deals with the rom/kernel /cache and not hboot.
Sent from my T-Mobile G2
It worked - thanks! I was so concerned about bricking the thing. The whole process was easy...now that I've done it. Cyanogen came up in Chinese...couldn't figure out how to change it to English for a while. I suppose there's some setting in my phone that tells it to default to Chinese. It also appears to be locking up frequently on my phone - but at least I got the software on there, and now I can play with other mods. Thanks again!
gromky said:
It worked - thanks! I was so concerned about bricking the thing. The whole process was easy...now that I've done it. Cyanogen came up in Chinese...couldn't figure out how to change it to English for a while. I suppose there's some setting in my phone that tells it to default to Chinese. It also appears to be locking up frequently on my phone - but at least I got the software on there, and now I can play with other mods. Thanks again!
Click to expand...
Click to collapse
If I had to make a guess, I would probably say you flashed Cyanogenmod onto the phone WITHOUT first doing a factory-reset/wipe, in which case you probably broke it (hence the language and freezing) by merging cyanogenmod on top of the pre-existing rom.
No, I definitely wiped the phone first. I got a few lockups in cyanogen so I went to install another rom. Now I'm getting "E:error in /cache/recovery/log" and "E:can't open /cache/recovery/log". When I install a new rom, it won't take and boots into cyanogen. It was in a reboot loop for a while but now it has booted into cyanogen again. Sigh. This is what I was afraid of.
Boot into boot and write down everything on that screen (power+volume down) just to check all is well, what is your recovery?
Search out two things (just use search function in g2 xda threads)
1 superwipe+ext4.zip
2 elitemod cm7
Boot into recovery and flash the super wipe like you did the from
Now flash elitemod
Is all well at this point?
Sent from my GT-I9100 using xda premium
Actually the phone seems to be working with cyanogen now. I suspect the internal memory is corrupt somehow, and that's a problem that can't be fixed. I'm going to stop messing with it before I brick it. If any more problems I'll revive the thread. Thanks so much to everyone who helped. I really can't afford a new phone right now and cyanogen seems to have fixed the problems I was having with the stock rom.
gromky said:
Actually the phone seems to be working with cyanogen now. I suspect the internal memory is corrupt somehow, and that's a problem that can't be fixed. I'm going to stop messing with it before I brick it. If any more problems I'll revive the thread. Thanks so much to everyone who helped. I really can't afford a new phone right now and cyanogen seems to have fixed the problems I was having with the stock rom.
Click to expand...
Click to collapse
If the emmc is faulty then it's going to eventually brick itself, and should probably be sent in for warranty if available.
Related
Hey guys
I noticed that many people are asking around for a way to unroot their phones, and you hear alot about flashing back as a solution for unrooting, but for me that was abit not preferred. So here is a way to do it quick and soooo easy and you don't even need a computer to do it. We start:
1- From the android market download (Terminal emulator) and run it.
2- Once inside the shell type in these commands (you gotta press enter after each line)
su
rm -r /system/app/Superuser.apk
rm -r /system/xbin/busybox
rm -r /system/bin/su
and Voila, your phone is now unrooted. needless to say that you should also uninstall the terminal emulator as well. Hope this is useful.
Thumbs up! Someone should have posted this quick and easy method earlier.
Meaning we wont have any warranty issues with Samsung if un-root and send back to service center? Thnx.
well, first of all you need to have the same stock rom shipped with the phone (or the officially upgraded one via kies). Then you should unroot it, then in recovery mode you need to clear cache and do factory reset. and format the internal storage (and of course remove SD card if any) then it will be in the same condition when it was shipped to you. Thats how you avoid trouble with the warranty before sending your phone back for service or replacement.
cheers
mmthabet said:
well, first of all you need to have the same stock rom shipped with the phone (or the officially upgraded one via kies). Then you should unroot it, then in recovery mode you need to clear cache and do factory reset. and format the internal storage (and of course remove SD card if any) then it will be in the same condition when it was shipped to you. Thats how you avoid trouble with the warranty before sending your phone back for service or replacement.
cheers
Click to expand...
Click to collapse
Wow....thnx...this make the whole rooting process sweet.
Great stuff man, well done.
Nice tip!
If you unroot using your method and then wipe the phone completely (cache/factory reset) then place ClockworkRecovery onto internal memory as update.zip and reboot in recovery and make a nandroid backup (doesn't need root) then carry on, should you need to send it in for warranty just restore the nandroid backup and it will be unrooted, stock firmware and fresh You might need to flash the stock modem back though if you change
xfile087 said:
Nice tip!
If you unroot using your method and then wipe the phone completely (cache/factory reset) then place ClockworkRecovery onto internal memory as update.zip and reboot in recovery and make a nandroid backup (doesn't need root) then carry on, should you need to send it in for warranty just restore the nandroid backup and it will be unrooted, stock firmware and fresh You might need to flash the stock modem back though if you change
Click to expand...
Click to collapse
Hey guys, glad you liked that. And indeed using clockrecoverymod as update.zip is a great tool, no root or whatsoever.
Cheers
After unrooting my sgs, uninstalled all as described, found strange app under settings > manage apps called "com.noshufou.android.su", default app icon, just 8 Kb...
googlin' found a site
(wwwdotmarket4androiddotcomslash-stock-android-2-1-apps-list) that says:
Superuser.apk com.noshufou.android.su yes 16549 Remembers ‘su’ settings
(yes is "safe to remove")...
Anyone knows if this is right?
May I remove it from apps?
Thx
Well I must say this is so strange. But you i'd bet it can be safely uninstalled. If I were you i'd make sure to do factory resetting once more and clear cache again.hope that helps.
Sent from my Galaxy S using tapatalk.
This method works on JP3 froyo firmware ???
nl2006 said:
This method works on JP3 froyo firmware ???
Click to expand...
Click to collapse
Well, technically speaking this method should wwork on any firmware as it is shell based. I tried it on JF3, JM2, and JP2. Plus you have nothing to lose it is 100% safe so you can try it, if it works , fine, if not no harm done.
This method have ruined my phone.
After step rm -r /system/app/Superuser.apk my phone hang and displayed the message "Can't write to readonly memory" and now it refuses to boot again. Have tried removing the battery. I have also tried to hardreset but i don't even get to the screen to select a hardreset. The phone starts but don't get passed the initial samsung splash screen. If anyone have an ide how to fix this please help me.
WARNING! Be really carefull before using this method
Well, sorry it didn't work out for you. But to be honest this should be the safest method as the other option is to flash your phone already to another stock firmware. So as now this method apparently failed and you got a wierd situation where some of the system files were ruined, you can just try to flash the stock rom files using odin.
The stock firmwares and the tools you need (odin) together with a tutorial on how to do it you find in the following link
http://samsung-firmware.webs.com/samsungi9000.htm
good luck
it worked fine for my sgs did it just few minutes ago, but added reboot in the end
not working
Iv entered these codes, and after I hit enter each time it says file.not found. Am I doin something wrong
Hi, my SGS is using XXJPY with voodoo kernel.
Can i use this method on my SGS?
And should i firstly remove the kernel or the commands can be applied directly?
Hey guys,
I have rooted my new evo 4g with the "[GUIDE] How to root Android 2.2 on the EVO 4G" and the first time around i did it all with no trouble (Although it was time consuming) I uploaded a couple of themes, also no problems... Then i tried flashing the Fresh Evo 3.3.0.1 and since i never had any other previous version of Fresh (or any other ROM for that matter) i didn't bother backing up or wiping, and when i rebooted the phone (After i flashed the ROM) it got stuck at the white "HTC EVO 4g" screen and stayed that way, and after about 10 minutes of that i decided to pull the battery and go back into recovery and wipe the drive & cache ect... That also did nothing, once i rebooted i was still getting stuck at that screen, So after that i did some sort of combination of updating the fastboot and then doing the "Clear Storage" option, i was able to at least get the phone to go through that whole startup process again, and i was able to use the phone again. but i ended up in the long run wiping EVERYTHING off my phone in the process, and after i was finally able to get my phone to work again, i promise myself i would NEVER mess with that stuff again... BUT, being as stupid as i am, 2 days later i was back into trying to install stuff again, But everytime i did, i was meant with the same results again. (Startup screen freezing) So after about 5 tries i decided to give up, within the past few days i noticed that HTC had the new 3.29XXX software version up... Now i figured since i can't get the themes and ROM for that matter to work anymore, i just ended up installing the new updates. but yesterday i tried to go into recovery and start messing around with it again, but i can't get to AMON-RA recovery screen anymore, My guess is when i updated the phone, it removed the necessary files for the recovery to work... So last night i deleted all the files i put onto the SD Card (For rooting) and started the full rooting process over again (pushin adb through command prompt ect) and i was able to get the RA recovery back, but when i tried installing a theme, and reboot it takes me through the startup and gets to the "4G Bootscreen" and then it just keeps looping over, and over again. So i had to end up wiping, clear storage ect again to get the phone to work again.
Sorry for the long explanation but i feel the more information there is that better help someone can provide me help with. So i guess my question is does anyone know what i should do to get the recovery to work again to i can start using themes & ROMS again? I'm just pissed off that everything was fine until i tried to flash freshes ROM, I must have done something wrong.
Thanks for all the help in advance, I realize I'm a noob to this site but any help would be greatly appreciated.
Holy crap. If you don't know what you're doing, you need to read hundreds of posts! I probably spent two weeks on these forums before I even considered rooting.
1. First off, regaw's root method is a little outdated. Unrevoked 3.21 is out and fully automated (or nearly). No adb, no command line, etc. Unrevoked is root privileges + nand unlock.
2. Never accept an ota update if you rooted! Ever! Best case is that it breaks root (which is what happened to you).
3. You must have s-off on you're boot loader screen to be able to install custom roms/kernels. This is nand unlock.
4. Always and forever wipe data and dalvik cache when switching between roms or when recommended during upgrade by the rom developer! Boot loops can happen!
5. To install a rom, wipe data cache in recovery then apply the zip of the rom. Phone may take 5 minutes at the boot screen because it's rebuilding the cache you wiped.
6. Always do a nand backup! Always, no excuses!
Greetings,
Everything dom085 said is gospel - really.
For convenience, I'm adding links to the rooting apps mentioned, as it appears
these are the ones you need. Do not forget to follow a successful root
process with Unrevoked forever (S-OFF). You will most assuredly want/require this
for all your rooting and MOD changing activities.
Once S-OFF has been achieved, you will not be required to do it again,
as it's a lower-level (radio) process, and other activities won't affect it.
Unrevoked 3.21 for HTC-EVO(supersonic)
Unrevoked forever for HTC-EVO(supersonic)
If unsure, start here to insure you get the correct
version(s) for your phone.
HTH
--Chris
Chris, thanks for adding the links, I'm not able to do that yet.
However, the newest Unrevoked 3.21 method includes permanent nand-unlock by default. No more separate Unrevoked-forever process. From the Unrevoked 3.21 website:
Does this permanently unlock the NAND flash on my phone?
Yes. The default configuration of this tool disables the phone's security, which also disables the NAND locks placed on the storage by the bootloader. If you choose not to disable security, the /system partition will be read-only after the tool completes
dom085 said:
Chris, thanks for adding the links, I'm not able to do that yet.
However, the newest Unrevoked 3.21 method includes permanent nand-unlock by default. No more separate Unrevoked-forever process. From the Unrevoked 3.21 website:
Does this permanently unlock the NAND flash on my phone?
Yes. The default configuration of this tool disables the phone's security, which also disables the NAND locks placed on the storage by the bootloader. If you choose not to disable security, the /system partition will be read-only after the tool completes
Click to expand...
Click to collapse
Strange. I rooted with Unrevoked 3.21. Everything went flawlessly. But S-OFF
wasn't indicated. So I downloaded the S-OFF, and performed it. Now S-OFF
shows up.
Strange, because I did it pretty recently (after the "new improved" version was released).
Please note, I'm not arguing with you. Just sharing my own experience.
--Chris
CTH-EVO said:
Strange. I rooted with Unrevoked 3.21. Everything went flawlessly. But S-OFF
wasn't indicated. So I downloaded the S-OFF, and performed it. Now S-OFF
shows up.
Strange, because I did it pretty recently (after the "new improved" version was released).
Please note, I'm not arguing with you. Just sharing my own experience.
--Chris
Click to expand...
Click to collapse
Interesting.
It does say "default configuration of this tool." I didn't see any way to change it though when I was rooting (I've done two phones through Unrevoked 3.21). In fact, I didn't see any menus or options at all. Perhaps you changed the "default configuration" somehow?
Hi All,
I rooted my unbranded/unlocked HTC desire using the unrevoked method successfully and loaded a custom rom on there which I have been using for about 1 year.
Needless to say it is now time for an update from (Paul's r9 to r11), however when I tried to install a new rom in recovery, nothing happens.
I boot my phone into recovery (clockworkmod v. 2.5.0.7) and delete all user data, cache, and the dalvik cache and then choose to install .zip from sd card.
I choose the .zip and go install, the it looks like it's working fine, the log says it's opening the package but then it just suddenly disappears and goes back to the recovery screen again as if nothing has happened.
When I reboot my phone, it just goes back to being reset but still using the old rom (r9).
Now all I want is to restore it back to the stock WWE version, but they all seem to be in .exe format...
Please tell me what I can do...
Thanks so much.
For flashing another rom I would try newer version of clockworkmod if yours don't work.
If you want to go back to stock, just run RUU. Like you said it's an .exe, so nothing you can do wrong.
Whats your erase size?
Thanks for your responses, I'm kind of new to all this.
Actually I started looking for solutions about 3 months ago but there's just so many different methods out there and I just didnt know which to follow.
RUU, ok I will look that up, thanks.
Also I installed Rom Manager (when looking for update to clockworkmod) and it has apparently flashed my recovery to the newest mod. So I will try it again.
EDIT: it hasnt worked, when I restarted my phone in recovery but it's still the old version...
I'm not sure what you mean by erase size?
Thanks again.
The erase size lets us know which hardwarerevision your desire has. It's important to know it because with the erasesize 40000 (aka PVT4 desire) you cannot use the cwm recovery which is usually flashed with unrevoked. To find out your erasesize, download a terminal emulator from android market, start it and then enter
Code:
cat /proc/mtd
ok I checked it and it shows erasesize as all being 00020000
Ok erase size is not the issue then.
I know I have this issue when there is a problem with my zip. Not always getting "Installation aborted, (bad)" error message.
Might be worth checking the file system of the SD card (maybe download h2testw.exe for windows to test it for errors)
Personally I'd just flash a better recovery and try again.
there's a guide on how to do so on my troubleshooting guide if you need help. Just look in the "repairing recovery" section. (Note: since you are fairly new to this, I'm betting on that your phone is S-ON, for you to be able to flash recovery, you need to be S-OFF, however there is also a guide on that, even with a video ^_^)
Thanks for your help
I checked and yes, I am s-on, but I read a few guides and really it's all too complicated for me.
The only reason why I needed a custom rom was because my phone was purchased in China and had chinese market content only and it wouldnt let me install Skype.
Now I'd be happy with a stock WWE rom that I can update automatically via android auto updates...
I think running the stock RUU will do this? I'm going to try it now.
Thanks again, but I might be back because I'm so unskilled at these things
Use android flasher, its easy to flash different recoveries, hboots, radios and boot animations. Almost cheating
HTC Desire
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Let's try this in order: if you are with Virgin Mobile, it is a CDMA. GSM phones take a sim card, both versions accept an sd card for storage.
Everything looks good until:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Good luck. If you have any more questions, feel free to ask.
pedantfool said:
DISCLAIMER: I'm completely lost, so please break things down into bite-size steps or at least expect some follow-up questions on my part. I'm one of those desperate guys who is attempting to just have a working phone tomorrow. Any help will get as many presses of the thank button as I can possible give.
After several hours of plodding and poking and searching I've managed to do some possibly irreparable damage to my htc one v. Whenever I try to boot the phone it starts up with the htc developer red text "development use only" etc etc. I can access the bootloader and recovery thankfully, so I guess there's hope.
I think the source of my troubles is what's addressed by the essential reading at the top of this sub-forum, ie distinguishing between GSM and CDMA. I think (and this is an assumption here) that despite being in the USA on virgin, the fact that I can shove a sd-card in there means it's GSM (correct me if I'm wrong. please). EDIT: It seems that the phone only works with the CDMA version of TWRP, so I guess that might be an indicator.
Info: htc one v, virgin USA, using TWRP 2.3.3.0, attempted to flash Rom using various versions of Paranoid Android
What I've done thus far:
1. Unlocked bootloader
2. Flashed recovery
2.5. Created backup
3. rooted device (I downloaded rootchecker or somesuch app and was able to confirm that I had rooted my device)
4. Wiped cache and dalvik cache (I think that's what it's called).
5. Attempted to do a factory reset (failed).
6. Attempted to flash ROM (failed)
7. Restarted Device (got stuck on dev screen for the first time).
8. Tried recovering using backup created earlier (which just booted me into the dev screen of doom again).
9. Tried partitioning sd card in an attempt to perform a factory reset (wiped everything including backup).
10. Factory Reset failed with a message about not being able to mount /sd-ext.
11. Tried flashing rom again with different version of PA for shiggles (it worked! oh frabjous day!)
12. Rebooted phone only to get stuck on the dev screen again.
Guides I've used/perused/glanced at:
1. http://forum.xda-developers.com/showthread.php?t=2154635
2. http://forum.xda-developers.com/showthread.php?t=1598964
3. http://www.idroidspace.com/jelly-bean-4-2-2-paranoid-android-custom-rom-for-htc-one-v/
4. http://techmell.net/android-tips/ho...paranoid-android-4-1-2-jelly-bean-custom-rom/
5. http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
6. http://www.youtube.com/watch?v=a3pof_WSEEI
I've been at this for nigh on 7 hours and all I have to show for it is a phone I can't use. Help.
Click to expand...
Click to collapse
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
followup
FIRST: Just thought of something that might be very important, I only had a version of android 4.0 installed on my phone. Will that make a difference when installing roms intended for later versions of android? If so, I feel like a huge knuckle-dragging fool.
Update: Was able to install and boot using PACman, but ran into a boot-loop.
But to follow up to your questions:
MameTozhio said:
If you're restoring "stock" sense 4.0 ROM, you need to flash a kernel that will work with it. Try Titanium-KISS or Stock. The stock one should have been kernel should have been backed up, it's labeled boot.IMG in the backup folder. EDIT: Since you are CDMA, you need to flash this kernel in Fastboot to get it to boot: http://forum.xda-developers.com/showthread.php?t=2024758. Be sure you flashed the CDMA ParanoidAndroid as well, and not the GSM one.
Click to expand...
Click to collapse
I'll admit I've had a hard time find a definitive version of PA or really any other Rom. I've tried going through their thread here and downloading one of the "stables" (http://goo.im/devs/gannon5197/paranoid/primoc/stables/). I've also used other unofficial versions of PA (http://forum.xda-developers.com/showthread.php?t=1799372). I'm currently downloading PACman to see if that will make any difference.
[email protected]@ said:
Which ROM you have flashed?
Did you install boot.IMG according to your ROM?
Sent from my HTC T320e
Click to expand...
Click to collapse
I did flash my boot.img using the method explained here:
Copy the kernel image (boot.img file you have extracted from zip file of ROM) to folder in which you have kept your fastboot files.
In the same folder, right click while holding shift button and select ‘Open command window here’.
A command window will appear on your screen. In command window type ‘fastboot flash boot boot.img’ and press enter.
On your screen you will get message ’OKAY/Finished’. You have successfully flashed kernel. Now you can disconnect your phone from computer.
http://androidlegend.com/upgrade-ht...ing_wp_cron=1369722527.0674550533294677734375
riggerman0421 said:
#5 The failed warning is due to lack of a SD EXT partition on your sd card. If you didn't re-partition it, you will get that failed warning. No big deal as it is wiping everything else correctly.
Click to expand...
Click to collapse
I'd like to think I'd partitioned it properly, but I keep getting a "unable to mount sd-ext" or "unable to wipe sd-ext" message when I attempt a factory reset. I've tried formatting the the mini sd and set the file type to FAT32, but to no avail as the errors persist. I know you said not to be too concerned, but I keep failing the system wipe from your next suggestion because of that error.
#6 You also need to wipe system prior to flashing your new rom.
After flash your new rom, you will need to connect to your pc and boot into bootloader. Make sure it says "Fastboot USB" at the top your phone screen. You have to flash the boot.img for the specific rom you are trying to install. See the rom thread for the correct method.
Click to expand...
Click to collapse
Now how important is it that I flash the boot.img after I have flashed the rom? I've been doing it beforehand, but does doing it afterward make a difference?
Check your radio and Hboot version in bootloader. If you have the newer radio (xxx.xxx.928) and Hboot (1.57), you are limited on the roms that will actually work. Check the CDMA development thread for roms that specify OTA compatible.
Click to expand...
Click to collapse
Those both match my radio and bootloader, what does that imply? I'm planning on flashing this rom: http://forum.xda-developers.com/showthread.php?t=1948034
Will that work?
No, it won't. You have the newer updated hboot and radio. That is the source of your boot loops. The only compatible roms at this time are MyOneV, ExtremeSemse, and RhythmicRom. You can also use Cyanprimo, but you'll have flash the boot.img from RhythmicRom.
Now I've downloaded RythmicRom and I'm still stuck in a boot loop. I'm sorry for being a bit thick, but could you link some roms that would be compatible or explain what I need to be looking for?
Version I downloaded: http://forum.xda-developers.com/showthread.php?t=2147407
You'll need to download the 1.2 update, then extract the boot.img from that. The boot.img in the Rom doesn't work with the new update.
So I've been reading up on the issue over here: http://forum.xda-developers.com/showthread.php?t=2018518&page=14
and while I don't claim to understand it all, I believe I get the gist of it.
I also've managed to get RythmicRom working thanks to riggerman. I guess I'll just play the waiting game until someone rolls out a fix or just replace my phone (though that's very much in the long-run).
Once again, thanks to everyone and hopefully this will be the last we see of this mess.
Glad you got it running, and glad I could help.
Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk
If you don't agree ... stop reading and move on...
Background: Our phone has access to so much personal information that its scary if it fell into wrong hands. The only way to fix this is to encrypt phone. I did lot of research and here is a working solution that works for me - try at your risk.
Download Links:
a) Tested with ROM Stock 4.4.4 NH7 Galaxy S4 M919/Jfltetmo by @ShinySide
b) Tested with ROM |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
c) stock recovery AT&T S4 works with M919
d) Philz/CWM custom recovery
Encrypting with custom rom
1) Assume you are on custom recovery. - Backup everything first. Create a nandroid backup
2) Do a full wipe and install one of the two roms linked above (I have tested with few other roms ... none worked). Start the phone and set it up the way you want. Install all apps etc.
3) ODIN Stock recovery. See #c under download above. Its AT&T stock recovery but works for me. You need to know how to ODIN - find out. Doing this wrong will permanently damage your phone
4) Start your phone and turn on encryption. You will need to set lock type = password and will need to connect to charger and have 80% charge.
- Phone will do blank and stay blank for 20-30 minutes. Do not do anything. Encryption is happening behind the scenes.
- You might have to do this twice or thrice if it did not encrypt first time. For me the phone went blank first time and after 25 minutes it restarted but device was not encrypted. I redid the same steps and worked second time.
- If you interrupt the encryption process (battery pull or power up) you will see error message (encryption failed, reset device)
5) If all goes well you now have a password protected encrypted phone with custom rom!!! Check in Settings -> Security
6) You may install custom recovery ... but I don't see the point because you will need stock recovery to decrypt
To install another ROM
1) Reboot into stock recovery, then wipe data and cache (this removes encryption).
2) install your recovery of choice and install ROM using recovery. Philz/CWM
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
Tronicus said:
How to Flash a rom on an encrypted Android phone (specifically this one, the I9505 SGH-I337).
The Problem: Once encrypted, you can't decrypt it easily. When encrypting the phone android will tell you you can only decrypt it using a factory reset. Naturally you assume it's talking about the "Factory Data Reset" option found in Settings --> Backup and Reset. But noooo, Android is lying through its ****ing teeth. Then you'll assume you have to wipe everything from your custom recovery mod (CWM, TWRP, or one of those). Wrong again! You'll get beautiful "can't mount /data" messages and more bull****. I read about a workaround that required installing the new rom using ADB, but I had ingeniously disabled USB debugging prior to wiping everything, so I only got so far with that option (plus it's tediously long if you haven't installed all the necessary software already and don't feel like bricking your phone because you made a typo in the command line). So, apparently the only other way to really format that partition free of its encryption is to use a stock recovery. So:
Short Version for Godlike users who know automatically how to do all this **** without any help (mimicking how most help posts are finely detailed on this site): Flash stock recovery, wipe everything, flash your custom recovery and install your new rom.
Long version for us mortals who don't know everything and haven't already downloaded already every single bit of software on earth:
Backup all the stuff you want to save. This process will truly wipe EVERYTHING. You can do it manually, or you can use an app like Titanium Backup Pro to help you (find it on Google Play Store). Here's a nice guide which recommends what to restore and what not to restore: http://forum.xda-developers.com/showthread.php?t=1480343
Flash the stock recovery using Odin. You can download a stock recovery from here: http://forum.xda-developers.com/showpost.php?p=49687791&postcount=3 It's the link called "I337MK2stockrecovery.tar.md5" In case you don't know how to flash it with Odin, this short guide will help: http://forum.xda-developers.com/showthread.php?t=1506697
In step 6 replace "recovery.tar.md5" with the stock recovery you downloaded.
Wipe everything from the Stock recovery console. This little ****er will **** up the encryption all those sissies couldn't touch. You're welcome. You boot into recovery mode from a turned off phone by pressing simultaneously the volume up key + the home key + the power key until you see blue text appearing in the top left corner of your screen.
Reinstall your custom recovery. In my case I had installed the rom BEFORE flashing in the stock recovery (apparently it works, you just can't boot because of the encryption), so I was able to boot into the new rom before I returned to my custom recovery. Weird. Anyways, I recommend CWM. You can pick it up from this link: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/jflte
For some weird reason they call the I337 version the "jflte" version. It's bonkers. Click there, and download the latest version that ends with .tar.md5. This version is upgradable via Odin, which we already used. Use the same instructions used as when you upgraded the stock recovery rom.
Boot into your recovery mod and flash your rom like you usually do.
A word about TWRP: it cost me many hours of work and I don't recommend it. Its website is outdated, and recommends using GooManager (which is no longer mantained) and doesn't work anymore for this. GooManager suggests using a new, different app, which doesn't have the option of installing TWRP. Then I tried using their TWRP Manager app from play store and the image file wouldn't download. Then I tried manually selecting the image file in TWRP manager that I downloaded from their site for use via the ADB method, and it bricked my phone... twice (using two different methods the app sugested). I tried so much because in theory TWRP has the ability to decrypt android's 4.4 encryption, but after looking at their github site I noticed it was filled with people's reports (including people with the S4) on how it wouldn't work decrypting squat. So I gave up, and installed CWM in 30 seconds.
Click to expand...
Click to collapse
Disclaimer: I am not responsible for any damage or liability arising out of these steps. I did not invent anything, I just tried something. Only move forward at your risk
cnewsgrp said:
One of the things I needed was the ability to encrypt my phone (device only not external SD) for security purpose. Our phones today gives access to lot of information that I would rather not fall in wrong hands. I did lot of research and here is a working solution.
Credit goes to @Tronicus and his reply Flash a Rom on an Encrypted Android
The quote looks long however it is really very simple. To install another ROM
- Install and reboot into stock recovery, then wipe data and cache (this removes encryption).
- Then install your recovery of choice and install ROM using recovery. Philz/CWM
This has been tested working on |ROM|★KANGAKAT★|►KTU84P◄|4.4.4|Xposed|►8◄|6.26.14 by @iB4STiD
This did NOT work on a Touchwiz ROM by same developer
I have not tested any other ROM
Click to expand...
Click to collapse
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app
lordcheeto03 said:
I don't know if it matters too much or not, but the stock recovery you linked to is for the AT&T S4. A good rule of thumb is to never use Odin to flash anything not specifically for your particular device... In this case the M919.
Sent from my SGH-M919 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I have tested stock recovery on M919 .. it works
Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...
p-hil said:
Honestly im surprised its not talked about more since there is a big push for personal privacy when it comes to data. Encryption really is a pain in the ass to work with on android. Figuring out how to switch or update custom roms while encrypted will drive you insane. The easiest way is to just odin back to stock and start over, but that requires a computer anytime you need to flash anything.
I recently was trying out one of the 4.4.4 GPE roms and turned on encryption. It worked great until i started missing touchwiz and wanted to go back to HyperDrive TW. So the journey began...
First of all, i backed up everything to external storage since i knew everything on the internal storage would have to be wiped. I loaded the phone into recovery mode (using TWRP) and tried wiping, but all i got was a bunch of "Failed to mount" errors. Fine. Got the same error when trying to factory reset or wiping /system, /data, /cache, and anything else. Tried formatting to different file systems and then formatting back to the original but no luck. Fixing permissions didnt help. I just kept trying everything available multiple times.
Eventually it started wiping everything except the /data mount. Well... At least i could install new custom roms. Im not sure exactly what did it because i was just throwing everything at it. Anyways I got it to install, and booted into it. Nope.
Now it was saying I needed the password to decrypt the internal storage. It would detect wrong passwords fine, but as soon as i put the correct password in, it would allow me in, show the green android encryption picture, then blank screen. I thought it was just decrypting and setting up my rom but after a few hours my screen was still black and nothing was happening. Pulled battery and went back to TWRP.
I started wiping everything again and again and tried doing everything i could to wipe everything on the internal storage. Again, not sure what did it, but eventually got it all cleaned up and got a new rom installed and could boot into it.
The whole process probably took about 6-7 hours...
I dont even want to enable encryption on the new rom...
Click to expand...
Click to collapse
Yeah Encryption does not seem to work on TWZ roms. I tried on G Eye without luck.
I have updated op. Please check
Encryption will slow down your phone quite a bit. More battery usage + more CPU usage + slower phone = not worth it unless you've got some very private stuff you don't want being shared. Otherwise, 3rd party apps that lock a lot of files, can encrypt certain files, and hide others will do the trick perfectly well.'
Not trying to bash fully encrypting your phone, but I've tried it before and although I am very pro privacy, I had to eventually take it off due to all the extra hassle it created.
Don't know about slowing down. I am not seeing it. I feel differently about security.