Related
There is a thread with this info in it, but it is buried deep in over a hundred pages and I thought the warning for HelixLauncher bared having a new post.
Here is the link to download the update.
http://android.clients.google.com/packages/passion/signed-passion-FRF50-from-ERE27.1e519a24.zip
Looks like that link is dead... here is a mirror
http://dl.dropbox.com/u/113487/signed-passion-FRF50-from-ERE27.1e519a24.zip
And one more just in case the others go down.
http://www.filefactory.com/file/b1chb29/n/update-nexusone-FRF50-signed.zip
Warning!! If you use Helixlauncher, uninstall or remove its defaults. It will go into a Force Close loop, making the phone unusable without booting into recovery again and performing a factory wipe/reset.
How to flash the update, I used these steps and it worked fine, but remember, there is always the possibility to brick the phone.
1. Download file from link up there.
2. Rename the file to update.zip.
3. Note that if you're using Windows and don't have "show file extentsions" turned on in the file explorer you won't see a .zip. Just rename it to "update" (no quotes, of course) because it's already a zipped file.
4. Copy the update.zip file onto your microSD card.
5. With your Nexus One off, hold down the trackball and press the power button.
6. You'll be booted into a white screen with three Android robots on skateboards. Select "Bootloader."
7. On the next screen, select "Recovery."
8. Your phone will reboot, giving you a picture of the Android robot and an exclamation point inside a triangle.
9. Now press the power button and volume up button at the same time. It could take a couple of tries.
10. Now (using the trackball this time) choose "Apply sdcard:update.zip" and let things run their course.
Taken from the update-1 instructions on:
http://www.androidcentral.com/how-ma...your-nexus-one
Also, I don't think my phone rebooted own its own after the update. After a minute or two, I tried hitting power and power+vol up to get the menu and reset manually. During that time it reset and booted up fine. So I say give it a few minutes before trying to reboot after the update finishes.
Edit: a ton of threads have popped into existence about froyo, but I didn't see any with early warnings about Helixlauncher.... ah well, maybe this post can be helpful for someone out there.
Edit 2: From what I am seeing, AT&T phones are on a different build of Android than the T-mobile N1. Seems like if you have an AT&T version you are out of luck for right now. This update was meant for the demo devices given to the Press outlets around launch, before the AT&T phone existed.
thanks for this, just a quick question.
Is this ok to use on a nexus one in england? it's not usa only or something is it?
thanks
Can it be flashed over Cyanogen? I read somewhere that it couldn't...
shrub said:
thanks for this, just a quick question.
Is this ok to use on a nexus one in england? it's not usa only or something is it?
thanks
Click to expand...
Click to collapse
If it is a US update then using it on a nexus one in England might not be a good idea, but I doubt it would hurt the phone, but some things might not work right.
St.Jimmy! said:
Can it be flashed over Cyanogen? I read somewhere that it couldn't...
Click to expand...
Click to collapse
You have to be back to stock recovery, so best to follow the directions in this thread. -> http://forum.xda-developers.com/showthread.php?t=686593
you made my day, man. Downloading...
Marine6680 said:
If it is a US update then using it on a nexus one in England might not be a good idea, but I doubt it would hurt the phone, but some things might not work right.
You have to be back to stock recovery, so best to follow the directions in this thread. ->
I flashed it over cyanogen 5.0.7 Test2 and it worked without any problem. Just helixlauncher is going nuts
Click to expand...
Click to collapse
Yeah I had to do a wipe when Helixlauncher went nuts on me, but Android restored all my apps for me lol.
Re: Official Froyo 2.2 update download, instructions, and HelixLauncher user Warnings
So...can we reinstall helixlauncher safely after updating? Just want to make sure
naynada said:
So...can we reinstall helixlauncher safely after updating? Just want to make sure
Click to expand...
Click to collapse
Not sure if Helixlauncher will already work with Froyo
i keep gettin installation aborted
Ritmjunk said:
Marine6680 said:
If it is a US update then using it on a nexus one in England might not be a good idea, but I doubt it would hurt the phone, but some things might not work right.
You have to be back to stock recovery, so best to follow the directions in this thread. ->
I flashed it over cyanogen 5.0.7 Test2 and it worked without any problem. Just helixlauncher is going nuts
Click to expand...
Click to collapse
Wait what?!?! Your saying it works just flashing over CM? Iv read all day that you have to go back to stock.. Have you tried/know if it works over 5.0.6?
Click to expand...
Click to collapse
Crime843 said:
i keep gettin installation aborted
Click to expand...
Click to collapse
I cant find it in the market anymore .....
johanove said:
Ritmjunk said:
Wait what?!?! Your saying it works just flashing over CM? Iv read all day that you have to go back to stock.. Have you tried/know if it works over 5.0.6?
Click to expand...
Click to collapse
I'm not joking really. I flashed it over cyanogen 5.0.7 TEST 2 and my N1 is working fine. I'm from Belgium and bought the N1 in U.K.
Click to expand...
Click to collapse
Ritmjunk said:
johanove said:
I'm not joking really. I flashed it over cyanogen 5.0.7 TEST 2 and my N1 is working fine. I'm from Belgium and bought the N1 in U.K.
Click to expand...
Click to collapse
Ok I assume you used Paul's release then?
Click to expand...
Click to collapse
johanove said:
Ritmjunk said:
Ok I assume you used Paul's release then?
Click to expand...
Click to collapse
Jeeee yes, sorry .... I just saw the header and this topic is about the official release/download. Indeed I used Pauls release..... sorry my mistake.
Click to expand...
Click to collapse
naynada said:
So...can we reinstall helixlauncher safely after updating? Just want to make sure
Click to expand...
Click to collapse
Ritmjunk said:
Not sure if Helixlauncher will already work with Froyo
Click to expand...
Click to collapse
Yeah I'm thinking the new update broke it, helixlauncher is integrated much deeper into th OS than most apps, so it would be more vulnerable to even small changes
Crime843 said:
i keep gettin installation aborted
Click to expand...
Click to collapse
I read somewhere, that another person had the same issue. Are you using stock recovery? Also, are you on the latest 2.1 update 1? I'm not sure the issue really. Try a search of the other threads, see if there is a solution.
same here... tried it twice with installation aborted each time. Redownloaded the file... renamed and copied to the sd card again.... same results.
Ritmjunk said:
johanove said:
Jeeee yes, sorry .... I just saw the header and this topic is about the official release/download. Indeed I used Pauls release..... sorry my mistake.
Click to expand...
Click to collapse
Cool, ill give it a try then. Thanks for your quick response!
Click to expand...
Click to collapse
Can someone post a link to HelixLauncher? Can't find it in the Market.
Thanks!
about the HELIXLAUNCHER:
there is NO NEED FOR WIPING everything! i had the same problem after updating and these force kills were really anoying.
here's what you have to do
1. remove your sim card (necessary because other wise your phone will reboot in safe mode - don't ask me why, but it did)
2. get into safe mode: (menu button long press while the X flashes on the load, give it a few tries, it vibrate long if it works)
3. delete helix
4. reboot
5. pray and thank me ;-)
worked for me!
Download files and place on SD card:
update-nexusone-FRF50-noradio-signed.zip from Modaco.com (May 24: noradio files added - should work fine for T-Mo & AT&T!)
froyo-rooter-signed.zip from Cyanogen
Titanium Backup -> Backup all user apps
Turn off phone -> Hold Volume Down, then Press Power button
Enter Recovery
Backup/Restore -> Nand backup
Wipe if you have a Sense UI ROM (no wipe needed coming from Cyanogen)
Flash update-nexusone-FRF50-signed.zip
Reboot, you'll get Android-falling-out-of-box
It will reboot into Recovery, select Reboot again
It should boot into 2.2, yay!
You should still have root, but if you want BusyBox (or lost root somehow), Cyanogen has done it again! Go back into Recovery and flash froyo-rooter-signed.zip. Then Titanium Backup will work once again.
Cyanogen for Prez
Paul for vice prez
(no hate on paul... just cant be prez since he wasnt born here )
i'm getting a picture of an Android falling out of a box
joksinjai said:
i'm getting a picture of an Android falling out of a box
Click to expand...
Click to collapse
I got that while the radio was updating, it should boot back into the recovery menu then reboot once more for FroYo
nDrg said:
I got that while the radio was updating, it should boot back into the recovery menu then reboot once more for FroYo
Click to expand...
Click to collapse
It worked! this is my first time doing this, so i got scared of the open box based on Paul's 100% fool proof guide
=)
joksinjai said:
i'm getting a picture of an Android falling out of a box
Click to expand...
Click to collapse
Yep! When it reboots to recovery, reboot again. Updated OP
Thanks Paul And Cyanogen!
As Always...Great work!
iam trying
once your done installing 2.2 get flash
http://www.androidcentral.com/now-we-have-froyo-its-time-feed-flash-android-22
Freaking sweet! I lost root for whatever reason. Glad to see that Paul and Cyanogen pumped this stuff out! And a flashing I will go!
My flash runs like crap unfortunately. I am getting some FCs too on SMSing apps
Does this work on AT&T devices?
AGeleff said:
Does this work on AT&T devices?
Click to expand...
Click to collapse
I think only if you're rooted. I'm not sure.
AT&T users in the Modaco thread have said it worked. Here's one poster who's done it:
http://android.modaco.com/index.php?s=&showtopic=309286&view=findpost&p=1284057
Post #76:
I think you can just not flash the radio, I do have an AT&T frequency too so I am not taking chance, I will remove the radio.img prior to install
Click to expand...
Click to collapse
don't worry about it. Just flash it. You'll get a speed bump. I did. Getting about 1mb faster DL speeds. Its crazy... especially since its mid-day saturday. I'm on ATT 3g in chicago.
Click to expand...
Click to collapse
Though as the previous person said, you may have to remove the radio.img in the zip. I'm totally not sure. Has anyone here done it?
AGeleff said:
Does this work on AT&T devices?
Click to expand...
Click to collapse
It should work on any rooted Nexus handset.
AGeleff said:
Does this work on AT&T devices?
Click to expand...
Click to collapse
People are saying in this thread that it DOES indeed work!
http://forum.xda-developers.com/showpost.php?p=6563603&postcount=255
http://forum.xda-developers.com/showpost.php?p=6563614&postcount=256
so when updating to froyo does rooted nexus one becomes just like the stock one, means do we need to root it again to install custom Rom
Thank you. This is awesome and super easy to execute. Thanks again.
Nice! thanks for the write up.
one thing that confuses me though, i have rooted my phone but have the stock rom (nadroid from cyanogen 506), will i be able to get the OTA when it rolls for the ATT version? Or only manual update for me?
thanks.
Everything works, great post by paul as usual
I followed these steps (was running Cyanogen 5.0.6) and it works perfectly. I have the AT&T/Rogers version. I didn't wipe and all my apps/settings are intact!
Finally a month to month, pay as you go 4G option! Has anyone received the update yet?
Isn't that the update being tested right now? per -> http://www.droid-life.com/2011/11/2...d-and-most-definitely-not-ice-cream-sandwich/
It is not ICS just some little update for pay as you go.
oh WTH here it is. It takes you up to ver. 3.2.4.
http://www.adrive.com/public/a01b15990d561977d8ca76d4e044cacb3e08b3610eb2e337e4a44832b238c89e.html
You may have to redo root afterwards i know i did.
p.s. i hope i am not breaking any rules by posting this if i am you may remove it and i hope you all forgive me.
twinkyz1979 said:
It is not ICS just some little update for pay as you go.
oh WTH here it is. It takes you up to ver. 3.2.4.
http://www.adrive.com/public/a01b15990d561977d8ca76d4e044cacb3e08b3610eb2e337e4a44832b238c89e.html
You may have to redo root afterwards i know i did.
p.s. i hope i am not breaking any rules by posting this if i am you may remove it and i hope you all forgive me.
Click to expand...
Click to collapse
Thanks for the upload! Source? I assume you're part of the "Motorola Feedback Network?"
jm9843 said:
Thanks for the upload! Source? I assume you're part of the "Motorola Feedback Network?"
Click to expand...
Click to collapse
I can neither confirm or deny that statement.
update?
Looks like this update is rolling out to general population. Just got notification on rooted 4g.
However I haven't updated, so no deets!
I just received this update ota
DANOinSD said:
Looks like this update is rolling out to general population. Just got notification on rooted 4g.
However I haven't updated, so no deets!
Click to expand...
Click to collapse
If you are rooted, the update will fail to install.
You can go through the process, get the triangle with the ! on it... hold power and hit Vol + to reboot... then copy the update's ZIP file from /cache to your SD card, reboot into clockwork, select "install zip from SD" to install it and reboot..
You'll loose root, so reboot back into clock work and install the exploit.zip from the universal root thread
I got the update this morning. Installed in about 3 minutes. Location is South West Michigan.
Followed KidJoe's directions, but I found nothing in the cache folder /cache. Is the update located somewhere else?
Sent from my Xoom using XDA App
ggoldfingerd said:
Followed KidJoe's directions, but I found nothing in the cache folder /cache. Is the update located somewhere else?
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
You have to have superuser permission to see the file. I do the copy operation from terminal. Just got done doing this, worked like a charm and I rerooted and reinstalled the Rogue Rana kernel at the same time.
Just got my update as well.
KidJoe said:
If you are rooted, the update will fail to install
You can go through the process, get the triangle with the ! on it... hold power and hit Vol + to reboot... then copy the update's ZIP file from /cache to your SD card, reboot into clockwork, select "install zip from SD" to install it and reboot..
You'll loose root, so reboot back into clock work and install the exploit.zip from the universal root thread
Click to expand...
Click to collapse
I tried this but it didn't work.
The file that was in the cache folder was named "28dbe910f0b5.signed-trygon-HLK75F-from-HLK75D.28dbe910.zip". I copied it to my external sdcard and tried to flash it and it got an error and aborted.
Elysian893 said:
You have to have superuser permission to see the file. I do the copy operation from terminal. Just got done doing this, worked like a charm and I rerooted and reinstalled the Rogue Rana kernel at the same time.
Click to expand...
Click to collapse
Okay, I will give that a try. Thanks!
Sent from my Xoom using XDA App
With mine, I needed to reflash my kernel after flashing the update as well as the root package. Without reflashing the kernel, I was soft-bricked at the red "M" logo.
Me too.. You need your system partition to have the stock apks for this to work. I had to replace my custom framework with the stock framework as well. It patches a boatload of files. It will leave SU alone. But you *will* lose root and CWM recovery - so be prepared to fastboot your recovery back. Then reapply Universal Root.
I had Rogue 143 kernel installed. On reboot - WiFi didn't work (not surprising - as Rogue probably had its own drivers left behind). I reapplied Rogue - and all better again.
Best I can tell - Settings > Wireless/Networks > Mobile Networks > "Verizon Data Service"... If pressed, brings a web page for service setup. This may be new - I don't recall checking it under HLK75D.
Other than that - the update appears benign. There was one curious update file - lte_bp_gota.img @ 24MB. This kinda looks like ROM for the radio card and maybe kernel - but what do I know? It does not appear to be a new bootloader - but @ 24MB - could be all those things.
Is there any way to not run the update and stop the notification from popping up?
To prevent the OTA, put FOTAKill.apk in your system apps.
Reference: http://forum.xda-developers.com/showpost.php?p=13452768&postcount=2
Direct link to file: https://www.dropbox.com/s/u0ygv25a4...3.7_#/XMod-Z_CM-7.1.0/system/app/FOTAKill.apk (source not confirmed, found via Google)
ggoldfingerd said:
Followed KidJoe's directions, but I found nothing in the cache folder /cache. Is the update located somewhere else?
Sent from my Xoom using XDA App
Click to expand...
Click to collapse
Same here...
Edit: sorry, just read above. Thanks!
KidJoe said:
If you are rooted, the update will fail to install.
You can go through the process, get the triangle with the ! on it... hold power and hit Vol + to reboot... then copy the update's ZIP file from /cache to your SD card, reboot into clockwork, select "install zip from SD" to install it and reboot..
You'll loose root, so reboot back into clock work and install the exploit.zip from the universal root thread
Click to expand...
Click to collapse
I copied it from where it originally downloaded to and put it on my SD card and installed through CWR with no problems just had to reflash root afterwards.
My phone kept nagging me to update and I kept exiting out. Apparently somehow I hit install and it updated. I'm on 4.4.4 according to the phone, I don't remember what I was on before I might have been on 4.4.2. I used these files to downgrade from Lollipop previously:
G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar and G900V_NCG_Stock_Kernel.tar
How do I regain root?
Downgrade your Device & root it via previous method,Which you use before.
Bakuryu42 said:
My phone kept nagging me to update and I kept exiting out. Apparently somehow I hit install and it updated. I'm on 4.4.4 according to the phone, I don't remember what I was on before I might have been on 4.4.2. I used these files to downgrade from Lollipop previously:
G900VVRU1ANK2_G900VVZW1ANK2_G900VVRU1ANK2_HOME.tar and G900V_NCG_Stock_Kernel.tar
How do I regain root?
Click to expand...
Click to collapse
Odin the NGC file down in the notes #4 then root with towelroot. Download SuperSU from play store. Update binaries and reboot phone. If you want safestrap as a recovery you must first download busybox from the play store and install it. Then safestrap will install properly.
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Next time install titanium backup pro and freeze SDM to stop the updates.
[email protected] # said:
Downgrade your Device & root it via previous method,Which you use before.
Click to expand...
Click to collapse
Sounds easy enough.
Tulsadiver said:
Odin the NGC file down in the notes #4 then root with towelroot. Download SuperSU from play store. Update binaries and reboot phone. If you want safestrap as a recovery you must first download busybox from the play store and install it. Then safestrap will install properly.
http://forum.xda-developers.com/ver...w-to-update-to-g900voc4-5-0-keeproot-t3068546
Next time install titanium backup pro and freeze SDM to stop the updates.
Click to expand...
Click to collapse
The note #4 states
4. If you do not already have root access you must first flash the G900VVRU1ANCG_Full_Odin.tar (flash in Odin's PDA slot(AP in Odin v3.09+)), root with Towelroot (this version does not require internet access), then proceed with the above process.
Click to expand...
Click to collapse
When I clicked the G900VVRU1ANCG_Full_Odin.tar it says it is for Galaxy S4? Is that right? Also how does this way differ from the way I originally did it which was seen here
Bakuryu42 said:
Sounds easy enough.
The note #4 states
When I clicked the G900VVRU1ANCG_Full_Odin.tar it says it is for Galaxy S4? Is that right? Also how does this way differ from the way I originally did it which was seen here
Click to expand...
Click to collapse
Yes, this is actually for the S5.
The difference is all the FCs you have to wade through. Also, the one I suggested is a clean and complete reinstall. It will wipe your SD card and you start fresh. Both will work provided you are not on lollipop. If you are on lollipop you should use the method I suggested.
Tulsadiver said:
Yes, this is actually for the S5.
The difference is all the FCs you have to wade through. Also, the one I suggested is a clean and complete reinstall. It will wipe your SD card and you start fresh. Both will work provided you are not on lollipop. If you are on lollipop you should use the method I suggested.
Click to expand...
Click to collapse
Sorry FC's? I am unfamiliar with the abbreviation. Also was confused when you said SDM, what does that stand for so I know what to freeze when I do it? Much appreciated.
Edit: Also is there a particular reason you recommended a full wipe of everything? I only ask because I hate doing wipes and I never did find a good way to back stuff up really.
Bakuryu42 said:
Sorry FC's? I am unfamiliar with the abbreviation. Also was confused when you said SDM, what does that stand for so I know what to freeze when I do it? Much appreciated.
Edit: Also is there a particular reason you recommended a full wipe of everything? I only ask because I hate doing wipes and I never did find a good way to back stuff up really.
Click to expand...
Click to collapse
FC = force close (aka crash)
SDM - Samsung Data Migration (freeze update software)
Not to answer for tulsadiver... but in my opinion wiping ensures you get rid of any stray "orphan" files that may be even a little borked. Has happened to me before so wiping is often a good way to go.
skeeterpro said:
FC = force close (aka crash)
SDM - Samsung Data Migration (freeze update software)
Not to answer for tulsadiver... but in my opinion wiping ensures you get rid of any stray "orphan" files that may be even a little borked. Has happened to me before so wiping is often a good way to go.
Click to expand...
Click to collapse
Alright one last thing, whats the best way to back stuff up so I can hit the ground running if I decide to do a wipe?
Bakuryu42 said:
Alright one last thing, whats the best way to back stuff up so I can hit the ground running if I decide to do a wipe?
Click to expand...
Click to collapse
You could use titanium backup.
Ok so I went ahead and tried to repeat the steps I did the last time I rooted and so far its not going to well. I've done up to #6 in the instructions here, but when I try to install Busy Box it says I am not rooted properly. Towel root said I was rooted sucessfully though? What should I do?
Bakuryu42 said:
Ok so I went ahead and tried to repeat the steps I did the last time I rooted and so far its not going to well. I've done up to #6 in the instructions here, but when I try to install Busy Box it says I am not rooted properly. Towel root said I was rooted sucessfully though? What should I do?
Click to expand...
Click to collapse
Did you install and setup supersu?
mrjiggywiggy said:
Did you install and setup supersu?
Click to expand...
Click to collapse
The instructions say not to till I install safe strap. Then again because I was previously rooted its actually already installed on there... is that a problem?
Btw a root checker app is also claiming I am not rooted.
Bakuryu42 said:
The instructions say not to till I install safe strap. Then again because I was previously rooted its actually already installed on there... is that a problem?
Btw a root checker app is also claiming I am not rooted.
Click to expand...
Click to collapse
You need to install supersu otherwise root won't work.
mrjiggywiggy said:
You need to install supersu otherwise root won't work.
Click to expand...
Click to collapse
Well I followed those instructions last time and didn't have an issue? Also it seems I can't simply uninstall the superSU I have installed already. I installed it through safestrap like the instructions told me.
Bakuryu42 said:
Well I followed those instructions last time and didn't have an issue? Also it seems I can't simply uninstall the superSU I have installed already. I installed it through safestrap like the instructions told me.
Click to expand...
Click to collapse
Open supersu and install what it tells you, then it should work.
superSu wont open it just gives me a black screen
Bakuryu42 said:
superSu wont open it just gives me a black screen
Click to expand...
Click to collapse
See if it will go ahead and install again from the play store.
Tulsadiver said:
See if it will go ahead and install again from the play store.
Click to expand...
Click to collapse
The playstore shows its installed already and uninstall only uninstalled an update. Tried running it after that and still didn't work, reinstalled it again and still nothing. I also have safestrap installed, which is also not working.
You better start over again. Go Odin the NGC retail tar again. You are too jacked up. After towelroot, install SuperSU from play store. Update binaries and reboot. Then download busybox from play store. Install it. Then install safestrap.
Tulsadiver said:
You better start over again. Go Odin the NGC retail tar again. You are too jacked up. After towelroot, install SuperSU from play store. Update binaries and reboot. Then download busybox from play store. Install it. Then install safestrap.
Click to expand...
Click to collapse
Is there a particular reason it has to format the sd card?
I can't find this anywhere. Every guide seems to assume that everyone has a micro SD in their phone. Currently, I don't have one. I'm wondering if an S7 Edge root is possible without an SD card.
diraga said:
I can't find this anywhere. Every guide seems to assume that everyone has a micro SD in their phone. Currently, I don't have one. I'm wondering if an S7 Edge root is possible without an SD card.
Click to expand...
Click to collapse
try this
mashardpro said:
try this
Click to expand...
Click to collapse
I have tried the CF-Auto-Root method twice now, both resulting in being stuck on boot like the other times. However, maybe I needed to wait longer? Next time I attempt a root I will leave the phone alone for at least 15 minutes before I call it a failure. Still, the post you linked seems to be for older firmware. Would you still recommend the method for Nougat? Thanks for the reply.
diraga said:
I have tried the CF-Auto-Root method twice now, both resulting in being stuck on boot like the other times. However, maybe I needed to wait longer? Next time I attempt a root I will leave the phone alone for at least 15 minutes before I call it a failure. Still, the post you linked seems to be for older firmware. Would you still recommend the method for Nougat? Thanks for the reply.
Click to expand...
Click to collapse
then you can try twrp , and use adb sideload if you don't have sdcard
mashardpro said:
then you can try twrp , and use adb sideload if you don't have sdcard
Click to expand...
Click to collapse
I think I've isolated the problem. After using adb sideloader to install magisk and antiroot remover, I'm prompted to reboot. In other guides, there is a further options screen after pressing the reboot button which has a couple checked boxes and a button that says "Do Not Install". I see this screen for maybe a third of a second after selecting Reboot before the device reboots on its own. Just tried this and now I'm stuck on the Samsung boot logo once again.
Note: There are many errors in the adb sideloader log relating to being unable to mount/unmount /data/ and stuff like that that I know are related to having an SD inserted.
Edit: I should also note that I am new to android. Fresh newbee from iOS, but I have been jailbreaking for the past 9 years. Still in over my head I think.
diraga said:
I think I've isolated the problem. After using adb sideloader to install magisk and antiroot remover, I'm prompted to reboot. In other guides, there is a further options screen after pressing the reboot button which has a couple checked boxes and a button that says "Do Not Install". I see this screen for maybe a third of a second after selecting Reboot before the device reboots on its own. Just tried this and now I'm stuck on the Samsung boot logo once again.
Note: There are many errors in the adb sideloader log relating to being unable to mount/unmount /data/ and stuff like that that I know are related to having an SD inserted.
Edit: I should also note that I am new to android. Fresh newbee from iOS, but I have been jailbreaking for the past 9 years. Still in over my head I think.
Click to expand...
Click to collapse
hmmmm, I am a bit confused as well. I am successful with that way. Or read this for other options. But I do not know work or not, because the last link I had never tried
mashardpro said:
hmmmm, I am a bit confused as well. I am successful with that way. Or read this for other options. But I do not know work or not, because the last link I had never tried
Click to expand...
Click to collapse
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
diraga said:
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
Click to expand...
Click to collapse
Well, it seems like all I know already I mentioned, better use of existing first now while waiting for someone who can help you. btw, the root will be used for what?
diraga said:
Still confused... I really don't want to reset my phone for the fourth time today. Please help!
Click to expand...
Click to collapse
Once data is wiped in twrp then reboot back to recovery and connect usb to pc. You should be able to copy SuperSU zip via mtp and your phone should show up on pc. Flash SuperSU zip once copied
mashardpro said:
Well, it seems like all I know already I mentioned, better use of existing first now while waiting for someone who can help you. btw, the root will be used for what?
Click to expand...
Click to collapse
Deleting stock apps, installing adblock, exploring non-Google Play apps, possibly installing custom ROM. I enjoy seeing what my phone can do.
ASHLEY117 said:
Once data is wiped in twrp then reboot back to recovery and connect usb to pc. You should be able to copy SuperSU zip via mtp and your phone should show up on pc. Flash SuperSU zip once copied
Click to expand...
Click to collapse
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
diraga said:
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
Click to expand...
Click to collapse
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
diraga said:
The phone is recognized on the PC but there are no folders. Any files I try to drag over come up with an error. Furthermore, I could use the stock firmware USB to store the necessary files on it, but I can't seem to navigate to the same storage destination via the TWRP file browser.
Click to expand...
Click to collapse
so you have twrp now?
ASHLEY117 said:
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
Click to expand...
Click to collapse
That's... a really good idea. Going to try right now!
mashardpro said:
so you have twrp now?
Click to expand...
Click to collapse
I've had no trouble installing TWRP whatsoever. I've done it five times today!
diraga said:
That's... a really good idea. Going to try right now!
I've had no trouble installing TWRP whatsoever. I've done it five times today!
Click to expand...
Click to collapse
seems nice, good luck. maybe lacking some finishing touches you need to do. I remember well my first too so, and the key is I have to format the data in twrp
ASHLEY117 said:
You could copy SuperSU zip to a usb flash drive and use the otg adapter that came with the s7? Twrp support otg usb install.
Click to expand...
Click to collapse
mashardpro said:
seems nice, good luck. maybe lacking some finishing touches you need to do. I remember well my first too so, and the key is I have to format the data in twrp
Click to expand...
Click to collapse
Update: Still stuck on Samsung boot logo after 15+ minutes after successfully loading from usb drive. TWRP still skipped right by the reboot options screen after the install... I have no clue why it's doing that. It's like it's taking the command to reboot after I press the button and processing it while it is going to the next screen. I don't know. Hopefully someone does. It's so close!
EDIT: IT WORKED!!! Had to format and then installing from usb drive worked great! Thank you so much!!
diraga said:
Update: Still stuck on Samsung boot logo after 15+ minutes after successfully loading from usb drive. TWRP still skipped right by the reboot options screen after the install... I have no clue why it's doing that. It's like it's taking the command to reboot after I press the button and processing it while it is going to the next screen. I don't know. Hopefully someone does. It's so close!
EDIT: IT WORKED!!! Had to format and then installing from usb drive worked great! Thank you so much!!
Click to expand...
Click to collapse
I am glad to hear it. Like I said, just need the final touch that you might forget
mashardpro said:
I am glad to hear it. Like I said, just need the final touch that you might forget
Click to expand...
Click to collapse
False alarm! Root checker says my phone is not rooted... I'm lost... At least my phone booted?
diraga said:
False alarm! Root checker says my phone is not rooted... I'm lost... At least my phone booted?
Click to expand...
Click to collapse
so if you have twrp and your phone is booted, then take a look this. quite easy to understand
mashardpro said:
so if you have twrp and your phone is booted, then take a look this. quite easy to understand
Click to expand...
Click to collapse
Currently following this tutorial and awaiting boot past the Samsung logo. Hoping it works. I see no reason why it shouldn't.
Edit: Running a rooted Android. Thanks