Related
Every single one of them are failing @ System.
I have flashed many roms and have yet to see this issue.
I have even tried to install a nandroid and they say system.img not found, skipping restore of System
my quadrant before doing anything was ~950 so im assuming no lagfix was present.
did you flash back to stock with odin1click??
ed116 said:
did you flash back to stock with odin1click??
Click to expand...
Click to collapse
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...
iamamp3pimp said:
no, i typically never do.
i have a stock eclair rooted nandroid but eh.
trying to avoid using odin right this minute...
Click to expand...
Click to collapse
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.
im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm
ccdoggy said:
Going back to stock is the only safe way to install a rom imo.
Do a proper stock install and watch all the roms work.
Click to expand...
Click to collapse
+100000000
iamamp3pimp said:
im sure it will.
im just trying to learn why. it all started when i went to install SetiroNs 1.4.6 cwm
Click to expand...
Click to collapse
Because it is the phone...not the rom or kernel...unless you had a bad flash to begin with.
This is why it is recommended when switching to different roms...and even sometimes flashing updates to certain roms ...that it is the most prudent thing to do, to head off these types of issues that come up sometimes. It is also recommended to do a master clear as well...and I usually go one step further and wipe and format the drives and do a factory reset. Sometimes doing it more than just once too. It may be a royal PITA...but...the alternative is what you are experiencing it seems...
Mac
is there a way to tell which filesystem is being used?
i have CWM 2.5.1.2
my Axura restore did work.......so i at least have a phone for the moment
Here are my doubts: Captivate on 2.2 no root
1)Is andromeda3 and phoenix unleashed based on android 2.2 or 2.3?(recent versions)
2)I used Odin v1.0 to go back to stock,what is the difference betwen Odin 1.0 and Odin 1.7?
3)Are there any other methods to go back to stock, I have read "Use odin 1.0 in case of emergency"?
4)How can I back up my stock rom after root in the case I want to flash back and unroot?
5)Do I need to go back to stock every time I want to flash a different rom?
6)Andromeda3 has a ursa minor kernel do i need this to install there rom or can i just flash the rom without ursa minor?
7)In the phoenix unleashed thread it says to flash there custom rom use odin to go back to stock,does this mean i have to do the whole back to stock+root again?(Staring from scratch in other words)
8)Will flashing rage patch while using andromeda3 or phoenix unleashed mess something up?
I think that's all please put the same number of the question in front of the answer so I know witch answers witch.Thank you in advanced.
Here are my doubts: Captivate on 2.2 no root (Don't doubt the captivate - it can handle it! Isn't autocorrect great?)
1)Is andromeda3 and phoenix unleashed based on android 2.2 or 2.3?(recent versions)
Andromeda3 is 2.2 based, and as much as I can see, so is Phoenix Unleashed.
2)I used Odin v1.0 to go back to stock,what is the difference betwen Odin 1.0 and Odin 1.7?
They're the same program, just different revisions. I can't say what specifically has changed between the two of the, but my guess would be 1.7 would have more features/bug fixes/etc.
3)Are there any other methods to go back to stock, I have read "Use odin 1.0 in case of emergency"?
Going back to stock will consist of using some version of Odin (one-click or otherwise) to reflash the stock rom to your phone
4)How can I back up my stock rom after root in the case I want to flash back and unroot?
From a rom standpoint, there's no need to back up your stock rom, unless you have settings done a specific way you want. Flashing to stock with automatically put you back at a stock, unrooted state. I would recommend doing a nandroid backup from the CWM recovery menu (assuming you have CWM) and copying the EFS folder to a safe location before moving forwards.
5)Do I need to go back to stock every time I want to flash a different rom?
Need to? No. Is it a good idea? There's debate on this, but in general, it's not a bad idea to flash back to stock (relative to where you are - GB/Froyo/Eclair) before flashing a new rom. It will help keep things tidy.
6)Andromeda3 has a ursa minor kernel do i need this to install there rom or can i just flash the rom without ursa minor?
To the best of my knowledge, it is included in the rom - there's nothing to do on your part, as it will flash with the rom.
7)In the phoenix unleashed thread it says to flash there custom rom use odin to go back to stock,does this mean i have to do the whole back to stock+root again?(Staring from scratch in other words)
If you're still on stock Eclair, you do not need to go back to stock. If you're on something else, you will need to go back to stock, but you shouldn't have to root, as most roms now work without being rooted.
8)Will flashing rage patch while using andromeda3 or phoenix unleashed mess something up?
It won't hurt anything - it just covers a security flaw.
I think that's all please put the same number of the question in front of the answer so I know witch answers witch.Thank you in advanced.
jmtheiss said:
Here are my doubts: Captivate on 2.2 no root (Don't doubt the captivate - it can handle it! Isn't autocorrect great?)
1)Is andromeda3 and phoenix unleashed based on android 2.2 or 2.3?(recent versions)
Andromeda3 is 2.2 based, and as much as I can see, so is Phoenix Unleashed.
2)I used Odin v1.0 to go back to stock,what is the difference betwen Odin 1.0 and Odin 1.7?
They're the same program, just different revisions. I can't say what specifically has changed between the two of the, but my guess would be 1.7 would have more features/bug fixes/etc.
3)Are there any other methods to go back to stock, I have read "Use odin 1.0 in case of emergency"?
Going back to stock will consist of using some version of Odin (one-click or otherwise) to reflash the stock rom to your phone
4)How can I back up my stock rom after root in the case I want to flash back and unroot?
From a rom standpoint, there's no need to back up your stock rom, unless you have settings done a specific way you want. Flashing to stock with automatically put you back at a stock, unrooted state. I would recommend doing a nandroid backup from the CWM recovery menu (assuming you have CWM) and copying the EFS folder to a safe location before moving forwards.
5)Do I need to go back to stock every time I want to flash a different rom?
Need to? No. Is it a good idea? There's debate on this, but in general, it's not a bad idea to flash back to stock (relative to where you are - GB/Froyo/Eclair) before flashing a new rom. It will help keep things tidy.
6)Andromeda3 has a ursa minor kernel do i need this to install there rom or can i just flash the rom without ursa minor?
To the best of my knowledge, it is included in the rom - there's nothing to do on your part, as it will flash with the rom.
7)In the phoenix unleashed thread it says to flash there custom rom use odin to go back to stock,does this mean i have to do the whole back to stock+root again?(Staring from scratch in other words)
If you're still on stock Eclair, you do not need to go back to stock. If you're on something else, you will need to go back to stock, but you shouldn't have to root, as most roms now work without being rooted.
8)Will flashing rage patch while using andromeda3 or phoenix unleashed mess something up?
It won't hurt anything - it just covers a security flaw.
I think that's all please put the same number of the question in front of the answer so I know witch answers witch.Thank you in advanced.
Click to expand...
Click to collapse
Thank you this is very informative and what i meant by "Here are my doubts: Captivate 2.2 no root" is that my captivate is on stock 2.2 without root just to be clear.
I got one more question:
Whats is the EFS folder?
Im going to tell you my former situation so you can tell me what I did wrong:
I rooted my phone with super one click at the time
I used rom manager it was also supposed to save a backup of my stock rom
Somewhere in the CWM I was supposed to save the stock rom just in case something went wrong(i thought i did it correctly)
I flashed Cognition everything was great
I wanted to eliminate Cog when i went to CWM to find my back up of stock it didnt work it stayed in Cog
I have read that flashing other roms while having a custom rom isnt recommended that you need to go back to stock first
I was stuck on Cog all i did was update to the most current version
Till last week where i got the guts to use Odin to flash back to stock with some fear i might brick my phone
Now im looking to do it all over but do it right and not mess it up only with different rom
DudeWatsThat said:
Thank you this is very informative and what i meant by "Here are my doubts: Captivate 2.2 no root" is that my captivate is on stock 2.2 without root just to be clear.
I got one more question:
Whats is the EFS folder?
Im going to tell you my former situation so you can tell me what I did wrong:
I rooted my phone with super one click at the time
I used rom manager it was also supposed to save a backup of my stock rom
Somewhere in the CWM I was supposed to save the stock rom just in case something went wrong(i thought i did it correctly)
I flashed Cognition everything was great
I wanted to eliminate Cog when i went to CWM to find my back up of stock it didnt work it stayed in Cog
I have read that flashing other roms while having a custom rom isnt recommended that you need to go back to stock first
I was stuck on Cog all i did was update to the most current version
Till last week where i got the guts to use Odin to flash back to stock with some fear i might brick my phone
Now im looking to do it all over but do it right and not mess it up only with different rom
Click to expand...
Click to collapse
It actually doesn't sound like you did anything wrong - you may just be looking for things in the wrong places. The CWM backup, if I am correct, doesn't create a quick-swappable backup of your stock configuration. My understanding of how the nandroid backup works is that it creates a snapshot of the phone with a particular rom in place, so that if something bad happens, you can flash back to a clean version of that rom, apply the nandroid backup, and you'll be right back in business with your custom rom (Again, that's my understanding - someone more knowledgeable may chime in and give a better/more correct explanation).
If you made a backup using CWM, you should have a folder on your internal SD called "clockworkmod/backup", with a folder that has the date of the backup on it. I would copy that to somewhere safe (like your computer). Once you've done that, and assuming your phone is functioning normally as a phone, I would use a root-level file explorer (root explorer, adb pull command, etc.) to get a copy the folder "/efs" on your computer as well. (Take a look at the link in my signature about XDA terms and acronyms for what the EFS folder is).
Once you've done this, if you haven't already done so, back up your applications with Titanium backup. Then use the Odin one-click to get back to stock 2.1 Eclair. You won't have root access at that point, but that is not a problem. Once you're there, just follow the directions for the rom you want to flash - most will install without requiring the root permissions. The AIO captivate toolbox in the development thread is a good tool if you want something to walk you through the installation process (although it should really only be used on Froyo roms at this point).
PLEASE NOTE - THIS IS EXTREMELY IMPORTANT: If you are going to flash a Gingerbread-based rom (Mosaic, Apex, etc), please read up and follow all directions extremely carefully. Flashing Gingerbread involves flashing the bootloaders on your phone, and if something happens during that portion of the flashing process, you will have a true hard brick - not a clay (recoverable error state), but a phone that you can't use.
jmtheiss said:
It actually doesn't sound like you did anything wrong - you may just be looking for things in the wrong places. The CWM backup, if I am correct, doesn't create a quick-swappable backup of your stock configuration. My understanding of how the nandroid backup works is that it creates a snapshot of the phone with a particular rom in place, so that if something bad happens, you can flash back to a clean version of that rom, apply the nandroid backup, and you'll be right back in business with your custom rom (Again, that's my understanding - someone more knowledgeable may chime in and give a better/more correct explanation).
If you made a backup using CWM, you should have a folder on your internal SD called "clockworkmod/backup", with a folder that has the date of the backup on it. I would copy that to somewhere safe (like your computer). Once you've done that, and assuming your phone is functioning normally as a phone, I would use a root-level file explorer (root explorer, adb pull command, etc.) to get a copy the folder "/efs" on your computer as well. (Take a look at the link in my signature about XDA terms and acronyms for what the EFS folder is).
Once you've done this, if you haven't already done so, back up your applications with Titanium backup. Then use the Odin one-click to get back to stock 2.1 Eclair. You won't have root access at that point, but that is not a problem. Once you're there, just follow the directions for the rom you want to flash - most will install without requiring the root permissions. The AIO captivate toolbox in the development thread is a good tool if you want something to walk you through the installation process (although it should really only be used on Froyo roms at this point).
PLEASE NOTE - THIS IS EXTREMELY IMPORTANT: If you are going to flash a Gingerbread-based rom (Mosaic, Apex, etc), please read up and follow all directions extremely carefully. Flashing Gingerbread involves flashing the bootloaders on your phone, and if something happens during that portion of the flashing process, you will have a true hard brick - not a clay (recoverable error state), but a phone that you can't use.
Click to expand...
Click to collapse
Thanks again
I don't plan on flashing 2.3 roms until the official 2.3 release come out
Theres a Odin that flashes stock 2.2 instead of 2.1 can I use that one instead?
Theres a Odin that flashes stock 2.2 instead of 2.1
Click to expand...
Click to collapse
I wasn't aware that existed - could you please provide a link?
Just to point you in the right direction, at the end of the flashing you're currently doing, what rom do you want to have on your phone?
jmtheiss said:
I wasn't aware that existed - could you please provide a link?
Just to point you in the right direction, at the end of the flashing you're currently doing, what rom do you want to have on your phone?
Click to expand...
Click to collapse
Heres the link http://www.mobiletechvideos.com/blog/?page_id=186
The rom i want to use is either Andromeda3,Phoenix Unleashed or just go back to Cognition 4.5.3 or Cog 5 when its not in Beta.
DudeWatsThat said:
Heres the link http://www.mobiletechvideos.com/blog/?page_id=186
The rom i want to use is either Andromeda3,Phoenix Unleashed or just go back to Cognition 4.5.3 or Cog 5 when its not in Beta.
Click to expand...
Click to collapse
Thanks for the link - good to know about that file.
In my opinion, you would have the best luck going back to stock Eclair (2.1). The reason I say this is because it gives you the cleanest path to getting to the custom Rom you want. 2.1 doesn't have the signed 3e recovery problems that can exist with a 2.2 stock rom, so you'll save yourself a lot of hassle there. Plus, the 2.1 stock rom to custom rom path has been followed hundreds of times on this forum, so it's had the chance to get pretty much all the kinks worked out by this point.
Again, just my opinion.
jmtheiss said:
Thanks for the link - good to know about that file.
In my opinion, you would have the best luck going back to stock Eclair (2.1). The reason I say this is because it gives you the cleanest path to getting to the custom Rom you want. 2.1 doesn't have the signed 3e recovery problems that can exist with a 2.2 stock rom, so you'll save yourself a lot of hassle there. Plus, the 2.1 stock rom to custom rom path has been followed hundreds of times on this forum, so it's had the chance to get pretty much all the kinks worked out by this point.
Again, just my opinion.
Click to expand...
Click to collapse
I would gladly take your advice if it makes everything safer and easier but I upgraded my phone using Kies mini to 2.2 so will using odin to flash back to stock 2.1 cause any problems since its a downgrade from 2.2 to 2.1?
DudeWatsThat said:
I would gladly take your advice if it makes everything safer and easier but I upgraded my phone using Kies mini to 2.2 so will using odin to flash back to stock 2.1 cause any problems since its a downgrade from 2.2 to 2.1?
Click to expand...
Click to collapse
You shouldn't have any problems with the 2.2-2.1 transition if you use the one click Odin back to stock. The dangerous move is going from 2.3 to any other version, as that involves flashing the bootloaders.
For maximum safety, just include these items on your checklist prior to starting:
- Nandroid backup from CWM
- EFS backup (copying that folder to a safe location)
- Titanium backup of your apps (copy titaniumbackup folder to safe place)
- Back up pictures/music/other items you want to save
Once you've done that, use the one-click Odin to get to a clean stock. From there, you should be good to go with flashing a custom rom. Just make sure you read and follow all directions in the custom roms' post. (If there's nothing there, follow this guide.)
jmtheiss said:
You shouldn't have any problems with the 2.2-2.1 transition if you use the one click Odin back to stock. The dangerous move is going from 2.3 to any other version, as that involves flashing the bootloaders.
For maximum safety, just include these items on your checklist prior to starting:
- Nandroid backup from CWM
- EFS backup (copying that folder to a safe location)
- Titanium backup of your apps (copy titaniumbackup folder to safe place)
- Back up pictures/music/other items you want to save
Once you've done that, use the one-click Odin to get to a clean stock. From there, you should be good to go with flashing a custom rom. Just make sure you read and follow all directions in the custom roms' post. (If there's nothing there, follow this guide.)
Click to expand...
Click to collapse
Eh i got it into download mode and i pressed start on odin but i think its stuck did i have to root first and then use odin im kinda scared right now
Edit:its showing a phone a warning sign and a Pc like connect phone to pc
I know it's nerve racking, but as long as you weren't on a Gingerbread rom, you'll be ok. Rooting isn't required - Odin is automatically "rooted".
A quick questions while you're waiting - When you plugged it in, did Odin recognize a phone was attached (did a yellow text box show up saying COM:4 or something similar)? It should look similar to the attached file.
jmtheiss said:
I know it's nerve racking, but as long as you weren't on a Gingerbread rom, you'll be ok. Rooting isn't required - Odin is automatically "rooted".
A quick questions while you're waiting - When you plugged it in, did Odin recognize a phone was attached (did a yellow text box show up saying COM:4 or something similar)?
Click to expand...
Click to collapse
Eh yes its i managed to trouble shoot it and its reboting everything is ok and yes it did show a yellow text box as of right now i just need to pop in the sym and reboot i have succesfully flashed 2.1 i just need to root and get CWM thru Room manager correct me if im wrong.
I'm not that familiar with Rom manager, but the general idea of getting root (maybe through the super one click root application, or from the CWM recovery menu) and installing CWM recovery (however you need to accomplish that) is the right first steps to getting to a custom rom.
Good luck with the flashing process.
jmtheiss said:
I'm not that familiar with Rom manager, but the general idea of getting root (maybe through the super one click root application, or from the CWM recovery menu) and installing CWM recovery (however you need to accomplish that) is the right first steps to getting to a custom rom.
Good luck with the flashing process.
Click to expand...
Click to collapse
I just rooted now all I need is CWM and thank you for all your help!
Glad it worked out. Don't be afraid to ask more questions in the future, as a reply to a question you've asked could help someone else with the same question out.
Everything you asked about could have been answered by doing some searches and reading up on these items. Invest the time instead of just posting.
Miami_Son said:
Everything you asked about could have been answered by doing some searches and reading up on these items. Invest the time instead of just posting.
Click to expand...
Click to collapse
I did ALOT of searching before thinking of posting this,the reason I did it was because most of the post are from 2010 and I had doubts on if I should use those methods or if there where new ones.This is the Q&A sub-forum right?I did just that ask questions.
I am running the most current version of Liquid ICS on my Droid Bionic and it is rooted and I use safestrap. However recently in the past couple of days when I have tried to flash it to a different ROM (i.e. AOKP, CM9, MIUI, etc) I get the motorola screen on reboot and then my screen goes and stays blank and does not load. I then have to pop my battery out and wipe wipe wipe and then restore.......Any advice??? (yes I also installed my gapps)
Motorola Droid Bionic / [AOSP]LiquidSmooth-ICS-v1.5mr1 ROM
SexyGermanChik said:
I am running the most current version of Liquid ICS on my Droid Bionic and it is rooted and I use safestrap. However recently in the past couple of days when I have tried to flash it to a different ROM (i.e. AOKP, CM9, MIUI, etc) I get the motorola screen on reboot and then my screen goes and stays blank and does not load. I then have to pop my battery out and wipe wipe wipe and then restore.......Any advice??? (yes I also installed my gapps)
Motorola Droid Bionic / [AOSP]LiquidSmooth-ICS-v1.5mr1 ROM
Click to expand...
Click to collapse
Hey man I have been having the same issue(s) as well. I have tried both CWM, and Safestrap following the typical clear cache/factory reset/wip dalvik etc(currently I am on .233). I suspect these roms (AOKP, and CM9, MIUI, etc) simply do not work on any of the other leaked based ROMS. From testing(I have tried everyone lol), they install fine on .902 based firmware some even work on .905, but installing over any of the ICS leaks seems to create boot loops(test in CWM, and Safestrap the results are the same). I would recommend flashing back to .902/905 and trying again. I am smelling a lot of bullshting come from people who say they are able to flash over any of the ICS Leaks. btw are you using CWM(4.x.x.x/5.x.x.x) or Safestrap?
Atheistnofaith said:
Hey man I have been having the same issue(s) as well. I have tried both CWM, and Safestrap following the typical clear cache/factory reset/wip dalvik etc(currently I am on .233). I suspect these roms (AOKP, and CM9, MIUI, etc) simply do not work on any of the other leaked based ROMS. From testing(I have tried everyone lol), they install fine on .902 based firmware some even work on .905, but installing over any of the ICS leaks seems to create boot loops(test in CWM, and Safestrap the results are the same). I would recommend flashing back to .902/905 and trying again. I am smelling a lot of bullshting come from people who say they are able to flash over any of the ICS Leaks. btw are you using CWM(4.x.x.x/5.x.x.x) or Safestrap?
Click to expand...
Click to collapse
I am using safestrap and never had a problem until last week flashing from my ICS leak to the other ROMS. Should I go back to stock and then install the leak again?
SexyGermanChik said:
I am using safestrap and never had a problem until last week flashing from my ICS leak to the other ROMS. Should I go back to stock and then install the leak again?
Click to expand...
Click to collapse
Yes, I would flash back the dev's are not putting correct information out most of these ROM'S (AOKP/CM9Gummy, etc) are not designed to be installed over any of the OTA Leaks(people keep insisting on it), and will cause boot loops like crazy. I have tested on two bionic's and the results where the same flashing over any ICS Leak to AOKP/CM9 etc will cause issues regardless of what 2nd stage boot loader you are using(Safestrap, or CWM via bootstrap). I would recommend flashing back to 902, or 905 using the SBF/FXZ method and installing eclipse 3.0(for .905 baseband), or sticking with the OTA Leaks untill the issues with flashing ROMS in both Safestrap, and CWM have been resolved or the dev's actually give solid advice(i.e. what firmware is actually needed, or what flashing requirements should be meet. Thanks again!!!
Atheistnofaith said:
Yes, I would flash back the dev's are not putting correct information out most of these ROM'S (AOKP/CM9Gummy, etc) are not designed to be installed over any of the OTA Leaks(people keep insisting on it), and will cause boot loops like crazy. I have tested on two bionic's and the results where the same flashing over any ICS Leak to AOKP/CM9 etc will cause issues regardless of what 2nd stage boot loader you are using(Safestrap, or CWM via bootstrap). I would recommend flashing back to 902, or 905 using the SBF/FXZ method and installing eclipse 3.0(for .905 baseband), or sticking with the OTA Leaks untill the issues with flashing ROMS in both Safestrap, and CWM have been resolved or the dev's actually give solid advice(i.e. what firmware is actually needed, or what flashing requirements should be meet. Thanks again!!!
Click to expand...
Click to collapse
So I wonder why it has worked for this long and just stopped flashing?
Hello Guys!
I just bought a droid 3 unlocked, are in Italy.
I have noticed that I have a software version .906 (The last I think), following some guides I installed Rom manager and flashed the recovery from them.
Now I wanted to ask, I can put that rom without incurring risks and fully functional?
And what is the procedure?
Thank you so much guys!
You'll want to install Safestrap 3 from Hashcode which is the latest recovery for the Droid 3 and allows you to install ROMs that use a custom kernel with kexec. Look in the development section for the thread.
I can put that rom without incurring risks and fully functional?
Click to expand...
Click to collapse
moto phones are pretty safe to root and rom, just be prepared to flash a .sbf to recover
but safestrap, makes flashing roms and restoring stock, too easy
cm10 has several things that just don't work, cm9 is better
steel droid ics 5.4 is good or steel droid GB 4.5
with safestrap 3 you flash 4 roms plus stock, and go back and forth just with a reboot
you need to remove rom managers cwm first
edit:
several how to videos here
How to Video's Root, safe strap, kexec, and much more
really thanks.
1) cm9 has not working cam, true?
2)How can i remove the rom manager and the recovery that rom manager have installed?
3)I just have to wipe everything and flash the zip, for every rom?
4) What about minimoto?
5)There is CM7?
Thanks..!
6) My droid is unlocked from when i have It. If i chance rom It Will lock again?
davibs said:
really thanks.
1) cm9 has not working cam, true?
2)How can i remove the rom manager and the recovery that rom manager have installed?
3)I just have to wipe everything and flash the zip, for every rom?
4) What about minimoto?
5)There is CM7?
Thanks..!
6) My droid is unlocked from when i have It. If i chance rom It Will lock again?
Click to expand...
Click to collapse
I'll try my best to help you out here but..
1.) The stock based builds of cm9 had a working camera for pictures only, but those builds are gone and no longer compatible with safestrap 3, otherwise development is focused on kexec.
2.) You should be able to uninstall it from rom manager itself I believe
3.) Sometimes, only for something really major like new codec or something, sometimes but its not always necessary and your stock system will be fully protected.
4.) I don't know what that is, lol i'm new here.
5. There is CM7 but it was never worked on nor finished so don't bother with it really.
6.) I really don't know but I highly doubt it.
Otherwise i'm glad to help you out.
davibs said:
really thanks.
1) cm9 has not working cam, true?
2)How can i remove the rom manager and the recovery that rom manager have installed?
3)I just have to wipe everything and flash the zip, for every rom?
4) What about minimoto?
5)There is CM7?
Thanks..!
6) My droid is unlocked from when i have It. If i chance rom It Will lock again?
Click to expand...
Click to collapse
1 true
2 should be option to remove recovery in rom manager
If you have trouble flash sbf and wipe data
3 yes
4 haven't used it
5 yes haven't used it
6. Will stay sim unlocked
Sent from my XT862 using xda premium
ive got safestrap installed. created rom slot. tried to load a rom and nothin. it boots to a wiped stock rom. nothin happens. nothin changes
harley1rocker said:
ive got safestrap installed. created rom slot. tried to load a rom and nothin. it boots to a wiped stock rom. nothin happens. nothin changes
Click to expand...
Click to collapse
You need to provide a lot more information if you want some help. What firmware are you on? What version of SafeStrap did you install? What ROM did you try to install? What steroids did you take? Which modules did you flash? Does your stock ROM boot?
Always provide as much information as possible, it will increase your chances of getting help.
Devo7v said:
You need to provide a lot more information if you want some help. What firmware are you on? What version of SafeStrap did you install? What ROM did you try to install? What steroids did you take? Which modules did you flash? Does your stock ROM boot?
Always provide as much information as possible, it will increase your chances of getting help.
Click to expand...
Click to collapse
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
---------- Post added at 12:33 AM ---------- Previous post was at 12:20 AM ----------
Caboose27 said:
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
Click to expand...
Click to collapse
And now I tried to wipe it again, and that ROM slot is gone, and I suddenly don't have room to make a new one.
*edit* apparently a wipe this time around reset my entire phone. No idea why. Is there a manual on this program somewhere? I keep getting told to search and I'll find it, but all I've found is about five lines worth of instructions.
Caboose27 said:
Let me try, because I think I have the same issue. I'm running 4.4.2, and I used safestrap 3.73 to create a rom slot and install Hyperdrive. I wiped everything it said to before I installed it, and installed the latest masterpatch after and rebooted. When it rebooted, it appears to have gone into my stock ROM. Everything is the same, except my network doesn't work because it says my SIM card isn't inserted. Any ideas?
---------- Post added at 12:33 AM ---------- Previous post was at 12:20 AM ----------
And now I tried to wipe it again, and that ROM slot is gone, and I suddenly don't have room to make a new one.
*edit* apparently a wipe this time around reset my entire phone. No idea why. Is there a manual on this program somewhere? I keep getting told to search and I'll find it, but all I've found is about five lines worth of instructions.
Click to expand...
Click to collapse
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
EDIT: just so you're aware, I'm still on 4.2.2, so I haven't actually had any experience with SafeStrap on 4.4.2. I'm just relaying information I've read. So definitely do some reading before you do anything in case I'm wrong. If you have more questions I'll do my best to answer them, but make sure you fact check me because i wouldn't want to brick your phone.
Devo7v said:
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
Click to expand...
Click to collapse
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?
Caboose27 said:
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?
Click to expand...
Click to collapse
same version of bootstrap. same prob here. and let me get this str8...over write stock rom slot? isnt that suppose to be like the "safe zone"
Caboose27 said:
Yeah, if that information is out there, it's pretty deep. Like, Mariana's Trench deep. At least now it'll be up front. So basically, SafeStrap is a custom recovery in itself, bypassing the need for an unlocked bootloader?
Click to expand...
Click to collapse
SafeStrap does not bypass the bootloader, it loads after the kernel loads so there is no way to install a custom kernel. This means that you can only use ROMs that are compatible with your stock kernel, no AOSP ROMs and no CM. You can only use TouchWiz-based ROMs.
harley1rocker said:
same version of bootstrap. same prob here. and let me get this str8...over write stock rom slot? isnt that suppose to be like the "safe zone"
Click to expand...
Click to collapse
That is the way it was intended to work, but Samsung changed some things in 4.4.2 and the developer didn't have time to reimplement ROM slots before he left.
Devo7v said:
SafeStrap does not bypass the bootloader, it loads after the kernel loads so there is no way to install a custom kernel. This means that you can only use ROMs that are compatible with your stock kernel, no AOSP ROMs and no CM. You can only use TouchWiz-based ROMs.
That is the way it was intended to work, but Samsung changed some things in 4.4.2 and the developer didn't have time to reimplement ROM slots before he left.
Click to expand...
Click to collapse
I got it working. I have the 4.4.2 kernel and the Graviton ROM flashed after using Safestrap to make a backup. After I flashed the rom, I wiped dalvik and cache, flashed the master patch v.2, wiped again, and rebooted. Everything works except the stock camera app, which I'm currently looking for a fix.
master patch link??
Devo7v said:
You cannot use ROM slots with SafeStrap 3.73. You have to install ROMs to your stock ROM slot overwriting your stock ROM. So make a backup before you flash anything. The developer of SafeStrap took a new job and had to abandon development before he could fully implement ROM slots on 4.4.2. I know it's difficult to find but the information is there. Thank you for trying to find it before posting.
EDIT: just so you're aware, I'm still on 4.2.2, so I haven't actually had any experience with SafeStrap on 4.4.2. I'm just relaying information I've read. So definitely do some reading before you do anything in case I'm wrong. If you have more questions I'll do my best to answer them, but make sure you fact check me because i wouldn't want to brick your phone.
Click to expand...
Click to collapse
DONT TRY OVERWRITING YOUR STOCK ROM SLOT WITH HYPERDRIVE ROM. YOU WILL LOSE SAFESTRAP AND IT BREAKS CAMERA WIFI,basiclly your phone wont work. Ive done it ant now have a s4 active paperweight. Ive tried odin and all the tar,pit and rar files you can find. NOTHIN WORKS. Before any1 says take it to bestbuy....i did. Kies and all the merry samsung reps culdnt put it back together. So before flashing anything over your stock rom slot make dam sure your a rocket scientist or at the very least a software engineer for samsung...
harley1rocker said:
DONT TRY OVERWRITING YOUR STOCK ROM SLOT WITH HYPERDRIVE ROM. YOU WILL LOSE SAFESTRAP AND IT BREAKS CAMERA WIFI,basiclly your phone wont work. Ive done it ant now have a s4 active paperweight. Ive tried odin and all the tar,pit and rar files you can find. NOTHIN WORKS. Before any1 says take it to bestbuy....i did. Kies and all the merry samsung reps culdnt put it back together. So before flashing anything over your stock rom slot make dam sure your a rocket scientist or at the very least a software engineer for samsung...
Click to expand...
Click to collapse
You need to flash the modules after flashing the ROM to get everything working again. Make sure you do it before you allow Hyperdrive to boot for the first time.
Also, in order to use Odin you cannot have Kies installed.
Devo7v said:
You need to flash the modules after flashing the ROM to get everything working again. Make sure you do it before you allow Hyperdrive to boot for the first time.
Also, in order to use Odin you cannot have Kies installed.
Click to expand...
Click to collapse
Way past that dude. The phone only allows me to enter into DL mode as of now. I know i was on ne3 htperdrive when this happened. Can you pls post a link for the correct tar file to use in odin? Ive tried most of those files but none worked. Can u post the correct ones for odin? May the software gods be with me....ima gonna need em....thanx dude
harley1rocker said:
Way past that dude. The phone only allows me to enter into DL mode as of now. I know i was on ne3 htperdrive when this happened. Can you pls post a link for the correct tar file to use in odin? Ive tried most of those files but none worked. Can u post the correct ones for odin? May the software gods be with me....ima gonna need em....thanx dude
Click to expand...
Click to collapse
Follow the instructions and you'll be fine. Remember, since you're on NE3 you can only flash NC9 or NE3.
http://forum.xda-developers.com/showthread.php?t=2835481