Related
hey guys i just got my nexus one 2.3.3
im confused what 2 do first
root, unlock bootloader
what 2 do first?
and i preffer to do all these things WITHOUT adb, bcoz adb never works with me
You can't unlock bootloader without ADB (or actually without fastboot, but if you can't get ADB to work, then you probably won't be able to get fastboot to work - since they work the same way).
My suggestion is - do nothing. At least until you'll be able to follow one of the guides and get ADB and fastboot to work. Then you can decide yourself, whether you want the bootloader unlocked or not, and how will rooting benefit you.
what are the benefits of unlocked bootloader?
i just wanted it to get it rooted and flash CM7 on it
It has been discussed a lot, please search to get A LOT of answers.
In a very short version, the benefits are:
Safe radio updates (using fastboot)
Ability to flash whatever you want whenever you want - which is, permanent ability to have root access, regardless of the currently used OS.
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
shiyou said:
but is it possible to flash CM7 rom without unlocking bootloader?
whenever i boot my nexus one, there is this little lock icon on the bottem that is "unlocked"
is my bootloader unlocked?
Click to expand...
Click to collapse
If there's lock icon at the bottom of boot splash screen, it means the bootloader is already unlocked. Is it used one?
yes its used, i guess that guy alrdy unlocked it for me
another problem
i have serius wifi issue, its different from the other wifi problem
if i connect to my wifi its authenticating, then disabled
i dont even go to sleep its just says disabled after authenticating, i tried reconecctint but same things happens again...
i installed wifi fixer but that doesnt work either
also, my 3g drops after 4 sec and i cant get it to work afterwards
Flash a new ROM, wipe your data, and try.
Repeat.
If the problems will still persist - they're in HW and you can't do anything about them.
i tried factory reset but didnt work...
This is exactly the reason why I suggest not touching your phone.
You either don't understand what exactly I'm guiding you to do, or don't understand the difference between various maintenance/repair operations. Flashing a new ROM and wiping user data from custom recovery ISN'T the same as doing "factory reset" from within already-installed ROM. Flashing 2 ROMs with different base (for example, lightly modified stock and CM7, or CM7 and MIUI, etc) introduces enough difference on the SW size to (almost) make sure that any problem which persists in both new ROMs, is coming from HW.
In any case, I suggest either waiting for someone with much more patience than myself (which isn't hard - patience isn't one of my strengths) to explain you some basics that you're not willing to learn yourself by reading, reading and some more reading, or to give your phone to someone who knows what he's doing.
dude....
i rooted and flashed many roms b4, this isnt my first android phone
i just got confused data wipe with factory reset....
Ok well now I need to know if you have a custom recovery, if so then just 5X wipe plus 3X system wipe and flash a new ROM, if not then do you have root access if not I'll walk you through the process.
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
i know how 2 root,flash,wipe, nandroid and all
i did it many times b4
i think i wont use nightly builds, but a stable? or RC?
which should i take?
How about cm7.1 RC1 that is the latest version of cyanogen mod.
rugmankc said:
shiyou
You are in good hands with Dude
Couple points:
Don't use Clockwork Mod 3.+ as recovery--which seems to be your next step--get a lower version
I prefer Amon_Ra 2.2.1 for my recovery
BACKUP phone (NANDROID) as soon as you get the recovery
Look thru Cyanogen thread from OP page and last few dozen pages
Cyanogen flashes a little differnet with having to flash gapps separate and flashing Dark Tremor's a2sd after each Nightly flash
Click to expand...
Click to collapse
why not clockwork recovery 3? the cyanogenmod rc1 states that i need that?
should i use gingerbeak? im on 2.2.3 and install the recovery afterwards?
ok i rooted it with gingerbreak and flashed clockworkmod recovery on it
after that i went into recovery and couldnt find nandroid backup so i rebooted again
i tried to make a backup via rom manager and it ended up with a "!" icon
i tried to go into recovery again and again i got the "!" icon
I don't know anything about Gingerbreak
But, on CWMod 3.+, it has been unstable for a lot of people--I don't recommend it
If you have Rom Manager--flash something like 2.5.1.4??
Still recommend Amon_Ra
I am not sure, but if you get the exclamation, you may not be rooted
If you are experienced at flashing, I would as another poster suggested--get to know your phone and study hard info from the Rom threads you want to try before trying.
What color was recovery--did it say ClockWork
I don't think you will see the name Nandroid in Clockwork--just Clockwork backups
A couple more suggestions, if you want
Back up sd card regularly--you will lose it on occasion--if you need to reformat it, use sdformatter outside of phone
Partition sdcard with zero swap
Wipe all (data/caches) multiple times before flashing new rom, including System
I've researched several forums for help with my GPS lock but I would like a little guidance from someone more experienced before I proceed with a fix. I'm comfortable flashing and I'm starting from the following configuration:
Starting Point:
1. Rooted running CM-10.2-20131016-Nightly, Baseband 1.00.20.0913_3, Kernel 3.410-CM-g5afe42c [email protected] #1
2. Performed a Nandroid backup with CWM Recovery v6.0.3.6
My questions are as follows:
1. Do I need to S-Off to fix this issue, and if so, what's the most efficient way of doing this starting from my CM nightly build and CWM version?
2. I have GPS status from the Android Market on there already and I've cleared GPS data. Do I need to reflash stock ROM to download the new agps data or can I do it from CM?
3. If I have to reflash stock to perform this GPS trick, will my backup restore everything back to the way it is, including installed applications and settings, or do I have to restore all my preferences, accounts, etc.
I've been lucky thus far with ROM flashing and never needed to restore a backup so I'm unclear the level of effort after a stock to CM swap maneuver. Thanks in advance for the help.
:good:
dhalmo said:
I've researched several forums for help with my GPS lock but I would like a little guidance from someone more experienced before I proceed with a fix. I'm comfortable flashing and I'm starting from the following configuration:
Starting Point:
1. Rooted running CM-10.2-20131016-Nightly, Baseband 1.00.20.0913_3, Kernel 3.410-CM-g5afe42c [email protected] #1
2. Performed a Nandroid backup with CWM Recovery v6.0.3.6
My questions are as follows:
1. Do I need to S-Off to fix this issue, and if so, what's the most efficient way of doing this starting from my CM nightly build and CWM version?
2. I have GPS status from the Android Market on there already and I've cleared GPS data. Do I need to reflash stock ROM to download the new agps data or can I do it from CM?
3. If I have to reflash stock to perform this GPS trick, will my backup restore everything back to the way it is, including installed applications and settings, or do I have to restore all my preferences, accounts, etc.
I've been lucky thus far with ROM flashing and never needed to restore a backup so I'm unclear the level of effort after a stock to CM swap maneuver. Thanks in advance for the help.
:good:
Click to expand...
Click to collapse
if you restore a backup everything will be the same as it was when you backed it up, settings, data, etc. all the same
Is there anyone else out there with this same problem or a solution?
dhalmo said:
I've researched several forums for help with my GPS lock but I would like a little guidance from someone more experienced before I proceed with a fix. I'm comfortable flashing and I'm starting from the following configuration:
Starting Point:
1. Rooted running CM-10.2-20131016-Nightly, Baseband 1.00.20.0913_3, Kernel 3.410-CM-g5afe42c [email protected] #1
2. Performed a Nandroid backup with CWM Recovery v6.0.3.6
My questions are as follows:
1. Do I need to S-Off to fix this issue, and if so, what's the most efficient way of doing this starting from my CM nightly build and CWM version?
2. I have GPS status from the Android Market on there already and I've cleared GPS data. Do I need to reflash stock ROM to download the new agps data or can I do it from CM?
3. If I have to reflash stock to perform this GPS trick, will my backup restore everything back to the way it is, including installed applications and settings, or do I have to restore all my preferences, accounts, etc.
I've been lucky thus far with ROM flashing and never needed to restore a backup so I'm unclear the level of effort after a stock to CM swap maneuver. Thanks in advance for the help.
:good:
Click to expand...
Click to collapse
Make a backup of current cm in twrp....... everything but storage options...... flash sense based rom...... update prl/profile(since your already in sense) go into maps while on data connection(found that works better than using wi-fi) maps will get a gps lock.... reboot into twrp restore backup of cm and than i always fix permissions and wipe dalv and cache... reboot into cm and profit hope this helps, never had a problem with gps when doing this.
**edit** a backup in twrp will back everything in the os up......apps....texts....settings....everything
Robisgnarly said:
Make a backup of current cm in twrp....... everything but storage options...... flash sense based rom...... update prl/profile(since your already in sense) go into maps while on data connection(found that works better than using wi-fi) maps will get a gps lock.... reboot into twrp restore backup of cm and than i always fix permissions and wipe dalv and cache... reboot into cm and profit hope this helps, never had a problem with gps when doing this.
**edit** a backup in twrp will back everything in the os up......apps....texts....settings....everything
Click to expand...
Click to collapse
:good:
A few questions on your procedure:
1. Will any sense based ROM work or do I need to use an RUU with stock recovery?
2. Can I perform this procedure with S-On, which is my current state?
If this works successfully, I will write a small and detailed guide for other people to use. Thanks.
dhalmo said:
:good:
A few questions on your procedure:
1. Will any sense based ROM work or do I need to use an RUU with stock recovery?
2. Can I perform this procedure with S-On, which is my current state?
If this works successfully, I will write a small and detailed guide for other people to use. Thanks.
Click to expand...
Click to collapse
1) any sense based will work.
2) not sure if the one is the same way with s-on.... but if so you will have to extract the boot.img from the rom and flash that via adb in bootloader than flash the rom in twrp.
Suggestion...... Go s-off your phone makes life simpler and makes playing more fun and much more safe
Greetings, and TIA for any replies.
I recently flashed ViperOne 3.0RC1 on my dev edtion HTC One. So far so good. However, I realized after the fact that with this ROM, I'm unable to successfully run revone and gain s-off (and therefore I can't upgrade my firmware).
So, I have two questions:
-I read in various places that people had success running revone under ViperOne 2.7. Does this sound like a reasonable thing to try, rather than trying to roll back to a completely stock ROM?
-Assuming that the answer to the above is 'yes', is it possible/safe to dirty flash 2.7 over 3.0RC1? I know one can do the opposite (dirty flash when upgrading) but I haven't been able to find any information about a dirty downgrade.
Again, thanks for any pointers. If somebody has a suggestion for a more elegant way to achieve s-off and upgrade my firmware, I'd love to learn about it.
Cheers,
/alex
r0shi said:
Greetings, and TIA for any replies.
I recently flashed ViperOne 3.0RC1 on my dev edtion HTC One. So far so good. However, I realized after the fact that with this ROM, I'm unable to successfully run revone and gain s-off (and therefore I can't upgrade my firmware).
So, I have two questions:
-I read in various places that people had success running revone under ViperOne 2.7. Does this sound like a reasonable thing to try, rather than trying to roll back to a completely stock ROM?
-Assuming that the answer to the above is 'yes', is it possible/safe to dirty flash 2.7 over 3.0RC1? I know one can do the opposite (dirty flash when upgrading) but I haven't been able to find any information about a dirty downgrade.
Again, thanks for any pointers. If somebody has a suggestion for a more elegant way to achieve s-off and upgrade my firmware, I'd love to learn about it.
Cheers,
/alex
Click to expand...
Click to collapse
Anytime that you change base, always do a full wipe, whether it's noticable or not chances are you will have problems sooner or later.
If it were me i would never dirty flash between bases.
dladz said:
Anytime that you change base, always do a full wipe, whether it's noticable or not chances are you will have problems sooner or later.
Click to expand...
Click to collapse
A dev of Viper ROM has clearly stated multiple times that you do not need to wipe flashing 3 over 2.7, even when it is a new base, see here and especially here.
So in general, yes, you are right, but in this case not.
Now about the original question:
How about you make a Nandroid backup and dirty flash 2.7 back and see if it works? If you get problems, re-flash your backup.
Cheers, Ingo =;->
If you are mainly downgrading for S-off, I'd make a nandroid of your 3.0 & flash a new version of 2.7 (just so you don't have any issues while running RevOne). I dirty flashed 3.0 on top of 2.7 to test it out (I couldn't give up my tweaks!), and there have been comments in the Dev thread saying there aren't issues. But like the previous commenter said, it's always best to wipe and start fresh with a new base.
TLDR: Backup, Wipe, Flash clean! Just in case.
Thanks, all, for the replies. I wasn't really thinking correctly about how to use nandroid backups to my advantage.
One last bit of clarification: the nandroid backup will include all apps, app settings, and system settings? (read: candy crush game progress and SMS history ) It does not, however, include user data (read: music)? What about a custom kernel (not that I even have one right now, just curious)?
I'm always sort of fuzzy on what exactly gets grabbed by a nandroid (which partitions, etc).
Again, many thanks.
/alex
Curly060 said:
A dev of Viper ROM has clearly stated multiple times that you do not need to wipe flashing 3 over 2.7, even when it is a new base, see here and especially here.
So in general, yes, you are right, but in this case not.
Now about the original question:
How about you make a Nandroid backup and dirty flash 2.7 back and see if it works? If you get problems, re-flash your backup.
Cheers, Ingo =;->
Click to expand...
Click to collapse
I absolutely don't care who says it's ok or not, i've had a tonne of phones and i've flashed more rom's than i could even mention, when you do a dirty flash you are much more prone to problems, corruption and issues than with a full wipe, don't try to bash someone who knows what they're talking about.
Flashing a rom the dirty way can and does end with problems.
Why do you think people who bug report don't dirty flash? I've bug reported for many dev's for many phones and my reports are consistent and true, that is something you will not get if you don't do a full wipe.
Reason being for this is because no two phones are the same, so for one person it may work perfectly and for someone else it won't, it's that level of inconsistency that means that a full wipe is always recommended.
r0shi said:
Thanks, all, for the replies. I wasn't really thinking correctly about how to use nandroid backups to my advantage.
One last bit of clarification: the nandroid backup will include all apps, app settings, and system settings? (read: candy crush game progress and SMS history ) It does not, however, include user data (read: music)? What about a custom kernel (not that I even have one right now, just curious)?
I'm always sort of fuzzy on what exactly gets grabbed by a nandroid (which partitions, etc).
Again, many thanks.
/alex
Click to expand...
Click to collapse
A nandroid will include all data on your phone, except what is stored on your 'sd card' partition. So a kernel is saved with a nandroid. So if you are switching between kernels backup and wipe cache/dalvik between.
Hello,
I've always used my Nexus 6 decrypted since i bought it. I've used some Custom ROMs and went back to stock again
Now, with Android 6.0.1 i went and flashed the stock images but i completely forgot about about encryption. Since the kernel changed i flashed the original boot.img and then franco Kernel after. It was fine until now and i didn't remember about it.
Lately i've been getting some hicups and lag. I updated my kernel to the latest r37 and searched the XDA forums for someone having the same issues as myself but i didn't find anyone or at least with similiar issues. That's when i remembered about encryption. It encrypted (obviously!) after flashing the original boot.img and it's probably what's causing the issue.
I've searched around about doing some TWRP backups (never used in the past tbh) but since i have so many stuff already i don't feel like having everything installed from base and restoring (too many SMS and takes ages to restore...) but i still have some doubts that i couldn't find.
My main questions are:
- are TWRP backups reliable?
- can i backup encrypted and restore to decrypted?
- To decrypt, can i just make fastboot format userdata and then restore backup? or do i need to start normally to create partitions?
Those are my main questions about my problem. If someone can help me (i'm sure someone will) i'd be very grateful!
twrp backups are reliable, and have been backing up/restoring for years now. can you backup encrypted but restore decrypted, i have no idea. when you decrypt, itll delete every single file in your phone, so you would have to move the backup to your computer, then back aftet decrypting. and no, to decrypt you need to flash a kernel that allows for decryption, then format user data(which will remove all your files as well).
simms22 said:
twrp backups are reliable, and have been backing up/restoring for years now. can you backup encrypted but restore decrypted, i have no idea. when you decrypt, itll delete every single file in your phone, so you would have to move the backup to your computer, then back aftet decrypting. and no, to decrypt you need to flash a kernel that allows for decryption, then format user data(which will remove all your files as well).
Click to expand...
Click to collapse
thanks for the reply,
I know about the kernels and i know about moving the files (makes sense after all )
I'm just worried about backing up encrypted and then restoring decrypted.
Another quick question, when restoring is it just userdata or system as well ?
informaniako said:
thanks for the reply,
I know about the kernels and i know about moving the files (makes sense after all )
I'm just worried about backing up encrypted and then restoring decrypted.
Another quick question, when restoring is it just userdata or system as well ?
Click to expand...
Click to collapse
i just dont know if itll work.
its restoring EVERYTHING. userdata, system, boot.img.. its like you take a photo of everything on your phone right now. then restore it in a year, and itll be exactly like right before you backed it up. exactly.
Restoring a backup of an encrypted data partition will result in you having bit for bit the same as what you backed up, encryption included.
informaniako said:
Hello,
I've always used my Nexus 6 decrypted since i bought it. I've used some Custom ROMs and went back to stock again
Now, with Android 6.0.1 i went and flashed the stock images but i completely forgot about about encryption. Since the kernel changed i flashed the original boot.img and then franco Kernel after. It was fine until now and i didn't remember about it.
Lately i've been getting some hicups and lag. I updated my kernel to the latest r37 and searched the XDA forums for someone having the same issues as myself but i didn't find anyone or at least with similiar issues. That's when i remembered about encryption. It encrypted (obviously!) after flashing the original boot.img and it's probably what's causing the issue.
I've searched around about doing some TWRP backups (never used in the past tbh) but since i have so many stuff already i don't feel like having everything installed from base and restoring (too many SMS and takes ages to restore...) but i still have some doubts that i couldn't find.
My main questions are:
- are TWRP backups reliable?
- can i backup encrypted and restore to decrypted?
- To decrypt, can i just make fastboot format userdata and then restore backup? or do i need to start normally to create partitions?
Those are my main questions about my problem. If someone can help me (i'm sure someone will) i'd be very grateful!
Click to expand...
Click to collapse
Restoring those sms may just cause you to have issues. Keep that in mind. Restoring system data can cause things to be come unstable.
The data is still just data.. Encryption only effects how it stored... It can still be read and written if you have the key.
With encrypted can you take a photo off your phone? Yes.
In the same way you can make a backup, then pull it off your phone and store it on your computer. The encryption just means that when that data is stored, its scrambled.... When its read blocks of scrambled data are read into memory, and the key is used to unscramble them... The data is the data though, whether its been put through encryption or not.
I have a Tmobile phone, but I have a rooted kernel, is there a way I could just flash a stock kernel through recovery and be done with root but keep from wiping all my data? Also links to such kernels would be appreciated, cause I'm not sure which to use.
You have to have a custom recovery installed via ODIN
Download stock firmware (there are several places around here to find it, and if you can't you can get it at Sammobile.com)
Boot into custom recovery and wipe all partitions EXCEPT INTERNAL STORAGE
Boot into download mode DIRECTLY FROM RECOVERY
flash stock firmware via ODIN
Profit
My apologies, but this will wipe my phone, I just want to replace the kernel with a non rooted version, not that firmware.
RighteousJoe said:
My apologies, but this will wipe my phone, I just want to replace the kernel with a non rooted version, not that firmware.
Click to expand...
Click to collapse
It will wipe your apps and settings (SMS conversations), but all of your personal data (Photos, movies, music) will still be there and the firmware includes the stock kernel.
As far as I know, this is the only way to revert to stock without losing all your data. I don't think you can simply flash a stock kernel, though I could be way off on that one. This method is how I reverted to stock.
Yeah I appreciate your input, but I have certain needs with the current data on my phone I can't part with yet. But hopefully somebody knows of a way, Thank you.
RighteousJoe said:
Yeah I appreciate your input, but I have certain needs with the current data on my phone I can't part with yet. But hopefully somebody knows of a way, Thank you.
Click to expand...
Click to collapse
You can backup all of the data you need. Since all of your internal storage will be untouched, you won't need to back that up, but if you need your SMS and call logs and whatnot that stuff can all be backed up. What data do you need exactly?
I have certain game data, that I need lol.
Akw6190 said:
You can backup all of the data you need. Since all of your internal storage will be untouched, you won't need to back that up, but if you need your SMS and call logs and whatnot that stuff can all be backed up. What data do you need exactly?
Click to expand...
Click to collapse
Hi,
after you reverted back to stock, will you be able to receive and apply official OTAs?
xijun824 said:
Hi,
after you reverted back to stock, will you be able to receive and apply official OTAs?
Click to expand...
Click to collapse
Yes, however most, if not all of the ROM devs are going to update their ROMs to Marshmallow fairly quickly.