I just swapped my HD2 with someone for a N1, and I'm trying to figure out if the phone is rooted or not... I've never had an android phone.
When it boots, the little "unlocked" icon appears at the bottom of the screen, and it appears to have the "custom recovery screen" when I enter the recovery section of the bootloader I get this image:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I ask because the phone shows Kernel version 2.6.29-gad36b87 and build number ERD79, and I wanted to put froyo on the phone but was told only to update froyo from ERE27. I tried to flash ERE27 from the sd card using the recovery screen but keep getting an "unsigned files" error.
I suspect that this is a custom rom already, but have no idea how to tell if it's rooted etc.
Any help is appreciated. Thanks.
Yes it is.
Seems like you have a stock ROM, but custom recovery. You'll need stock recovery to flash the ERE27 update.zip
or you can just flash non stock update like the one of Paul's
the tut thread is here in this forum
Will the Wipe option in that recovery screen accomplish that? I don't mind trying one of the non stocks, but I'm 100% new to this and would love to avoid destroying my phone
Depends how you want to do it.
If you want everything stock, then the easist thing to do would be to grab the complete ERD79 image, flash that and you're good to go, it should OTA to ERE27 pretty quickly.
If not, then as above you can look at a non-stock update, there are tutorials for both, so just take your pick.
Thanks for the advice, I will try one of the non-stocks, I just wanted to make sure that I'd end up with root access and not get hung up halfway through the install.
just go with this one:
http://forum.xda-developers.com/showthread.php?t=686734
its the best, i did it today myself as well
Related
Does anybody knows if i updated my evo fr froyo 2.2 to 2.3 gb, how can I get it back to froyo cuz I want to rooted
Flip35 said:
Does anybody knows if i updated my evo fr froyo 2.2 to 2.3 gb, how can I get it back to froyo cuz I want to rooted
Click to expand...
Click to collapse
I just copied and pasted this out of the other thread you started... Unless your bootloader shows S-off, there is nothing you can do. If it's S-on, you just have to wait for a new exploit.
From what I posted in your other thread.........
If the phone has never been rooted before, then you are going to be S-on. Since you have the new bootloader, AND you have S-on, there is nothing you can do to root the phone at this time. You cannot downgrade to 2.2, you cannot downgrade the bootloader. The only thing you'll be able to do is wait until someone figures out how to get S off on the new bootloader, or if someone figures out a way to downgrade the bootloader. The only way you can downgrade back to 2.2, is if the bootloader is S off. Also, if the bootloader was S off, downgrading to froyo to 'reroot' is a complete waste of time. All you need to do is flash a PC36IMG of a recovery image, and then use that recovery to flash a new rom. That's it. Anything more than that is a total waste of time, and a bunch of steps that don't need to be taken.
So, unfortunately, all you can do is wait until someone figures out a way around the new bootloader.
__________________
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Stop the phone on this screen, what should I do
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
Same thing happened to me. There are 3 problems;
First is that you do not have enouch battery power to run RDS.
Second is that you have to load SBF file again with RDSLite.
Third is that you have to unlock your bootloader not to have the same situation.
But to make you feel happy, I can say that your phone is not bricked.
We shall go step by step for your problems. First of all, do you have second battery or can you supply it because it is necessary to overcome second and third problem ?
micromedia2011 said:
what should I do
Click to expand...
Click to collapse
Hi,
Please use search.
Thanks,
I'm having the same problem "failed to boot 2". Minus the battery part.
I did all the following steps a few months ago to update to the new gingerbread firmware from http://forum.xda-developers.com/showthread.php?t=1182871
Claims I would have an unlocked bootloader, root, and CWM. Which, I have root, CWM, and evidently still on a locked bootloader per a post I read on androidforums.
I'm lost as I've been reading so much that I've done confused myself on what I should actually do, and feel worse off than I was before I started reading.
Overall, my phone works fine. I just wanted to flash a different ROM. I'm just not sure where to start to fix my problem (redo all the steps in the post I linked up, or flash a whole other SBF file). Any help would be greatly appreciated. Thanks!
I am almost a complete noob but want to learn everything i can to really "own" my phone. Im on an SPH-L720 4.4.2 and had root with [CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5] (i think) though it might have been CF-Auto-Root. Everything was fine until I screwed around with some settings in SystemTuner . Now the phone is stuck in boot loop and sticks at the yellow Sprint screen. I've been able to flash back to stock ROM i think, and keep getting the PASS in Odin but keeps sticking at boot. I must have somehow got to TWRP 2.8.4.0 cause I'm going through that but really dont know what to do. Still can't use phone. Any help is seriously needed.
mebert518 said:
I am almost a complete noob but want to learn everything i can to really "own" my phone. Im on an SPH-L720 4.4.2 and had root with [CF-Auto-Root-jfltespr-jfltespr-sphl720.tar.md5] (i think) though it might have been CF-Auto-Root. Everything was fine until I screwed around with some settings in SystemTuner . Now the phone is stuck in boot loop and sticks at the yellow Sprint screen. I've been able to flash back to stock ROM i think, and keep getting the PASS in Odin but keeps sticking at boot. I must have somehow got to TWRP 2.8.4.0 cause I'm going through that but really dont know what to do. Still can't use phone. Any help is seriously needed.
Click to expand...
Click to collapse
Just flash a ROM in TWRP, also wipe data, system, cache, and dalvik cache.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
I'm new to android and recently rooted my Galaxy S7 Edge AT&T Snapdragon and now I want to unroot and return to stock but I'm having trouble.
To begin, I can't access recovery mode anymore. I get a message in the top left corner of the screen that says something about "custom rom blocked". I tried to follow instructions I found on XDA on how to unroot and return to stock. I downloaded the files and used Odin to flash it, it begins to do something and then gives me an error.
What am I doing wrong or how do I fix it? I apologize if I'm not explaining this the greatest, like I said I'm new to this and don't understand it much. All I want to do is wipe the root and return to stock. All help is greatly appreciated!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If Your phone works then try this ^
If Your phone is dead then post the log from Odin.
Thanks for the help! I tried it multiple times and it says each time "uninstallation failed". Could it be the issue I'm having with the recovery image?
Iamtriple717 said:
Thanks for the help! I tried it multiple times and it says each time "uninstallation failed". Could it be the issue I'm having with the recovery image?
Click to expand...
Click to collapse
I don't think so, but I guess that the best thing You can do right now is to just reflash the whole phone with Odin, but since You get errors in Odin I need to see the log.
I successfully unrooted last night using these instructions and the files provided. I don't know if it'll work for you though.
Instructions: https://stockromupdate.com/how-to-flash-stock-rom-samsung-smartphone/
Files: https://stockromupdate.com/2016/08/...galaxy-s7-edge-sm-g935fd-6-0-1-g935fxxu1apgf/
Note: Make sure you ignore the Home_CSC file AND the Pit tab in Odin. Never touch "Pit" unless you know what you're doing. And also note that the ROM provided might not be the one developed for your country, but it should work fine.
Hello,
I followed the guide at http://https://forum.xda-developers.com/moto-g4-plus/how-to/stock-rom-npjs25-93-14-4-march-1-t3608138.
I went from having TWRP installed and just having blinking white LED to now booting into Android recovery screen (shown here)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now that I'm at the Android Recovery screen, someone mentioned I should just be able to hit wipe data/factory reset option and it should boot me into the OS. However, what actually happens is the unit reboots, shows the motorola sign, buzzes, goes black, shows the motorola sign again, goes black, then boots back into Android recovery screen shown.
I'm not sure how to continue troubleshooting.
The one thing that stuck out to me is it said "Flash signed images after reboot if needed"
Is that what I'm missing? If so, what does that entail?
Any help is much appreciated. Concerned I may have fully bricked the phone.
Thanks from your frustrated friend,
Connor J.
P.s. Model # is XT1625-SS
I realized I forgot to add the model number which is XT1625-SS.
I've bought another moto g4 in the meantime that I'm using.
I originally went wrong by installing the SuperSU in a link from a youtube video that was a link to an older version of SuperSU.
So I know I messed up there.
But I'd like to know if there's a way to remedy it because other than my failed tinkering the hardware on the phone is perfectly ok.