Related
I uninstalled the old version of safestrap, then installed the new version. I can do everything just fine (install, wipe, etc) but when I try to boot from the ROM slots, the phone just sits at a black screen.. I tried flashing Eclipse 3.0 and nothing happens.. help???
Sent from my DROID3 using xda app-developers app
Well eclipse 3.0 hasn't worked for me. The latest cm10,aokp,and aosp boot for me as well as mavrom 4.5 and axiomcs 1.0. Have u tried any other roms aside from eclipse?
Sent from my XT862 using xda app-developers app
Don't think eclipse works with new Safestrap. I have tested CM10, AOKP, AOSP, and Steel Droid. Those 4 all are "working".
Steel Droid is the most stable one i have tried so far, CM10, AOKP and AOSP all lag for me.
Hey guys,
New to Droid 3/ Milestone 3 World here.
I just bought one, actually with the 5.2.390.XT860.Brasil.en.BR version.
I'm not exacly new to flashing roms, and recoveries, but in this case I'm a little confused. Is it possible to use SafeStrap on this one? Or better go for an older version of it?
Thanks in advance.
@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!
bArAbAts said:
@Munckster, as long as it is rooted you can install safestrap 3.04 and try if custom roms work for you?? but make sure you have the correct SS3 version!!
Click to expand...
Click to collapse
I was thinking about trying... Maybe during the weekend..
Thanks for the advice, man!
I took my phone back to stock (from an oldish CM9 that had been working reasonably well for me for some time) so I could install SS3. Made the mistake of letting the phone OTA update itself and then had to find a new root hack before I could get SS3 installed.
Unfortunately the OTA update has messed with the radio, as reinstalling the CM9 I've used for months gets a system where the phone app just crashes.
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.
Well,
I installed the 3.0.5 version. Works like a charm! The easiest to use recovery that I ever use.
But the question is: Is it safe to downgrade it?
Sorry about the dumb question.
SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.
matthewgeier said:
The kexec cm9 on hash code's download site results in a black screen for me. I have to pull the battery to get the phone back. Funnly enough the old CM9 does boot - and every thing works except the phone.
The latest CM10 does every thing I want (I can live with out the camera) BUT I can't receive calls, the phone app crashes. (But I can MAKE calls!).
This is on GSM BTW, not CDMA where I live.
So i'm busted back down to the 'stock' OS so I can use my phone as a phone
And as a new XDA user I can't post my bug report in the developer thread.
Click to expand...
Click to collapse
Is the issue you're having that when you're speaking to people on the phone you can't hear anything and they can't hear you? Cause on CM9 there should be no issues with using it as a phone as long as you don't enable bluetooth ever or use buttons on a headset connected to your phone. I haven't tried CM10 yet so I wouldn't know too much about that. Just for some extra info to save your time do not flash Liberty or Eclipse, they don't seem to work. The newest Maverick works fine.
matthewgeier said:
SS3 can be un-installed pretty easily. Boot your 'stock' OS, then use the SS3 app to remove the 'hijack' and then reboot again. No SS3. Just remember to do it from the 'stock' OS and not one of the others.
Don't do what I did with SS2 - from a non stock OS, remove SS and reboot. Ended up with a phone that never finished booting before it rebooted. Fortunately the emergency recovery mode built into the phone worked to recover it.
Click to expand...
Click to collapse
I was going to try from the stock.
I am much more familiar with clockworkmod.
Anyway, thank you for the advice
Sent from my XT860 using xda app-developers app
Every time I reboot, I get the "android is upgrading" screen.
I am rooted and BL unlocked. This started after I tried --and failed, see below -- to flash Batakang Rises.
Is my Dalvik-cache being cleared somehow? Doesn't that do this?
I have tried a factory reset. I can't reflash my rom, since zips I flash don't seem to stick. (I posted about that earlier and got no responses.)
Not that big of a deal, but just quite annoying and time-consuming.
Same problem
I'm getting the same problem, although it doesn't affect anything, it just bothers me a lot.
On the development forum it is already on the "known bugs" list, so it must be a common problem.
I've tried all the common fixes but its still there. I LOVE the Batakang Rises rom, but this really annoying, and I may try out the PACman rom.
Its just built into the rom since the rom was meant for locked bootloaders.
Sent from my PACMAN MATRIX HD MAXX
Meant for locked bootloaders
So if we had a rooted phone, but locked boot loader, we wouldn't get this message during every start up? Sorry if this is a noob question
Kohwali said:
So if we had a rooted phone, but locked boot loader, we wouldn't get this message during every start up? Sorry if this is a noob question
Click to expand...
Click to collapse
No idea because if you had a locked boot loader and tried to flash any of the roms for this phone (4.2.2 ones anyways) you'd probably brick your phone.
Anyways I'd definitely recommended PAC. I've tried all the major roms here and I like it the best. There is a battery drain on all 4.2.2 roms bit it seems a little higher on pac (might be fixed with the newesy build). There is a fix for it (more of a battery boost actually) in the dev section.
Sent from my PACman Atrix HD
About PACman Atrix HD, my computer doesn't seem to recognize it...any ideas?
Kohwali said:
About PACman Atrix HD, my computer doesn't seem to recognize it...any ideas?
Click to expand...
Click to collapse
Doesn't recognize what? The PAC file or the device after PAC has been flashed?
Sent from my PACman Atrix HD
Just a thought but I have learned that when changing ROMs its best to manually WIPE system, data, cache. Don't know why but it seems to help. Especially when flashing back to stock.
Sent from my MB886 using xda app-developers app
Blackest Pain said:
Doesn't recognize what? The PAC file or the device after PAC has been flashed?
Sent from my PACman Atrix HD
Click to expand...
Click to collapse
Nevermind, I was just being a noob during fastboot - instead of entering "fastboot devices" I was entering "adb devices". I have PACman rom installed and running now thanks to the people on XDA
Kohwali said:
Nevermind, I was just being a noob during fastboot - instead of entering "fastboot devices" I was entering "adb devices". I have PACman rom installed and running now thanks to the people on XDA
Click to expand...
Click to collapse
lol glade to hear it.
So I have tried installing this rom, but I've failed many many times. I'm not sure what the problem is, but if you've already successfully installed PACman rom, please tell me your exact steps (I'm a noob)! In the mean time, here are my steps:
1. Startup Safestrap Recovery
2. Create ROM Slot: rom-slot1 (system partition size: 1024 MB, data partition size: 1 GB, cache partition size)
3. factory reset, wipe system, format data, wipe cache, wipe dalvik cache
4. Flash PACman rom (mb886_PAC_JB_4.2.2-v22.4.0_20130607-003508.zip) via SD card
5. Flash gapps (gapps-jb-20130301-signed.zip) via SD card
6. Flash Paranoid fix (I've done this step and skipped this step)
7. Wipe cache and wipe dalvik cache
^ So this doesn't work :crying:and I really want to try out this rom
... Wow no one reads ever. Do... Not... Use... Safestrap.. With.. Newer.. Roms.. It will not work. This has been posted countless times. Even says so in the Safestrap title.
Sent from my PACMAN MATRIX HD MAXX
Haha okay
Hey, sorry
What should I be using then?
EDIT: I looked around and found that I should be using ADB and stuff - the only knowledge I had was from watching the tutorial from the guy installing Infekted
Adb isn't necessary. Your bootloader is unlocked correct? Use cwm.
Sent from my PACMAN MATRIX HD MAXX
Oh, okay. I originally thought the Atrix HD wasn't supported, but it seems as though I can do something about it
Sent from my MB886 using xda premium
Supported by what?
Sent from my PACMAN MATRIX HD MAXX
I thought Atrix HD wasn't supported by CWM - it wasn't in the list of devices. I did find the tutorial from skeevydude on how to do stuff, but when I fastboot, ADB doesn't seem to recognize my phone - so I'm not sure how to install CWM anymore.
Not officially but we have our own version you have to fastboot.
Read this.
http://forum.xda-developers.com/showthread.php?t=2350721
Sent from my PACMAN MATRIX HD MAXX
I've found everything now through threads and stuff, thanks for helping! What I did was I just restored everything (flashed stock rom with RSD lite), rebooted, installed CWM, then installed the rom.
Is there a moderator up here that can remove the safestrap thread in the Atrix HD forums? This issue has to happen like 3 time a week lol.
Sent from my PACman Atrix HD
Well it's because the first custom ROM I installed (Batakang) required the use of Safestrap and I just assumed that all ROM installations were okay with Safestrap.
Kohwali said:
Well it's because the first custom ROM I installed (Batakang) required the use of Safestrap and I just assumed that all ROM installations were okay with Safestrap.
Click to expand...
Click to collapse
Lol don't worry I made that mistake when I first flashed a rom on this phone. I just think the safestrap thread should be removed because (I believe) you can still flash roms that say to use safestrap with cwm. That would make sure more people don't mess up their phones
Sent from my PACman Atrix HD
Blackest Pain said:
Lol don't worry I made that mistake when I first flashed a rom on this phone. I just think the safestrap thread should be removed because (I believe) you can still flash roms that say to use safestrap with cwm. That would make sure more people don't mess up their phones
Sent from my PACman Atrix HD
Click to expand...
Click to collapse
Skeevy mentioned last time I requested the removal of the SS3 thread, he said we still need it for people that need/want to keep their bootloaders locked for warranty reasons or whatever.
penser said:
Skeevy mentioned last time I requested the removal of the SS3 thread, he said we still need it for people that need/want to keep their bootloaders locked for warranty reasons or whatever.
Click to expand...
Click to collapse
I read something on relocking the bootloader on this site (third guy down)
http://androidforums.com/incredible-all-things-root/486704-how-relock-bootloader.html
Sent from my PACman Atrix HD
penser said:
Skeevy mentioned last time I requested the removal of the SS3 thread, he said we still need it for people that need/want to keep their bootloaders locked for warranty reasons or whatever.
Click to expand...
Click to collapse
We do. Not everyone needs or wants to be unlocked for whatever reason. Is it annoying answering these questions? Yes. This, IMHO, is a problem from people used to crack flashing and not bothering to read OPs, guides, faqs, or even use the search bar.
Blackest Pain said:
I read something on relocking the bootloader on this site (third guy down)
http://androidforums.com/incredible-all-things-root/486704-how-relock-bootloader.html
Sent from my PACman Atrix HD
Click to expand...
Click to collapse
fastboot oem lock and unlock don't work for us. The was the unlock was done we're in a (what-should-be) permanent fastboot oem unlock state.
Can I edit the title to read "[Solved]" in front?
Yeah you can. Even better instead of making new topics with each issue you have just keep them in one and change the tile.
Sent from my PACMAN MATRIX HD MAXX
OK so I have this great ATT note 3. I have it rooted (mj5). I haven't done much with it because as far as I know I can't get a custom recovery yet Correct??
I am having issues with a few things and I'm a little concerned with the phone. For 1 I have a hard time starting up my phone some times. It seems to keep restarting and I have to keep taking the battery out and it will work after a few times. 2nd the volume sometimes gets messed up with things I do.
I've been rooting for maybe close to 1 year now and by no means a expert here but I've never failed doing it.
So here is my question, I would like to know if there is anything I can do now to get a custom recovery now that some time has gone by. I see a lot of things going on but it's all things I've never seen or read about before. I'm just looking to get pointed in the right direction from the point I'm at right blessed which is rooted with Mj5.
Or do I unroot and if so how?
also any of these options am I going to lose everything on my phone? Any help is greatly appreciated.
Thanks!!
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Look at the safestrap thread. It is our version of recovery for locked bootloaders
Sent from my SM-N900V using XDA Premium 4 mobile app
itmaster85 said:
Look at the safestrap thread. It is our version of recovery for locked bootloaders
Sent from my SM-N900V using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Would you be able to send me a link to the one your using? I just want to make sure I'm looking on the right thread.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
enzosly said:
Would you be able to send me a link to the one your using? I just want to make sure I'm looking on the right thread.
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
At the top of this page if you just click where it says AT&T Samsung Galaxy Note 3 you will see all our sections. Click on the Android Development link then search around there for safestrap by hashcode.
enzosly said:
OK so I have this great ATT note 3. I have it rooted (mj5). I haven't done much with it because as far as I know I can't get a custom recovery yet Correct??
I am having issues with a few things and I'm a little concerned with the phone. For 1 I have a hard time starting up my phone some times. It seems to keep restarting and I have to keep taking the battery out and it will work after a few times. 2nd the volume sometimes gets messed up with things I do.
I've been rooting for maybe close to 1 year now and by no means a expert here but I've never failed doing it.
So here is my question, I would like to know if there is anything I can do now to get a custom recovery now that some time has gone by. I see a lot of things going on but it's all things I've never seen or read about before. I'm just looking to get pointed in the right direction from the point I'm at right blessed which is rooted with Mj5.
Or do I unroot and if so how?
also any of these options am I going to lose everything on my phone? Any help is greatly appreciated.
Thanks!!
Sent from my SAMSUNG-SM-N900A using XDA Premium HD app
Click to expand...
Click to collapse
I had rooted myself on SM-N900A on MJ5 using Kingo and also used kingo to unroot too. No issues / No Knox tripping.
Rooting
So I have the ATT N900A and have tried rooting it or at least looked into it so far but when the forums say only certain version available I never find one that actually says N900A. I have seen others, but to be honest I am freshly new to all of this and I am learning it all slowly but surely. Can I get some help any one?
enzosly said:
OK so I have this great ATT note 3. I have it rooted (mj5). I haven't done much with it because as far as I know I can't get a custom recovery yet Correct??
I am having issues with a few things and I'm a little concerned with the phone. For 1 I have a hard time starting up my phone some times. It seems to keep restarting and I have to keep taking the battery out and it will work after a few times. 2nd the volume sometimes gets messed up with things I do.
I've been rooting for maybe close to 1 year now and by no means a expert here but I've never failed doing it.
So here is my question, I would like to know if there is anything I can do now to get a custom recovery now that some time has gone by. I see a lot of things going on but it's all things I've never seen or read about before. I'm just looking to get pointed in the right direction from the point I'm at right blessed which is rooted with Mj5.
Or do I unroot and if so how?
also any of these options am I going to lose everything on my phone? Any help is greatly appreciated.
Click to expand...
Click to collapse
Those are not normal issues to have on your phone, and I don't think they are related to the rooting; I think they are indicative of larger issues with the phone. I would unroot it so it looks stock, and assuming the problems persist, take it back to AT&T.
If unrooting fixes it, ofc, reroot and do it right this time (I don't know what method you used, or what might have gone wrong)
Do that BEFORE messing around with our poor-substitute for a custom recovery (safestrap) and custom ROM's.
DrAzzy said:
Those are not normal issues to have on your phone, and I don't think they are related to the rooting; I think they are indicative of larger issues with the phone. I would unroot it so it looks stock, and assuming the problems persist, take it back to AT&T.
If unrooting fixes it, ofc, reroot and do it right this time (I don't know what method you used, or what might have gone wrong)
Do that BEFORE messing around with our poor-substitute for a custom recovery (safestrap) and custom ROM's.
Click to expand...
Click to collapse
Well its funny because I did root my phone using the Vega root files but lol I just looked last night and I'm not rooted anymore... Maybe I took a update with out realizing it?? Ok so now that I'm not rooted what do I do?
If I just do a restart from stock what thread should I look at?
Or do I root again using the kingo .com thing? Wow I'm so lost with this phone. I have the s4 HTC one, nexus 5 and never have had these issues. Just when I start to think I'm getting g good at this
Sent from my Nexus 5 using XDA Premium HD app
enzosly said:
Well its funny because I did root my phone using the Vega root files but lol I just looked last night and I'm not rooted anymore... Maybe I took a update with out realizing it?? Ok so now that I'm not rooted what do I do?
If I just do a restart from stock what thread should I look at?
Or do I root again using the kingo .com thing? Wow I'm so lost with this phone. I have the s4 HTC one, nexus 5 and never have had these issues. Just when I start to think I'm getting g good at this
Sent from my Nexus 5 using XDA Premium HD app
Click to expand...
Click to collapse
Sigh - always, first thing after rooting, always freeze OTA updates, and wait to upgrade before people here say it works and there's a root available!
Since you're having suspicious issues, I would want to put on clean MJ5 firmware before continuing - get the system into a known state before continuing.
http://forum.xda-developers.com/showthread.php?t=2559715
This will erase everything on your phone.
I would hold off on rooting and first check if the issues you mentioned in the OP are fixed, and if they are, then you can chalk it up to a software problem (pin the blame on the OTA update), and follow the instructions in that thread to get root.
DrAzzy said:
Sigh - always, first thing after rooting, always freeze OTA updates, and wait to upgrade before people here say it works and there's a root available!
Since you're having suspicious issues, I would want to put on clean MJ5 firmware before continuing - get the system into a known state before continuing.
http://forum.xda-developers.com/showthread.php?t=2559715
This will erase everything on your phone.
I would hold off on rooting and first check if the issues you mentioned in the OP are fixed, and if they are, then you can chalk it up to a software problem (pin the blame on the OTA update), and follow the instructions in that thread to get root.
Click to expand...
Click to collapse
That's what I will do.
Sent from my Nexus 5 using XDA Premium HD app
Hey guys, this is my first post. I recently bought a rooted verizon G2(VS980)and i tried to flash a rom on it. Im a noob, so of course the worst happened. My phone will boot past the LG screen, but then stays at the "verizon" screen. If i try to put it in recovery(i have cwm) it just reboots. I really need a fast fix, im having to use the good ole slll until my jewl is working again. Thanks in advance
Davidmay6 said:
Hey guys, this is my first post. I recently bought a rooted verizon G2(VS980)and i tried to flash a rom on it. Im a noob, so of course the worst happened. My phone will boot past the LG screen, but then stays at the "verizon" screen. If i try to put it in recovery(i have cwm) it just reboots. I really need a fast fix, im having to use the good ole slll until my jewl is working again. Thanks in advance
Click to expand...
Click to collapse
You need to make sure your boot stack and radios are appropriate for the rom you want to flash. The G2 ROM scene is a bit fractured, since CM11 and a good chunk of derivative ROMs are still based on the 12B (4.2) OTA, but some devs are now working with the 24A (4.4) OTA.
If you can get into the bootloader/fastboot, you may be able to flash the appropriate boot stack and recovery from there, if you know what you're doing. The "cleaner" route would be to use TOT or KDZ to get back to stock, and start from scratch.
Sent from my Nexus 7 using Tapatalk
arkolbus said:
You need to make sure your boot stack and radios are appropriate for the rom you want to flash. The G2 ROM scene is a bit fractured, since CM11 and a good chunk of derivative ROMs are still based on the 12B (4.2) OTA, but some devs are now working with the 24A (4.4) OTA.
If you can get into the bootloader/fastboot, you may be able to flash the appropriate boot stack and recovery from there, if you know what you're doing. The "cleaner" route would be to use TOT or KDZ to get back to stock, and start from scratch.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
i can get my phone into download mode, but nothing more. Also, i had 12B and the rom(wich i downloaded from xda) said it was specifically for 12B.
Davidmay6 said:
i can get my phone into download mode, but nothing more. Also, i had 12B and the rom(wich i downloaded from xda) said it was specifically for 12B.
Click to expand...
Click to collapse
Did you make a backup of the rom, prior to installing the new Rom?
Sent from my GT-N5110 using XDA Premium 4 mobile app
evolishesh said:
Did you make a backup of the rom, prior to installing the new Rom?
Sent from my GT-N5110 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yes.
Davidmay6 said:
Yes.
Click to expand...
Click to collapse
If you can't get into recovery, and only download mode, I'd probably go ahead and return to complete stock. The nice thing about this phone is it is easily rooted and rommed again if you want to do that. Plus you'll learn a lot in the process. My two cents. :thumbup:
Edit: When you return to stock, take the Ota to 4.4.2, then root.
Sent from my VS980 4G using XDA Free mobile app