Related
I recently attempted to root my N1 but after unlocking the bootloader and using superboot to gain root, everytime i boot up now i get an error that says "process system is not responding" I'm hoping this $600 paperweight can be turned back into a phone
You don't need to root if you unlocked the bootloader...
If there's a pulse, it probably ain't dead...
Download the ROM you wish to use, then use fastboot to flash a custom recovery, boot into recovery, wipe, then install the downloaded ROM.
Sent from my Nexus One using XDA App
I tried that with CM7 and it errors out on installing update.zip
rockchalk2526 said:
I tried that with CM7 and it errors out on installing update.zip
Click to expand...
Click to collapse
It's not an 'update.zip' if you are trying to flash a full ROM. Select 'Install ROM from SD' if you are rooted and using Rom Manager, otherwise reboot into your custom recovery and select 'flash .zip from SD'.
danger-rat said:
You don't need to root if you unlocked the bootloader...
Click to expand...
Click to collapse
Ok, i think i'm getting this now. You're saying that you don't need Root to flash a custom ROM if the Bootloader is unlocked, but for anything that requires Root (i.e Titanium Backup), you still need that additional step? So really, unlocking the Bootloader is pointless at the moment as using a combination of SOC and Rom Manager gives you the best of all worlds.
You don't need this step, since all the custom ROMs come pre-rooted. If you unlock the bootloader to install custom recovery.
Jack_R1 said:
You don't need this step, since all the custom ROMs come pre-rooted. If you unlock the bootloader to install custom recovery.
Click to expand...
Click to collapse
Thanks, it's all useful info.
It's worth noting that not everbody wants to use a custom ROM, but they may still want Root and the advantages it brings, on their stock ROM. (Me for one!!)
Still, if you only want root access, why unlock the bootloader, since unlocking the bootloader only gives the ability to flash images (unless you want to flash a rooted stock image, in which case why root the rom you have)?
Sent from my Nexus One using XDA App
You probably still have the stock recovery my friend. Cuz you won't find installing zip from sd card if you don't have a custom recovery. So flash ar or clock work to install a custom rom. Good luck.
Sent from my Nexus One using XDA App
How can I install two ROMS (MavROM and ICS) on my D3? one in SAFE MODE and one without.
what programs to use?
I already have MAVROM installed with SAFESTRAP from hashcode, but if i disable it, i get the stock rom.
thank you.
You have to use a bootstrap to flash your nonsafe before you install safestrap
Sent from my XT860 using xda premium
can you direct me to a link to that application? all I can find is safestrap from hashcode.
i have this one: "Droid3CWBootstrap"
http://www.appbrain.com/app/droid-x-recovery-bootstrap/com.koushikdutta.droidx.bootstrap
but how can I install zip with it?
I'm sorry I didn't see your last PMs
Anyway.
1) Start in stock ROM http://forum.xda-developers.com/showthread.php?t=1336980
(Or your non-safe ROM in safestrap and then remove safestrap)
2) After root, download bootstrap (I uploaded it) http://www.mediafire.com/?3u8xhmsp3lg5yfx
3) Install the APK and open the bootstrap app. Press install recovery then reboot recovery. You're now in bootstrap, not from using vol -+ etc (from your PM)
4) Flash mavrom using their CWM Recovery instructions
5) Once you got it setup, remove bootstrap app and install safestrap http://goo.gl/1pr5T
6) Reboot into safestrap and switch to safe system. Make a backup if you want before swithing. The switch will backup your current ROM (data), which is mavrom. Once in safe-system you can now flash ICS using the instructions. This will flash ICS in a different place. When you go back to non-safe system your mavrom will be restored.
Hope it's clear now
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
bogdan_wrc said:
thank you. sorry i "attacked" you with a lot of PMs. i tought you had enough
i will try it tomorrow.
Click to expand...
Click to collapse
Np aside from the fact that I'm not on XDA all day the notification is very small - most of the time I don't see it until the next day
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
zzandrewst said:
Will this method work with Liberty as well? I have never installed safestrap, but have bootstrap installed. I thought that I had read that safestrap does not work with Liberty ROM.
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Endoroid said:
Afaik hashcode fixed safestrap to work with all roms
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
zzandrewst said:
Great! I will give it a try, basically I would just install safestrap and use Liberty as my non-safe and then flash cm7 for my safe right?
Sent from my DROID3 using XDA App
Click to expand...
Click to collapse
you can't flash nonsafe with safestrap. Gotta use a bootstrap to flash your nonsafe, then install safestrap for flash safesystem. But yes, i have liberty as my nonsafe and ics as my safe
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
what to do?
I dont have the INSTALL from zip option, just UPDATE from zip.
that why i used safestrap.
but if I want to install the boot animation from RAZR, now in which location shall I do that? it used to be in /system/media folder. still there?
thank you, i managed to install both one successfully.
bogdan_wrc said:
Last time i tried to install MAVROM using CWM, i got the following error:
E:signature verification failed
when updating zip from card.
Installation aborted
Click to expand...
Click to collapse
I think thats because you tried to flash using original recovery, you said something with -+ volume buttons?
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
calash said:
Please be careful when doing this. While you "can" run 2 custom roms at once it is not what the safestrap system is designed for. Your non-safe rom should be stock and unaltered as it is what will save you from a fastboot flash should your safe rom go bad.
Sent from my HP Touchpad using Tapatalk.
Click to expand...
Click to collapse
Really a fastboot flash isn't such a big deal. I've done it more times than I can count. Takes 10 minutes. Id rather have my fav rom in nonsafe so I can use safe to testing new roms and new ics builds
Sent from my XT860 using xda premium
Is this dual boot system possible for my phone ? I would like to switch froyo and cynaogenmod !
Sent from my Optimus Me using XDA App
DoubleYouPee said:
Well there's no reason to have the stock rom on non-safe "in case things go bad" because you can also just use "easy unbrick" which will put your phone back to stock just as fast as switching from safe to non safe.
As said before the only reason where this would be handy is when an official OTA is released, although i heard you need to uninstall safestrap for it to work
Click to expand...
Click to collapse
I think you miss a key point. When you boot safestrap it starts in the non-safe system no matter what you do. Depending on your mode it then moves you to a totally separate partition on the device, preventing you from doing any harm to the boot rom.
The non-safe is key for the entire system to work. Yes it can be any rom, but you do put yourself at risk of losing two installs, including all the data.
Easy unbrick may be as fast to get to stock, but to rebuild back to where you were is going to take a lot longer.
In the end I am just advising caution, not telling people what to do. It does go against what the system was designed for and people should be aware of that before jumping off the ledge.
I understand, but now I have to go back to bootstrap to do essentially the same thing
Not sure if I follow you..
If you are only working in Safe-mode Rom the worst you can do is blow that rom up. Fixing it is just a matter of restoring your last backup via Safestrap recovery.
The problem with working in non-safe rom is that you can blow up both and lose your recovery. From that point you have to do Fastboot, install bootstrap, restore non-safe backup, install SafeStrap, restore Safemode backup.
Unless I am not understanding you correctly.
So I've had a nexus one for a while now, and recently I decided to root it. I managed to unlock my bootloader and flash clock work recovery. I then made a stupid mistake of trying to flash a rom before rooting my phone or backing up my rom. When I power on my phone now it just freezes on the boot animation. The only thing I can do is access recovery. What is the easiest way to root my nexus one in this condition or is there anyway of flashing a rom, hence fixing it? Preferably from a Mac but I may be able to get access to windows or linux. Thanks in advance
Sent from my U20i using xda app-developers app
moose.splash1 said:
So I've had a nexus one for a while now, and recently I decided to root it. I managed to unlock my bootloader and flash clock work recovery. I then made a stupid mistake of trying to flash a rom before rooting my phone or backing up my rom. When I power on my phone now it just freezes on the boot animation. The only thing I can do is access recovery. What is the easiest way to root my nexus one in this condition or is there anyway of flashing a rom, hence fixing it? Preferably from a Mac but I may be able to get access to windows or linux. Thanks in advance
Sent from my U20i using xda app-developers app
Click to expand...
Click to collapse
Turn off your phone, pop your SD card in your comp and copy the su.zip into it. Pop it back into your phone, boot into recovery and flash it on. Voila, root access!
Then wipe cache, dalvik-cache and all those and reflash the ROM again. You should be good to go.
BTW. I hope you are flashing a ROM which needs a stock HBOOT. Coz for JB ROMs, custom HBOOT is needed. Cheers!
sphinxcs898 said:
Turn off your phone, pop your SD card in your comp and copy the su.zip into it. Pop it back into your phone, boot into recovery and flash it on. Voila, root access!
Then wipe cache, dalvik-cache and all those and reflash the ROM again. You should be good to go.
BTW. I hope you are flashing a ROM which needs a stock HBOOT. Coz for JB ROMs, custom HBOOT is needed. Cheers!
Click to expand...
Click to collapse
Thanks a lot for the help! Do you know of any JB or ICS roms that do not require a special HBOOT? And where is the download for the su.zip you mentioned? Thanks a lot
All newer ROMs have a larger system partition requirement, why not flash an older gingerbread ROM that doesn't require black rose until you get the hang of flashing.
You don't need to flash superuser or busy box or anything first, just wipe all in recovery, flash ROM (plus anything else needed like gapps) reboot
Sent from my Nexus 4 using xda premium
moose.splash1 said:
Thanks a lot for the help! Do you know of any JB or ICS roms that do not require a special HBOOT? And where is the download for the su.zip you mentioned? Thanks a lot
Click to expand...
Click to collapse
demkantor said:
All newer ROMs have a larger system partition requirement, why not flash an older gingerbread ROM that doesn't require black rose until you get the hang of flashing.
You don't need to flash superuser or busy box or anything first, just wipe all in recovery, flash ROM (plus anything else needed like gapps) reboot
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
@demkantor is right. Basically you don't need su.zip coz most ROMs will have that flashed in already. I think the problem you were facing was because you did not wipe your cache/dalvik-cache and data before flashing on the ROM.
So my phone is stuck on the Motorola Dual Core logo after trying to flash a 4.4 Rom. I am still able to get to get into my recovery and into fastboot. No matter what rom I try to flash it still seems to go into the boot cycle. I have tried flashing to stock firmware with no luck. Anyone know what I should do?
After trying to flash stock again it seems like it is on but the screen is pitch black. When holding down the power button it gives the the vibrations after a little bit. Really not sure what this means. When plugging the device into the computer when the screen is black windows does recognize that there is a device and plays the noise but it does not show up in the devices list.
penser
ph3dia said:
After trying to flash stock again it seems like it is on but the screen is pitch black. When holding down the power button it gives the the vibrations after a little bit. Really not sure what this means. When plugging the device into the computer when the screen is black windows does recognize that there is a device and plays the noise but it does not show up in the devices list.
Click to expand...
Click to collapse
Is your bootloader unlocked?
What recovery are you using?
What ROM did you try to flash?
How did you flash it?
How are you trying to flash back to stock?
penser said:
Is your bootloader unlocked?
What recovery are you using?
What ROM did you try to flash?
How did you flash it?
How are you trying to flash back to stock?
Click to expand...
Click to collapse
1. Yes
2. Philz
3. OSE Latest nightly 4.4.2
4. Wiped everything and then flashed
5. Using Myth Tools
penser
ph3dia said:
1. Yes
2. Philz
3. OSE Latest nightly 4.4.2
4. Wiped everything and then flashed
5. Using Myth Tools
Click to expand...
Click to collapse
Alright, try flashing back to stock manually. Unzip the .zip, open the .xml in notepad(++) and on every line you'll see something along the lines of operation, partition, img. Open a command prompt in the location of the folder that contains the .xml (not the .zip, shift-click on white space in the folder and click open command prompt window here) and flash each line by typing
Code:
fastboot operation partition img
so each should look something like
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
Just don't do the one that says "GPT_MAIN1.img" or something of the sort (should be one of the first ones). Also type
Code:
fastboot -w
before you start.
same problem...
Hi all,
I have the same problem... I cannot flash CM 11.0 builds. In the first boot it works, but if you reboot, it will get stuck in Motorola's logo.
I also tried to restore original images (using sbf dot droid-developers dot org / phone.php?device=7 AT&T 4.1.1 image), but with no success.
CM 10.1 build works fine, so that's odd.
My fastboot bootloader says:
"
AP Fastbot Flash Mode (NS)
10.9B(*) (sha-2e68372 2012-11-17 23:33:08)
eMMC Info: Size 8GB
Device is UNLOCKED, Status Code: 1
...
"
Is your bootloader unlocked?
Yes
What recovery are you using?
Tried CWM 6.0.38 and Philz latest.
What ROM did you try to flash?
CM 11.1 nightly (cm-11-20131217-NIGHTLY-mb886.zip)
How did you flash it?
Wiped everything and then flashed
How are you trying to flash back to stock?
Using RSD Lite.
Thanks very much!
Did you try updating to Phiz latest here: http://forum.xda-developers.com/showthread.php?t=2552622
It is my understanding that the latest CWM is required to flash 4.4 and higher roms.
audit13 said:
Did you try updating to Phiz latest here: http://forum.xda-developers.com/showthread.php?t=2552622
It is my understanding that the latest CWM is required to flash 4.4 and higher roms.
Click to expand...
Click to collapse
Yes, I downloaded it last night... Is it better to use Philz or pure CWM?
My atrix HD broke however when it was working I was able to get cm11 on it by flashing using this recovery:
http://forum.xda-developers.com/showthread.php?t=2421418
When flashing cyanogen mod, wipe EVERYTHING basically /system /cache dalvik and then storage as well, this prevents the emulated/0/0/0/0/0 directory type of thing from happening, then after flashing factory reset clear cache and wipe dalvik then start up the phone. This has always worked for me and makes a squeaky clean install
Sent from my Nexus 10 using XDA Premium 4 mobile app
jubarim said:
Yes, I downloaded it last night... Is it better to use Philz or pure CWM?
Click to expand...
Click to collapse
I currently use Touch CWM which Philz is based upon. From my experience, the latest release for both will do the job.
anthony2424 said:
My atrix HD broke however when it was working I was able to get cm11 on it by flashing using this recovery:
http://forum.xda-developers.com/showthread.php?t=2421418
When flashing cyanogen mod, wipe EVERYTHING basically /system /cache dalvik and then storage as well, this prevents the emulated/0/0/0/0/0 directory type of thing from happening, then after flashing factory reset clear cache and wipe dalvik then start up the phone. This has always worked for me and makes a squeaky clean install
Sent from my Nexus 10 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks man!! That really worked!
jubarim said:
Thanks man!! That really worked!
Click to expand...
Click to collapse
You're welcome, glad to help
Sent from my Nexus 10 using XDA Premium 4 mobile app
I had my phone download this and then just copied it off. My phones build was 98.18.94. Not sure what the difference between this and 98.30 is. I'm rooted so I haven't installed it but it's here for anyone that wants it. My phone downloaded a different version than I found online. It was version 182.46.10XT907.Verizon.en.US. I don't know what other phone builds it will work with. Either way use at your own discretion.
Here is the update for phones running 98.18.94
https://drive.google.com/file/d/0BxU6nmErI6QFS0M1Z0o3QmlrTmM/edit?usp=sharing
Here is the update for phones running 98.30.1
https://drive.google.com/file/d/0BxU6nmErI6QFRkdyUGdxZk9TeW8/edit?usp=sharing
Did anybody try it with unlocked bootloader?
Bootloader still unlocked or OTA relock it?
St.Noigel said:
Did anybody try it with unlocked bootloader?
Bootloader still unlocked or OTA relock it?
Click to expand...
Click to collapse
My understand is that it should leave the bootloader unlocked. It will replace the recovery, radio and other system partitions. If you removed anything from the /system/apps folder then I think it will fail/abort install. I've removed some so I need/want to RSD back to stock and then update but if I do then I'll lose root which I use.
Yes, and with SELinux and some other enhancements in KitKat I wouldn't even take a future root for granted.
remijenkins said:
I had my phone download this and then just copied it off. My phones build was 98.18.94. Not sure what the difference between this and 98.30 is. I'm rooted so I haven't installed it but it's here for anyone that wants it. My phone downloaded a different version than I found online. It was version 182.46.10XT907.Verizon.en.US. I don't know what other phone builds it will work with. Either way use at your own discretion.
https://drive.google.com/file/d/0BxU6nmErI6QFS0M1Z0o3QmlrTmM/edit?usp=sharing
Click to expand...
Click to collapse
Posting updates on how to use this thru the stock recovery.
This is how it is supposed to be used:
1 - Flash LATEST stock SBF of JB thru RSD. (Android 4.1.2
Blur_Version.98.30.1.XT907.Verizon.en.US)
2 - After RSD flash reboot phone on stock recovery and proceed to install update from SD card, here select the file that is provided at the beginning of the thread.
3 - After this first flash completes, phone is going to reboot in recovery again, to open the menu of this specific recovery, the combo of the buttons is power + vol up.
4 - proceed to install from sd card again and select the same file that you selected on the second step.
5 - Wait for it to finish
6 - Wipe data/factory reset
7 - Select restart system, Phone will restart in KK, enjoy guys.
Keep in mind that you have to follow the explanation at the beggining of the thread or this one, if you dont follow this steps like this, you wont be able to install this update or you wont be able to finish installing the update.
is this the offical KK update?
Yes it is official. Like I posted earlier, its OTA from Verizon.
Sent from my XT907 using XDA Free mobile app
And it works like a charm.
roxy.schram said:
I had my phone download this and then just copied it off. My phones build was 98.18.94. Not sure what the difference between this and 98.30 is. I'm rooted so I haven't installed it but it's here for anyone that wants it. My phone downloaded a different version than I found online. It was version 182.46.10XT907.Verizon.en.US. I don't know what other phone builds it will work with. Either way use at your own discretion.
https://drive.google.com/file/d/0BxU6nmErI6QFS0M1Z0o3QmlrTmM/edit?usp=sharing
Click to expand...
Click to collapse
Where does one locate the file to copy? Id like to share... I am downloading the ota now and I'm currently on 98.30.1.
[DELETE]
Can you flash this using a custom recovery?
Sent from my XT907 using Tapatalk
H0LT3R said:
Can you flash this using a custom recovery?
Sent from my XT907 using Tapatalk
Click to expand...
Click to collapse
I doubt it. It's for stock phones. It will need a stock recovery I do believe.
Hmmm..
My razr is stock & rooted, and I have manually removed several bloat apps. If I attempt to this update ota could it cause any harm to my system aside from possible abort/update fail? Will it remove root? Gracias.
It won't install... or its not suppose to.
Sent from my XT907 using XDA Free mobile app
Does it lose root after OTA?
Sent from my DROID RAZR M using XDA Free mobile app
allen_ho said:
Does it lose root after OTA?
Sent from my DROID RAZR M using XDA Free mobile app
Click to expand...
Click to collapse
Yes.
allen_ho said:
Does it lose root after OTA?
Click to expand...
Click to collapse
My understanding is you can retain some root functionality using SuperSU Pro's Survival Mode. I believe you'll still lose R/W capability.
The best approach would be to unlock your bootloader. I've heard some success with custom recovery, though stock recovery would be best bet.
triloger said:
Posting updates on how to use this thru the stock recovery.
This is how it is supposed to be used:
1 - Flash LATEST stock SBF of JB thru RSD. (Android 4.1.2
Blur_Version.98.30.1.XT907.Verizon.en.US)
2 - After RSD flash reboot phone on stock recovery and proceed to install update from SD card, here select the file that is provided at the beginning of the thread.
3 - After this first flash completes, phone is going to reboot in recovery again, to open the menu of this specific recovery, the combo of the buttons is power + vol up.
4 - proceed to install from sd card again and select the same file that you selected on the second step.
5 - Wait for it to finish
6 - Wipe data/factory reset
7 - Select restart system, Phone will restart in KK, enjoy guys.
Keep in mind that you have to follow the explanation at the beggining of the thread or this one, if you dont follow this steps like this, you wont be able to install this update or you wont be able to finish installing the update.
Click to expand...
Click to collapse
This method did not work for me after i flashed back to 98.30.1 the stock recovery doesnt see the update and i just get the android logo. When i go to software updates the service is unavailable/
my bootloader has unlock. and does it mean I can have root permission after I flash the stock zip package?
OK here it is, black and white and very simple:
Bootloader Locked - NO ROOT, NO CUSTOM RECOVERY.
Bootloader Unlocked - CWM Recovery and FULL ROOT with SuperSu.
That's it, no if ands or buts.
Sent from my XT907 using Tapatalk