Hello everyone! I'm new to this forum and kinda newb in this all business..
I have a rooted Nexus 1 device with recovery, I recently updated my phone to the following:
Build Number: FRF85B
Baseband V: 34.41.00.32H_5.08.00.04
After updating everything works fine except from the Market, which is gone!
I tried updating to CM6 with Google Addons and the Market worked, but I didn't want to lose all my applications, SMS, etc.. so I restored..
Is there anything similar to Google Addons but for Froyo 2.2?
You're just about 2 generations behind, and running non-official build (which disables paid Market). Why do you expect the Market to work?
Update to FRF91, or to recent FRG83.
Use the bold link in my signature to get to the collection of all official stock ROMs and OTAs, and update your FRF85B to FRF91 by applying an update from there.
As I mentioned I'm a noob.. :/
Anyway, I downloaded FRF91,
when I'm trying to flash it I get:
E:No signature (575 files)
E:Verification failed
Installation aborted.
Same thing with FRG83.. What went wrong?
What recovery are you using? Use Amon_RA's 1.8 or above, and disable signature verification.
And if you flash full ROM (~80 MB) - you'll lose the root and the recovery. Be prepared to root again and reinstall the recovery. Wiki can guide you with root.
Ok, I updated to Amon_RA 1.9.0-alpha (1.8 link was broken) and updated to FRF91.
Still... No market!
What am I gonna do?!
Check that you indeed have FRF91 on your system (Settings/About/Phone).
Then go to Settings/Applications/Manage/All/Market, and do "clear cache" and "clear data".
Then run Market.
Checked and I do have FRF91 installed..
And I can't do that because the market is not there... It vanished from my device..
BTW Jack, I really really appreciate you trying to help me, thanks a lot.
If you don't have Market at all - then you're missing its APK that you accidentally erased.
Since you have root (and if you don't - then root):
adb push Vending.apk /system/app/
Get the Vending.apk from the FRF91 ROM you've downloaded, it's under - surprise - /system/app
In case it doesn't help - then something is bad in your setup, and the best thing would be to wipe and reinstall everything from scratch, including the ROM.
Man I'm such a noob.. I can't manage to push it, i'll describe what i've done step by step, tell me what i've done wrong please..
1.Turned USB Debugging on.
2.While the device is turned on (not in bootloader) i connected it to my pc, I didn't mount the device.
3.In SDK tools folder i opened the command window.
4.I typed adb devices, my device was found.
5.I typed adb shell, a $ symbol appeared.
6.Typed adb push c:\sdk\vending.apk /system/app
(I placed the vending file in c:\sdk)
7.Got: adb: permission denied
Either you already have it on your phone, or you're not rooted.
do:
adb shell ls /system/app/V*
(Android is case sensitive!)
You should see "Vending.apk" present. If present - it'll be easier to wipe and reinstall than to try and solve the problem. If not present - check if you have root by running any root application.
Man.. It's present..
Guess I'll wipe and reinstall everything.. Hate to lose everything though (especially my unlimited Shazam lol)....
BTW, I need to also reinstall the radio?
Or just the ROM and the ROOT?
And should I do it in a certain order?
Install Titanium backup, back up the applications, wipe, install a custom ROM, restore Titanium backup.
You won't gonna believe, I was about to wipe it all and then I found this file - http://www.multiupload.com/HV1MWXXXY0 and managed to push it!
Market is working fine right now.
Thanks a lot for your help!
I learned a lot today thanks to you :]
Yeah, i'm trying to look for a root method for 2.2.1 on the Nexus One, but I have yet to find one.
How hard did you look?:
http://forum.xda-developers.com/wiki/index.php?title=Nexus_One/Guides_&_Tutorials#Root
Sent from my Nexus One using XDA App
I already looked at it, it says it supports 2.1, not 2.2.1
I believe SOC and Rage still work..http://forum.xda-developers.com/showpost.php?p=9703879&postcount=19
Sent from my Nexus One using XDA App
thank you,
I have just one question.
I get a 'adb' is not a recognized as an internal or external command when I do the commands in CMD.
What am I doing wrong? I downloaded the lastest version of Android SDK
At Cmd prompt, navigate to the sdk folder where the adb file is...
Sent from my Nexus One using XDA App
I've just rooted my 2.2.1 with SuperOneClickv1.5.5 by ShortFuse with guide from Unlockr. Waaaayy much easier than last time when I rooted my Legend.
If you are on FRG83 (not FRG83D) you can use VISIONary by Modaco. It can be found here:
http://android.modaco.com/content/software/320350/19-nov-r14-visionary-one-click-root/
First things first, place a ROM (I recommend CM modified that removes the hboot require for 0.33.0012 check found here: http://www.megaupload.com/?d=VLBH27Z0) on the root of your sdcard, along with a zip of gapps.
Next, open up VISIONary, and make sure Temproot on boot and Set system r/w after root are checked. Then click Temproot Now
Next install via terminal the Amon_RA recovery 2.0 found here:
http://forum.xda-developers.com/showthread.php?t=611829
After rebooting into recovery, wipe cache/data, flash the ROM then the gapps you placed in your sdcard earlier.
That's it!
*note that if you install CM, update ROM manager through the market, and make sure you flash recovery version 2.5.1.4 (found under "All ClockworkMod Recoveries")
hi all,
I was running my TX with advanced kernel v4, rooted:
http://forum.xda-developers.com/showthread.php?t=1922925
yesterday i installed Miui Security from here:
http://forum.xda-developers.com/showthread.php?t=1663222
Then the root is gone. I checked that /system/bin/su and /system/xbin/su are still there but they are inter-linking with symbolic link when i view them with root explorer.
fixes tried:
When i use ADB push trying to replace them, it said "too many symbolic links encountered"
I cannot remove both file as i cannot su in ADB shell.
I booted into CWM recovery but ADB is not enabled in CWM.
I reflashed the flashable zip in CWM to gain root access with no error message prompted, but after reboot into system the SU files are still the same
I reflashed the kernel with flashtools and fastboot, still no change applied to the phone.
Any idea?
finally got it fixed...
I rewrite the updater-script in the CWM flashable zip for root package to force remove both /system/bin/su and /system/xbin/su and rewrite them back.
Thanks for watching...
I've the same problem
Hi guys,
I've the same problem.
I've flashed my Xperia T with MIUI-3.11.22 rom.
I've activated the root permission on Security tab, but my phone doesn't give me the root access (I've tried to install adbd insecure and BusyBox but the result is "problem with root access".
Some ideas?
Thx
My ota zip update through CWM is failing on the 'debuggerd' file from /system/bin. If someone could pm me with the original 'debuggerd' file from 4.2.2 I would be very grateful. I think the Stickmount app changes or replaces the file so it won't pass the authentication check of the system files. Please don't send me the debuggerd file if you have installed Stickmount. Much thanks in advance. I'm trying to help another forum member with the same problem.
me too, my bak file was from 4.2.1 which has sha1sum of df2e705da097e4d535b4f4d98fab3bd76601e76c
I think 4.3 wants one with a2323a0c8e245e3879d6b8beff6b2c4802045271
o8x8 said:
me too, my bak file was from 4.2.1 which has sha1sum of df2e705da097e4d535b4f4d98fab3bd76601e76c
I think 4.3 wants one with a2323a0c8e245e3879d6b8beff6b2c4802045271
Click to expand...
Click to collapse
I'm having the same problem. (Groid is helping me)
My OTA update failed because of the same issue (/system/bin/debuggerd), once I copied from stock 4.2.2, and try, it failed againm this time was with /system/bin/gzip)
so, thought this was going to be pain, what I did was copied /system/bin/ from stock 4.2.2 files to my N7's /system/bin/ folder (except SuperSU bin file).
once I did, I re-tried OTA update, it worked.
Yes, yes, yes, thank you tiggggr. I downloaded the file you attached to my pc, renamed to just 'debuggerd', copied to my N7, copied file to /system/bin with Root Explorer, booted into CWM recovery, installed zip. After installing, said 'NO' to question about recovery and said 'Yes' to try to keep root. Booting up now. Thank you again. I'll let you know about root after 'Android is updating' finishes.
So, I didn't keep root, as expected, but everything else seems fine. On first boot I got a message like 'process Acore has stopped' or something like that, but it booted up. I waited a couple of minutes and restarted and did not see that message again. Now to check Chainfire's posts about reflashing SuperSu to get root back. If you had the debuggerd error, replacing the file with the one in tiggggr's post did the trick for me.
Screenshot:
Regaining root was more of a pain than I thought. I tried flashing Chainfire's SuperSu 1.43 per his G+ post, but didn't have a recovery to flash it with. Finally used Wugfresh Nexus Root Toolkit, chose Android *.*.* Any, plugged into a back port with the original cable, and chose the Root button with custom recovery checked. I was pretty sure my drivers were all good, so I didn't even install them again first. I wasn't paying attention on the custom recovery part where it said TWRP was selected instead of CWM (you can change that.) I followed the rest of the directions, then booted into TWRP and flashed the SuperSu 1.43 zip from Chainfire. After rebooting, I have root and TWRP recovery. Tested with Root Explorer and Titanium Backup for root and all is well. Whew! Sorry for making 4 straight posts, but I know some other members were in the same circumstances as me.
How do I make a recovery to avoid the issues you ran into regaining root
Sent from my Nexus 7 using Tapatalk 2
Groid any tips on this? I'll try replacing the debuggerd file, but would like it to be as simple as possible to regain root after the update.
Link to Wugfresh Nexus Root Toolkit
http://www.wugfresh.com/nrt/
Link to Chainfire's SuperSu 1.43
http://plus.google.com/+Chainfire/posts/Jkuu84odnx6
Here is what I did and it wasn't really too difficult. Put Chainfire's zip in the root of your sdcard with the OTA zip you have there already. After replacing the 'debuggerd' file I flashed the update through CWM. It worked fine, but I lost root and CWM. Downloaded the Wugfresh NRT and installed it. As stated earlier, I followed the guide in the link and set the device as Android *.*.* and hit the root button with install recovery checked and the original usb cable plugged into a good port. It rooted and installed TWRP recovery and that was fine. After booting up, go into TWRP recovery and flash the SuperSu zip. After booting up again, you should have root and TWRP recovery.
Since you are unlocked and rooted, if your drivers are good, just go to the Root button. You shouldn't have to unlock the bootloader and wipe everything. My update preserved all my programs and data. Follow the guides and watch the videos. My N7 is running great.
tiggggr said:
Glad to hear it helped! For me it was pretty straight forward. I had rooted stock ROM, so flashed CWM, applied zip from CWM, booted, noticed I had lost root, downloaded SuperSu 1.43 zip, booted into CWM, applied zip, booted and was up to 4.3 with root.
Click to expand...
Click to collapse
That's great you didn't lose recovery. I'm not sure why I lost CWM, but I don't think I had updated Rom Manager and that may be why. At least it wasn't hard getting recovery back on with the Wugfresh NRT. TWRP seems like a good recovery, so I will just stick with it.
Mine failed again
I downloaded and replaced the deguggerd file with the one tigggger posted, but still can't get updated.
{
"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"
}
Could anyone help?
coollyjordan said:
I downloaded and replaced the deguggerd file with the one tigggger posted, but still can't get updated.
Could anyone help?
Click to expand...
Click to collapse
Did you make sure to rename the file by removing the .rename.zip? The file you copied to /system/bin should be named simply debuggerd and you should not have tried to unzip it, if you tried. It should have replaced the debuggerd file there unless you renamed the original one first. Since you received the same error, you could try copying it to /system/bin again. You must be rooted to copy into that folder. Are you using a custom recovery? You are installing the OTA zip file, not the official OTA that ends in .tgz right?
Groid said:
Did you make sure to rename the file by removing the .rename.zip? The file you copied to /system/bin should be named simply debuggerd and you should not have tried to unzip it, if you tried. It should have replaced the debuggerd file there unless you renamed the original one first. Since you received the same error, you could try copying it to /system/bin again. You must be rooted to copy into that folder. Are you using a custom recovery? You are installing the OTA zip file, not the official OTA that ends in .tgz right?
Click to expand...
Click to collapse
Yes, I'm pretty sure I renamed the file to debuggerd, didn't unzip it.
I placed the debuggerd file to /system/bin with es file explorer.
I'm using the stock recovery.
I'm not sure what you said about the official OTA ends in .tgz, I just went to settings-about tablet-system updates and pressed the check now button to get OTA.
Groid said:
Link to Wugfresh Nexus Root Toolkit
http://www.wugfresh.com/nrt/
Link to Chainfire's SuperSu 1.43
http://plus.google.com/+Chainfire/posts/Jkuu84odnx6
Here is what I did and it wasn't really too difficult. Put Chainfire's zip in the root of your sdcard with the OTA zip you have there already. After replacing the 'debuggerd' file I flashed the update through CWM. It worked fine, but I lost root and CWM. Downloaded the Wugfresh NRT and installed it. As stated earlier, I followed the guide in the link and set the device as Android *.*.* and hit the root button with install recovery checked and the original usb cable plugged into a good port. It rooted and installed TWRP recovery and that was fine. After booting up, go into TWRP recovery and flash the SuperSu zip. After booting up again, you should have root and TWRP recovery.
Since you are unlocked and rooted, if your drivers are good, just go to the Root button. You shouldn't have to unlock the bootloader and wipe everything. My update preserved all my programs and data. Follow the guides and watch the videos. My N7 is running great.
Click to expand...
Click to collapse
Can root be regained by using [Google Nexus 7 TOOLKIT V5.0.0] - http://forum.xda-developers.com/showthread.php?t=1809195
WUG's toolkit acts weird on my laptop and doesn't seem to run right.
coollyjordan said:
Yes, I'm pretty sure I renamed the file to debuggerd, didn't unzip it.
I placed the debuggerd file to /system/bin with es file explorer.
I'm using the stock recovery.
I'm not sure what you said about the official OTA ends in .tgz, I just went to settings-about tablet-system updates and pressed the check now button to get OTA.
Click to expand...
Click to collapse
Sorry to be confusing. I have a custom recovery (TWRP) and with a custom recovery, the update can be done with the OTA update that was repackaged as a .zip file. Then in recovery, I chose to Install a zip and chose the OTA update zip file. Since you have the stock recovery, and you got the update started, you must have been using the correct update file. Since you got the same error on debuggerd, I wonder if you didn't get it copied correctly into /system/bin. Can you compare file dates or sizes to make sure you got the right one? That debuggerd file did fix the update error for me and for a couple of other people I heard from. I would try again after confirming the debuggerd file. You could check permissions also, but I didn't have to change them. RW, R,R. (just compare to permissions on other files there).
Foxman2k said:
Can root be regained by using [Google Nexus 7 TOOLKIT V5.0.0] - http://forum.xda-developers.com/showthread.php?t=1809195
WUG's toolkit acts weird on my laptop and doesn't seem to run right.
Click to expand...
Click to collapse
Do you still have your custom recovery? If so, you should be able to flash the SuperSu zip and regain root. I lost recovery and the Wugfresh toolkit worked great for me to choose root and install custom recovery. If you try to install the drivers from the toolkit, I think it gives you a way to see if the correct drivers are installed, and install them if necessary. You could try that. Using the original N7 cable is important. I don't know of another way to get root and custom recovery, but there are many in the forum that may be able to help you with Fastboot commands or the ADB push method. I have used those, but only following specific instructions for a specific purpose. In any case, if the debuggerd file works to install the update, you will be able to regain root.
Groid said:
Do you still have your custom recovery? If so, you should be able to flash the SuperSu zip and regain root. I lost recovery and the Wugfresh toolkit worked great for me to choose root and install custom recovery. If you try to install the drivers from the toolkit, I think it gives you a way to see if the correct drivers are installed, and install them if necessary. You could try that. Using the original N7 cable is important. I don't know of another way to get root and custom recovery, but there are many in the forum that may be able to help you with Fastboot commands or the ADB push method. I have used those, but only following specific instructions for a specific purpose. In any case, if the debuggerd file works to install the update, you will be able to regain root.
Click to expand...
Click to collapse
Groid, all is well and thanks for the help! I replace the debuggerd file and then ran the OTA install via ClockWorkMod. This went fine now and the Nexus 7 updated to 4.3
I then reboot and did still have the custom recovery, flashed the SuperSU file and back in business! Thanks again for the help!
Thank U! However I used Nexus 7 Toolkit, reflashed the stock 4.2.2, then got an OTA to 4.3. Though I lost my root and some local data, I've got 4.3!
Anyhow, thank you for helping me out!
Groid said:
Sorry to be confusing. I have a custom recovery (TWRP) and with a custom recovery, the update can be done with the OTA update that was repackaged as a .zip file. Then in recovery, I chose to Install a zip and chose the OTA update zip file. Since you have the stock recovery, and you got the update started, you must have been using the correct update file. Since you got the same error on debuggerd, I wonder if you didn't get it copied correctly into /system/bin. Can you compare file dates or sizes to make sure you got the right one? That debuggerd file did fix the update error for me and for a couple of other people I heard from. I would try again after confirming the debuggerd file. You could check permissions also, but I didn't have to change them. RW, R,R. (just compare to permissions on other files there).
Click to expand...
Click to collapse
Hey there browsing with all those ads is a real pain, therefore i wanted to edit the hosts-file since adaway didn't worked.
Therefore i wanted to use the content of this page and add it to my hosts-file:
http://someonewhocares.org/hosts/
problem is, i can't mount /system with total commander although root is working (flashtool installed busybox fine as the root popup comes up and asking for root).
the bootloader is unlocked and via adb shell in root mount i also get:
Code:
[email protected]:/ # mount -o remount,rw /system
mount -o remount,rw /system
mount: Operation not permitted
is there another way? can i somehow flash the hosts-file trough recovery?
You must not have full root. Install RIC Killer or XZDR to defeat this protection.
i thought only "temp root" existed besides the full root? well NUTS Dual Recovey is also installed... gonna check out the RIC Killer...
:Edit: Ok, neither the "Windows" RIC-Reboot Remount Fix worked, as the ZIP-Version trough Dual Recovery....
what would be the best way to reinstall root (altough it is an system app?)
The command you specified works fine for me. Further, root explorer via ES Explorer.
What root APK do you have installed? SuperSU, for example, has a "complete unroot" command you can use unroot.... but since there's no one-click root for 5.1.1, re-rooting isn't possible without reflashing. I suppose a dirty flash back over top 51.1 isn't as risky as between versions, so you could try that in order to re-root.
How did you root initially? My process for 5.1.1 has been to flash the FTF, SuperSU, and XZDR all in one go, no reboots between. People have had issues getting full root to work especially if the SuperSU and XZDR steps are separated by a reboot.
sorry for the long pause i was at vacation and there i had no chance to try something (since a backup would be needed first in case of fire )
I've been installing a prerooted tft the day 5.1.1 came out. RIC Killer didn't worked and fully unrooting well... doesn't work either
Flashing a zipped SuperSU or something like that won't work? I mean - i can unroot it go to XZDR and flash it again - this should work right?