I've noticed a few pre-Froyo changes that seem to have appeared suddenly with no warning:
1. Report button when an app force closes
2. No longer have root with Paul's superboot as Root Explorer and Quickboot don't work. Re-running the Superboot reinstates root.
3. Phone seems quite a bit smoother
Has anyone found any other changes? Also, can you say which ROMs you've had. According to something I read on the official Nexus One forums, rooted phones stay on the update white-list.
I'm on the stock EPE76 (via Paul O'Brian) previously with Paul's superboot root.
nexus5894 said:
I've noticed a few pre-Froyo changes that seem to have appeared suddenly with no warning:
1. Report button when an app force closes
2. No longer have root with Paul's superboot as Root Explorer and Quickboot don't work. Re-running the Superboot reinstates root.
3. Phone seems quite a bit smoother
Has anyone found any other changes? Also, can you say which ROMs you've had. According to something I read on the official Nexus One forums, rooted phones stay on the update white-list.
I'm on the stock EPE76 (via Paul O'Brian) previously with Paul's superboot root.
Click to expand...
Click to collapse
There's a whole other thread right below this one talking about this. Why start a new thread?
A
Arghh- must have missed it. Someone close this please
Related
Hello all
Have searched this forum, but im not really sure what to do.
I've used titanium backup to perm remove a few stock apps, the exchange stock app and amazon app
Now i can't recive any updates OTA, and i get this message..:
assert failed: apply_patch_check("/system/app/Stock.apk"....
E:Error in /sdcard/download/OTA_Ace_HTC_WWE_172_405_3_r2_1_32_405_6_release_1632939lowfu0y78jktpp2.zip
(status 7)
using 2.2 android version number 1.32.405.6
please help
//Cham
You can't accept OTA updates when you are rooted.
I see, but only used temp root with visionary
is that going to affect something?
Or what are my options to get a hold of updates in the future, a costum rom instead? I do kinda like the stock rom, just without stock apps
anyone?
Once again, if you are rooted, it doesnt matter how, you CANNOT accept ota update.
If you deleted something you shouldnt have, then restore the backup to that, or do a factory reset and re-root.
Ok i just figures since it was TEMProot that it didn't matter. Tnx for the reply, tried the factory default option (no luck), is there any place where I can get the Stock firmware to re-flash the phone?
Or would anyone in here recommend another rom ? Tons of custom roms, as I can tell.
Thread moved in Desire HD General.
go here and youll find your rom that you need,
you need the ones that are "RUU_Ace_HTC_WWE" in the file name, as these are what we call World Wide Editions
Thank you very much.
Just to make sure I do not **** something up, what are the steps i should follow, to install the rom?
This is what I did: http://forum.xda-developers.com/showthread.php?t=888109
Got the same problem -- some time ago I removed some "useless" apps from my /system/app folder, and when 1.72 update was released I wasn't able to install it in any way (I was trying to follow this guide). I restored the missing apps, and then everything went fine using the guide mentioned above!
Hope this helps.
sitlet said:
You can't accept OTA updates when you are rooted.
Click to expand...
Click to collapse
Sorry but that ain't correct... You *can* update your phone if you're rooted, the main problem is that root will be gone after update. The best solution is to *always* reject OTA updates provided by HTC and wait until devs here have found a safe way to update your device without losing root privileges.
Thank you
Thank you all, it gave perfectly sense since I'm quite happy with the stock firmware, i'll stick with this. The root is not so necessary for me at least for now
I'm glad it was corrected that visionary did not remove the ability for OTA, that was also what I've read before used it.
Sorry if this has already been posted.
Superboot for N1 GRI40
Tested and working
http://android.modaco.com/content/google-nexus-one-nexusone-modaco-com/298782/08-mar-superboot-erd79-gri40-rooting-the-nexus-one/
super easy method for rooting.
Not a "super easy" way to root the Nexus, just 'cause you have to unlock the bootloader first...and there're plenty of post about having problems after that. I prefer to wait for a Gingerbreak, or a "SuperOneClick" for the GRI40.
Worked on my phone like a charm. Bootloader unlocked.
flixos said:
Not a "super easy" way to root the Nexus, just 'cause you have to unlock the bootloader first...and there're plenty of post about having problems after that. I prefer to wait for a Gingerbreak, or a "SuperOneClick" for the GRI40.
Click to expand...
Click to collapse
What are these problems you speak of regarding unlocking the bootloader? I am curious because ever since I unlocked, my phone will not seem to keep settings such as alternate keyboards or what the default action for the home key is. If you can point me to a thread it would be much appreciated.
jimbobalu said:
What are these problems you speak of regarding unlocking the bootloader? I am curious because ever since I unlocked, my phone will not seem to keep settings such as alternate keyboards or what the default action for the home key is. If you can point me to a thread it would be much appreciated.
Click to expand...
Click to collapse
I've seen post at modaco about people having issues after using Superboot. I'm not telling that those issues are only about the app, probably there are another issues involved.
Hi I am an new user with a rooted N1 running GRI40, I want to root mine to enable navigation outside US and install the latest release of Google Maps.. but I don-t want to mess with the bootloader.. is there a z4root kinda method yet?
No z4 style method available yet, but you can roll back to an older version of android and use z4 or whatever. Once rooted you can install a pre-rooted version of 2.3.3...
Sent from my Nexus One using XDA Premium App
flixos said:
I've seen post at modaco about people having issues after using Superboot. I'm not telling that those issues are only about the app, probably there are another issues involved.
Click to expand...
Click to collapse
Flashing modaco's superboot has nothing to do with how the phone behaves because of unlocking the bootloader. They are independent. Unlocking the bootloader does NOT affect anything other than allowing you to use fastboot commands to flash full partition images to your device. That's it.
And you shouldn't be using modaco's superboot unless you need/want insecure boot. You should use ChainsDD's superuser zip (link in my sig), which justs roots your device, without flashing an insecure boot.img
efrant said:
Flashing modaco's superboot has nothing to do with how the phone behaves because of unlocking the bootloader. They are independent. Unlocking the bootloader does NOT affect anything other than allowing you to use fastboot commands to flash full partition images to your device. That's it.
And you shouldn't be using modaco's superboot unless you need/want insecure boot. You should use ChainsDD's superuser zip (link in my sig), which justs roots your device, without flashing an insecure boot.img
Click to expand...
Click to collapse
Yep, i understand that; but, under a stock Nexus One, in order to flash superboot, you have to unlock the bootloader first (if i'm not wrong).
I'm going to have a look to your ChainDD's stuff right now.
flixos said:
Yep, i understand that; but, under a stock Nexus One, in order to flash superboot, you have to unlock the bootloader first (if i'm not wrong).
I'm going to have a look to your ChainDD's stuff right now.
Click to expand...
Click to collapse
I don't think you understand what I'm trying to say: It's superboot that is likely messing things up with people's phones, NOT unlocking the bootloader.
Like I said, unlock your bootloader, and flash ChainsDD superuser package, and you will have a stock ROM with root, perfectly stable. (The only thing that the package does is adds two files to your device that give you root. That is all.)
If you don't want to unlock (and I can't understand/imagine why people would not, given that many folks have already shown that HTC still honors the warranty), then ignore everything I'm saying.
Thanks so much, got it
By the way, i will wait for another SuperOneClick...developer said that it's just a matter of time to make it work on Gingerbread.
I recently rooted my atrix with superoneclick then i accidently updated then i belive i still had my root until i went to install a 3d theme then my phone crashed and wouldnt get past the at&t screen so i had to erase everything now on my phone i still have "super user" in my app draw but i cannot side load apps did i lose my root? what do i have to do to sideload apps again ? and i guess re root my phone
Yes i am a newb i am comming from IOS and an iPhone 4 please dont flame
If you updated, you mean 4.1.57, this is what I did to re-root when I lost mine after updating and SuperOneClick wouldn't work.
http://forum.xda-developers.com/showthread.php?t=1013931
Ok so i read that so basically i have to flash my phone back to default then root again?
Yeap, that's exactly what I did, but in that same thread, I think someone else outlined using aRoot to go over SuperOneClick.
Originally Posted by donbar85
I'm pretty new to Android (two weeks now), and want to ensure I don't end up with a bricked device, so I apologize for the 'noob' question here. I rooted with SuperOneClick. Has anyone else used this script successfully with that root method, or will it only be successful with aRoot?
Also, if I need aRoot, can I run it over top SuperOneClick, or would it be best to unroot, run aRoot (or let the script root) and then run the script?
I appreciate all the hard work I've seen done in these forums and appreciate any help anyone can offer.
---
Yes you may safely run aroot over superoneclick. Aroot is the recommended method because it cleans up a lot of things Superroneclick does.
----
Originally Posted by DJQ1212
Yes you may safely run aroot over superoneclick. Aroot is the recommended method because it cleans up a lot of things Superroneclick does.
Thank you both. I believe I will try running aRoot over my SuperOneClick root and then try out the script. Thanks again!
Click to expand...
Click to collapse
Yup the aRoot script is used in the GladiAtrix and possibly the GingerBlur rom as well. Either way. SOC is crap, not meant for atrix anyway. aRoot was written specifically for the Atrix. If you want to update to 4.1.57 read through the retain root thread over in atrix development.
after update, i can still see "su" installed in /system/bin/
I am unable to use it, getting permissioned denied message, any solutions ?
sam_t610 said:
after update, i can still see "su" installed in /system/bin/
I am unable to use it, getting permissioned denied message, any solutions ?
Click to expand...
Click to collapse
This has been explained many times. updating kills root, even though you still have superuser installed. to retain root you need to use the script in the development section when updating from 1.26 to 1.57. flash back to 1.26 and try again.
Problem: GingerBreak simply sits and churns forever trying to exploit and root my tablet but never succeeds, I have left it running for almost an hour once.
My notes
1. I started with a stock install of 3.0 on the tablet and rooted with GingerBreak no problem.
2. I tossed the recently leaked 3.1 update.zip onto my SDCard and flashed using the stock methods.
3. Checked if root was maintained through the update, and it was not.
4. Double checked that USB Debugging is enabled, even disabled and re-enabled to make sure.
5. I have a clean SDCard in the tablet and mounted with no issues.
6. I have removed and reinstalled GingerBreak to try and see if that would clear things up.
I have seen a few other posts on threads that people have had no issues using GingerBreak on 3.1 but for the life of me I cannot get it to successfuly root my device.
If it comes down to it, I will just return to stock and go about it another way. But, I thought I would inquire if anyone had any suggestions for the current situation.
Are you tried iconiaroot-1.0.apk special for HC3.1 ?
look for it in developement section
Ah, thankyou for pointing out that thread. This has allowed me to root on 3.1 stock.
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Stock Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
Stock ODIN for the P900 can be found here: http://forum.xda-developers.com/showthread.php?t=2724895
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
Thank you for your help. Now I will be able to use my tablet more frequently
dragunbayne said:
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
Click to expand...
Click to collapse
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
dragunbayne said:
Hello, I have had a few people ask about how I reverted back to stock and managed to root without having reboots so here is an outline including links.
First you will need to use ODIN to go back to the original stock firmware.
Odin for P907A can found here: http://forum.xda-developers.com/galaxy-note-pro-12/general/sm-p907a-att-version-news-t2850564/page1
For those who don't know how to use ODIN, here is a nce guide for you: http://androidcentral.us/2014/02/how-to-flash-firmware-using-odin-samsung-devices/
Now the next thing you need to do is root using TowelRoot, but DO NOT install SuperSU yet! After rooting use the debloat script in this thread (You run it from your device using terminal, I used the terminal function in ROM Toolbox): http://forum.xda-developers.com/showthread.php?t=2797540
I only used the option to disable KNOX and the updater along with the option to disable the startup sound.
Once you have successfully done those things, you may now install SuperSU. It will no longer ask you about KNOX, because it is properly disabled and will not cause you any reboots. My Note Pro has been rock solid stable and lightning fast after doing this.
NOTE: You will not be able to update to new firmwares after this.
Thanks to:
najoor
torreon91
Please make sure you hit thanks in these guys' threads for their hard work!
EDIT: If Jellybean comes out for our tablet I would not update unless the trade off was worth it to you. Or obviously if an exploit for the jellybean update were found then you would want to. If you did want to update, you could re-enable the updater by using the enbloat script that was with the debloat script.
Click to expand...
Click to collapse
Is there a way to do this, but for the SMP-900 version the first link with the odin files state that they are only for the SM-P907 version? I have reverted back to stock but my tablet reboots qute often and with school starting it would be great to avoid that while taking notes. Thanks!
acaldrn2 said:
Is there a way to do this, but for the SMP-900 version the first link with the odin files state that they are only for the SM-P907 version? I have reverted back to stock but my tablet reboots qute often and with school starting it would be great to avoid that while taking notes. Thanks!
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2724895
I will add it to the main post also.