Late last night I went to fix a touchpad that was handed to me, was told that the Android install was started, but had messed up. If I fixed it I could keep the touchpad.
So, i wandered over here and followed RolandDeschain79's how to install android thread, using the novacom,exe route with ACMEUninstaller2 and ACMEInstaller5. After running both of these (and placing the Cyanogen9 Mod on the tablet... i followed the instructions to the T). I got Android to run on it. BUT there was a problem! I got a bunch of notices @ initial startup, (Like 3). I don't remember what the other 2 were, but the biggest problem was the android keyboard would not function. Thinking that it would fix it, I went ahead and re-did what I had already done, running ACMEUninstaller2 and ACMEInstaller5. When I was in the middle of doing this the battery died (wish the stupid thing would just feed off power from my PC when it's plugged into it but apparently not). Now, I'm stuck in a bootloop (i think).
what does it do?:
The WEBOS boot screen, the little circle w/ HP in it? It just sits there. Sat there the entire time it was plugged in, didn't show me it was charging or anything. When I force it to shut off (hold power button and home key) it'll sit there 4 10 seconds or so, then turn itself right back on. I CAN GET INTO RECOVERY MODE however.
What I have done since then:
1. left it sit on the charger for about 7 hours... should be fully charged I hope.
2. Re-ran ACMEUninstaller2
3. Re-ran ACMEInstaller5
my thoughts were that if I can get an older ROM to work on it, I can upgrade to the most current from there.
HELP!!!!
Any ideas would be appreciated. This is the first tablet I've messed with, actually the first tablet I've owned and I'd really like to fix it...
Thanks in advance!
The easiest and most simple means of installing Android is with TP Toolbox. Follow the advice and instructions in the developers forum, you will have to do some reading to understand what you are doing.
I also am listing a link that I think is clear on the install:http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
As for the ROMS, there are a number to choose from. I have jcsullins installed on several TP's as well as pac-man ROM on another. Please take your time to read and decide.
Also, using toolbox will require that you use the naming convention for gapps as outlined in the toolbox thread.
Thank you. I followed the instructions on that site and the touchpad is working excellent.... Minus one glitch thus far: the camera works on boot, but as soon as you go to take a photo the whole screen digitizes and the touchpad loses connectivity with the camera. Is there an easy fix for this?
What ROM are you using? Also, which gapps did you install? Please be as specific as possible.
The ROM I am using is cyanogen 11 and I downloaded the gapps from the same page. The tablet upgraded itself last night and after that everything works great. It said something like upgrading apps, and reinstalled all the apps I had put on it. I'm playing with it as much as possible, making sure it acts like it should.
Thanks 4 all the help thus far
more issues
okay guys I am using invisiblek's cyanogen 11 and gapps... still have an issue with the camera I randomly acting up. it will work and then it won't. I have no clue where to even start with this. the build is from June of 2014. I do have an update available, I don't know if that will fix it but I do not have my laptop available at this current moment, so I cannot try it. Any ideas?
Are you reading the posts in the forum thread for that particular ROM? Other people using it may have encountered and fixed the issue.
I would invite you to read information about the various ROMS in the developer section as issues such as you are describing are
usually addressed and fixes or work arounds are presented.
I do not use the particular ROM you have installed but run other ROMS on several touchpads and do not have the problem you describe.
like an idiot I have not read the other threads regarding this particular CyanogenMod... I will look into them.
Thank you.
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Greasemonkey50701 said:
OK... I'm a dufus sometimes... what's the easiest way to get this thing to simply boot CM? Without going to moboot. Id like this thing to act like it had android on it from the factory. Would it cause a problem if I didn't put the ClockWorkMod on it?? I plan on using TPToolbox any time I need to do something, I have a PC around 90% of the time.
Is this even possible?
Thanks for the help thus far.
Click to expand...
Click to collapse
You can't bypass moboot, and what you're proposing is going to ultimately cause you problems. But if you must, the easiest way to do what you want is to reduce the moboot timeout so that it goes directly to boot quickly. Create (if it's not already there) or edit (if it is) a file named moboot.timeout and put the number of seconds you want moboot to wait before booting CM. You can do that with a root browser like ROM ToolBox lite, or you can do a terminal session and type in:
Code:
su
mount -o remount,rw /boot
cd /boot
echo "1" >/boot/moboot.timeout # will set timeout to 1 sec (defaults to 5)
sync
What problems would this cause? Call me stupid (and I am sometimes) but i really don't forsee any problems caused by doing this...
I think Shumash already answered your question.
You need moboot to boot into Android.
Android is Linux based and Linux requires the use of a bootloader.
The best you can do is to shorten the time out before it boots.
In spite of the best advice given to you...it is your touchpad and you are free to do what you choose.
Even if that means borking it for good.
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Greasemonkey50701 said:
OK. I just re-read my initial post with this idea, and am thinking I wasn't clear enough. What my goal here is is to have my touchpad simply boot straight into Android without going into the moboot list to select whether Android, WebOSRecovery, CWM, etc. boots. What I am wondering is if I take CWM off of it, will it set Android as it's default OS and simply boot that, just like a PC does when it has only one OS on it and like our touchpads did from the factory with WebOS. I'm not looking to brick my tablet otherwise I'd just do it and see what happens.
Thank you for your time and assistance thus far.
Click to expand...
Click to collapse
You were clear enough, but seem to have some misunderstanding of what the sequence is. On boot, moboot times for a default 5 seconds and then automatically boots into Android, unless you screw with it by touching buttons or making selections. If you want it to do that faster, change the timeout as I suggested. You do not need to take anything off of it, and in fact, doing so will cause you grief eventually. If you take CWM off, and want to update your ROM, create a nandroid backup, clear the caches, or do any other low level stuff, you won't be able to. If it's booting into CWM (which you haven't said it does yet), then the moboot.default file has been changed. It should contain the word "CyanogenMod" (w/o the quotes) to boot directly to CM/Android. Use a root browser to edit or recreate it.
Related
When I originally got the TouchPad I played around with just long enough to put CyanogenMod on it then gave it to my parents. Here is the info I got from the device:
Modboot version 0.3.5 (Dont recall the actual version.. I recall seeing something like this)
ClockworkMod version: 5.0.2.6
CyanogenMod version: Alpha 2
Since then I personally got a Galaxy Nexus and have ventured into the world of ROMs. One of the first things I did when I got a hold of the TP again was to install GooManager then browse by compatible ROMs. To my surprise I saw that Black Ice (my fav ROM) was also available in a Tenderloin version which GooManager said was compatible with the TP so I did a Titanium backup and a nandroid backup then wiped back to factory, wiped the cache and wiped the Dalvik cache and flashed Black Ice.
First thing I noticed was that there was now another entry in the boot list named "Black Ice" but it didnt work or do anything. Choosing the original CyanogenMod option did boot Black Ice (after showing a brief CM logo which I assume is part of CWM?). However once booted into Black Ice I wasnt able to get the Wifi to turn on at all. It would flip the toggle but it would just grey out and never actually turn on. Naturally I did a nandroid recovery and its all back to the way it was but it left me with some questions...
1) Does the TP have to be dual-booted with WebOS? Or can I set it up similar to my GNex and have it not prompt for a boot option and run only Android?
2) Should all "Tenderloin" builds work on a TP? And if so what is the proper method for me to switch to a different ROM? The method I used above is what I do for my Gnex but I realize it might be different on TP.
3) Did I do the flash properly and it should have technically worked and the wifi issue i had is fixable?
Thanks for any input!
WoodroweBones said:
When I originally got the TouchPad I played around with just long enough to put CyanogenMod on it then gave it to my parents. Here is the info I got from the device:
Modboot version 0.3.5 (Dont recall the actual version.. I recall seeing something like this)
ClockworkMod version: 5.0.2.6
CyanogenMod version: Alpha 2
Since then I personally got a Galaxy Nexus and have ventured into the world of ROMs. One of the first things I did when I got a hold of the TP again was to install GooManager then browse by compatible ROMs. To my surprise I saw that Black Ice (my fav ROM) was also available in a Tenderloin version which GooManager said was compatible with the TP so I did a Titanium backup and a nandroid backup then wiped back to factory, wiped the cache and wiped the Dalvik cache and flashed Black Ice.
First thing I noticed was that there was now another entry in the boot list named "Black Ice" but it didnt work or do anything. Choosing the original CyanogenMod option did boot Black Ice (after showing a brief CM logo which I assume is part of CWM?). However once booted into Black Ice I wasnt able to get the Wifi to turn on at all. It would flip the toggle but it would just grey out and never actually turn on. Naturally I did a nandroid recovery and its all back to the way it was but it left me with some questions...
1) Does the TP have to be dual-booted with WebOS? Or can I set it up similar to my GNex and have it not prompt for a boot option and run only Android?
2) Should all "Tenderloin" builds work on a TP? And if so what is the proper method for me to switch to a different ROM? The method I used above is what I do for my Gnex but I realize it might be different on TP.
3) Did I do the flash properly and it should have technically worked and the wifi issue i had is fixable?
Thanks for any input!
Click to expand...
Click to collapse
1) yes you have to keep dual boot. A quick search would have given you this info. But when you install android it should default to boot Android in moboot... if you have several entries then I suggest you clean moboot or wipe android from the TouchPad altogether and start off with a cleean install (the stickies have plenty of instructions on how to do any of that
2) tenderloin is the codename so to speak for the TouchPad. You need to read up on the workings of moboot to understand the dual booting method and understand the entries you see when its booting and how to manipulate it (again information readily available on the forum)
3) yes you flashed correctly but your moboot /boot folder has conflicting entries. Most wifi issues have been fixed in all the most stable ROMs. Your issue may be related to conflicts from your install and/or having one of those.devices that is.just persistently going to have android wifi issues. When i say devices I mean yours in particular. Some of us depending on our device have never had issues no matter what ROM we used
Hope that helps...
Sent from my cm_tenderloin using Tapatalk 2
As abrasive as always...
Anyways, he does have a couple of points.
1) Yes, you do have to keep the dual-boot setup. You can change the default to whatever you want, or you can clean it up. There are some nice topics that explain it all throughout the General and Q&A and Dev forums (I don't have them handy). If you want to default to one of those, I can tell you now you need a little bit of familiarity with terminal (which is easiest), or you need to boot back into WebOS, install Preware, and then install CyBoot (which changes boot options).
2) He's right, Tenderloin is the name given to the Touchpad, like es209ra is the name for the Sony Ericsson Xperia X10. It's just what it's called.
3) Wifi issues are something that are hit-and-miss with a lot of people. One thing that seems to fix a lot of peoples' issues is switching your router to one of the lower channels (1-6) rather than the upper (6-13). There's also usually a lot less chatter on the lower 1-3 than closer to 6 (which is the default). Also, set your wireless to WPA2/Personal with AES (no TKIP), and disable WPS (Wireless Protected Setup). This will make your network more secure, and work better with your TP.
3) Another thing I've noticed is that if you switch your Wifi off and then back on, it can take upwards of a minute before it's re-enabled. Not sure why, but it is something to note.
Hope that helps you with a little less attitude than our resident... person... posted above.
Cheers.
Thank you ve6ay!
I was pretty positive Tenderloin was meant for touchpad but was thinking maybe its for actual android tablets only.
For some reason with Black Ice I just could never get the Wifi to enable at all. The latest AOKP nightly wouldnt even flash but I ended up getting AOKP Milestone 5 to flash and its working great! Have definitely experienced the other "normal" wifi issues of losing connectivity and having to switch to airplane mode and back, etc. so I am used to those already
i installed 4.1.2 first time w/ROM GUIDE how to install HP TP the easy way but after used for several days, got error "unfortunately, android kybd stopped".
i followed instruction on this website to uninstall used ACMEUninstaller2(and previous version) but screen displayed hp logo without any lines running up the screen as it supposed to.
i did at least 4-5 times w/same results.
Once i left screen at HP logo till battery drain and TP came back w/ANdroid 4.1.2 still alive but no kybd.
HELP, please!
thank you,
-t
Sorry for the issues you are having.
I used JCSullins TP Toolbox to do my installs. Do you want to keep web OS or install just Android?
gtallmadge said:
Sorry for the issues you are having.
I used JCSullins TP Toolbox to do my installs. Do you want to keep web OS or install just Android?
Click to expand...
Click to collapse
i used CM10 Android 4.1.2 10 JB (20131019)cminstall package Download and follow the guide.
i found lots of replies in forum mentioned about after ACMEUinstaller2, run WEBOSDoctor. i did that and it seemed like the app fixed not only WEBOS(?) but also able to uninstalled after that.
But now I'm trying different packages in easy way guide and wasn't able to install any of them: either after reboot hanged at flash screen till battery drained or some conmponents missing(installed same package you mentioned above).
thanks for your response,
-t
tpham56 said:
i used CM10 Android 4.1.2 10 JB (20131019)cminstall package Download and follow the guide.
i found lots of replies in forum mentioned about after ACMEUinstaller2, run WEBOSDoctor. i did that and it seemed like the app fixed not only WEBOS(?) but also able to uninstalled after that.
But now I'm trying different packages in easy way guide and wasn't able to install any of them: either after reboot hanged at flash screen till battery drained or some conmponents missing(installed same package you mentioned above).
thanks for your response,
-t
Click to expand...
Click to collapse
So, do you want to keep web OS? The advantage of using tptoolbox is that you can really start over, clean cache and and do a complete data reset which wipes previous installs of android and web OS.
For what it is worth, this is what I did as I found web OS to be almost unusable for me. I really liked the OS but the lack of support and available apps made it unsuitable for me. So, installing Android has made the TP relevant again for me and my family. We have Android on three TP's and are not looking back. We do have other Android devices but now the TP is once again our favorite and most versatile device. Kudos to all the developers here for giving life back to the TP.
Here is the link to the easiest install guide for using tptoolbox: http://liliputing.com/2014/06/use-touchpad-toolbox-install-android-erase-webos-hp-touchpad.html
this TP belongs to my sister and she prefers to have both OS. While i was trying to install Android to her TP, i did successfully install 4.2.2 to two other TPs.
i think this troublesome TP is unique!
do you have another way to install android while keeping WebOS?
thx,
-t
tpham56 said:
this TP belongs to my sister and she prefers to have both OS. While i was trying to install Android to her TP, i did successfully install 4.2.2 to two other TPs.
i think this troublesome TP is unique!
do you have another way to install android while keeping WebOS?
thx,
-t
Click to expand...
Click to collapse
I don't want to keep WebOS, because HP touchpad hardware is near the end of life, and WebOS is useless and slow.
I used JCSullins TP Toolbox to help me to install CM11, and currently I stay with the CM11 by JCSullins.
Since CM11 is still under development, I have encountered several CM11 common issues on my HP touchpad, but luckily I found the workarounds for them.
If you don't want to deal with trouble, you should stay with WebOS, CM9 or CM10.
i finally got it to work. i suspected the pkg i downloaded @home missed some bits. i downloaded @work and it worked fine.
i also google checksum app and verified the new pkg.
everything is GREAT!
thank you for all your help.
-t
Hi All,
I've been putting this off long enough, but seeing as I won't see any updates for this device that are non-DM compiled... Thought it's about time I bit the bullet... and used Touchpad Toolbox
So, pre-questions before I go ahead and do it....
1) Going over to DM format, would I still be able to do my TRIPLE BOOT (of WebOS, Android and Ubuntu native)
2) Can I still flash non-DM roms to a DM formatted Tablet?
3) Can I return it back to fully stock
--- there are other questions, but currently distracted at work....
But just curious about those features if I upgraded the volume/partition layouts...??
Thanks, Lister
Hello guys and Gals, this will be my first time posting so please bear with me. I have been trying to find the best option to root my Samsung Galaxy Note 3 Sm-n900a for a while now, seems to be one of the harder phones to root... this will be my first time attempting to root a device, so I want to make sure I do everything correctly. I have watched multiple videos and read a lot of threads on the subject but it is hard to find anything that is current and has the proper links to be files needed. if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it, if you do respond to the thread please dumb it down I am still learning terminology. I am determined to get this done come hell or high water. so if anybody has a good step-by-step walkthrough or video and the time to help me I would greatly appreciate it. Thank you for helping me put a nail in this coffin i I have been trying to do this far too long.
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/note-3-att/general/root-att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
GregJ7 said:
I just did this over the course of hours. I can't say I'm pleased with any of the explanations on xda-developers or found by Google. Unfortunately, writing up a good, full explanation is beyond me right now.
I did this from the Android 5.0.1? Lollipop "OC3" version (seen as the last 3 characters of the "Baseband version" under Settings -> General -> About device). Apparently this version cannot be rooted, however, you can downgrade your version of Android to one that you can root: Android 4.4.2 KitKat ("N900AUCUCNC2"). Apparently you can do something to stay rooted while manually updating to Android 5.0 Lollipop "OC1," but updating to the current AT&T version "OC3" revokes your root access.
I followed the process listed at https://forum.xda-developers.com/no...att-note-3-android-5-0-t3318130/post65467618, but if you are satisfied with having rooted Kitkat 4.4.2, you don't need to do steps 11 and 12. If you want the more recent Android 5.0 OC1, then do steps 11 & 12.
One thing I can do is help you understand some of the things I never saw explained. In the list of instructions you will see some programs you will need. A brief summary of each:
Odin - A program that runs on Windows that will manage some low-level aspects of your phone over a connected USB cable. It is used to install an OS (Kitkat 4.4.2 in this example) after your phone has been Wiped from the boot loader menu (gotten to by turning your phone on holding down VolumeUp + Home buttons). It is nice to have a MicroSD card onto which you can move various things before wiping the phone. (You never need to wipe your MicroSD card. Make sure you don't wipe it when using the Wipe feature in SafeStrap).
Towelroot - This is actual program that roots your phone using a known problem in the phone. After running the program, tap the only button there is to do it. I think this is a safe operation—as in, I think it will tell you if it can't rather than scrozzle your OS.
SuperSU - A program that manages which apps on your phone have root access. After it is installed, when you run a newly installed program that requires root access, SuperSU will pop up a dialog asking you if you want to grant it root access. I saw no indication you can get by without it, even if you don't need to "manage" app root access.
SafeStrap - This is a program that does various things, most importantly installing other operating systems that you previously loaded onto your phone as a file and then letting you choose which one you want to boot to whenever your phone boots up. It installs like a normal program, however from within the program you can "Install Recovery" or "Uninstall Recovery." "Recovery" is a bit of software it inserts into the phone boot process. While booting, if you want to use that software, you tap "Recovery" in the lower left. Tap "Continue" if you just want to boot with the currently active OS (chosen from within the Recovery software under the "Boot" options). With Recovery, you create a new slot for an OS, MAKE IT THE ACTIVE OS, Wipe it (Advanced, NOT format), then can back up a menu and install an OS from your MicroSD card. The purpose of all these shenanigans is so you don't have to lose your working Android install while installing something else.
Titanium Backup - A software backup program that requires root access to work. It also has a ton of other features loosely related to backing up. It is the simplest way to prevent AT&T from updating your version of Android to the unrooted current version. Having said that, it is anything but simple because of the user interface. You might investigate alternative methods for preventing auto-updating.
Be aware that whatever software (e.g., file manager) you use to hunt down files and folders on your phone is probably not going to be showing you everything. There are hundreds of programs that your phone uses, some of which are hidden. Titanium Backup does appear to be capable of showing a true full list of apps (including system apps). This is pertinent, because the AT&T Software Update program is hidden very well.
Potential costs:
$10-20 US approximately for a MicroSD card. There's fast ones that are in that price range. Google for reviews.
$5.99 for Titanium Backup from the Google Play store.
Click to expand...
Click to collapse
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
XxLightxX said:
Life got pretty busy there for a minute... I was able to get Titanium Backup I have had a good SD card for a while now safestrap SuperSU towelroot everything that I need. But this being my first time and not really ever using the software, it's giving me a little bit of anxiety. Before trying process the root I had a couple of questions that I definitely would like to get a solid answer on they might sound stupid but I'd rather sound stupid then not have a phone and ask lol. Okay how about we know I have a Note 3 SM n910a AT&T original carrier swapped over to Metro PCS I'm on one of their $50 plans which I think is unlimited everything but no tether so I have been using PDA and foxfi tethering from my phone to my computer... my roommate has a hotspot but he is rarely home. I need to know if it is possible to complete the root in that situation also the person from the thread that you sent me to confused me as far as making sure you have the ROM pre-downloaded. It just confused me I'm to the point I want to have somebody jump on TeamViewer with me and just make sure I don't screw up too bad.. I did go look at them custom robs as well if anybody would like to share their favorites or what they think is a good easy ROM to be able to play around with it and not mess it up too bad I would love any suggestions from anybody
Click to expand...
Click to collapse
I just ended up stayin on kk rooted on mine. Everytime i goto lolipop i brick it. Its almost a hassle to try. I would odin the kk firmware and use towel root. Install xposed and some root apps. If ures is anything like mine dont debloat it. I debloat lightly. And next reboot get all kinds of spen and other force closes. The note 3 in general seem unstable. But i need to restore m8ne back stock now as its keeps force closing. I will be starting mine over for the 100th time it feels like. Dont let my ramblings discourage you. It is a awsome device and having a lgg5 iphone 5 and a few others my note 3s outer glass is destroyed. Got it like that. I would take the note 3 over the rest if i could get it to run rite more than 2 or 3 days at a time. Ive. Always set all my devices the same way. Debloated them the same but this one is really touchy.... Im on here a lot if u gots any ?s just hollar at me.
If you're still interested in an easy way to root, use Wondershare Dr Phone. It worked for me on stock OC1 and then the just used Flashfire to flash whatever I wanted.
I have uninstalled a system app that I shouldn't have (something to do with network conectivity according to the recovery log) and everything was fine until I updated my device. I hadn't restarted it since removing the system app but after tyhe update it will no longer go past the Samsung galaxy logo. I remember doing something similar to either this device or another and I remember that I was abler to get into the system enough to be able to reinstall the neccessary app and fix the problem. However, this time I cannot get into adb at all. adb won't show any devices when in recovery, download mode, or at any of the three stages of the boot screen. I have tried wiping the cache and everything but factory resetting it as I have data that I can't lose. Any help would be appreciated whether getting adb install-existing to work or to pull important files off of the device before a reset. The device runs android 12 not rooted.
(...)
Go back via odin to the original firmware including the correct BIT.
(...)
Flash in Odin using home CSC file, simple
You only need to run ADB in Windows PC terminal or DOS mode in order to Odin flash firmware. No need to run ADB commands in the phone.
Just be sure that you install the "Samsung ADB Driver" into your PC before
you try Odin flashing firmware.
Just be sure you download the proper firmware for your phone.
Good luck, have a great day and have fun!
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode. From here, the phone goes through the initial setup screens but all data is still intact, just not apps. Concerningly, it doesn't ask for you to enter your password, it just puts you on the homescreen, which seems bad from a privacy perspective as any samsung repair tech can easily cause the phone to boot loop. From here, you can back up anything important and factory reset. There is no way to exit safe mode once you've gotten this far.
I don't remember why odin didn't work, it may have been that I couldn't get the firmware to download as Samsung likes to change that stuff all the time or it may not have reinstalled the system app neccessary.
I should've been more clear in the original post but I have not flashed any unofficial firmware just the U1 firmware to remove carrier bloat, but that was way before this occurred. In case it wasn't clear, the problem happened because through
Code:
adb shell uninstall --user 0 package.name
an important system app was removed (something network related) which caused android to crash when trying to start the service. In short: be careful what you remove when using adb and, for all you forum members: read the whole post instead of jumping to conclusions about the user's mistake and if it isn't clear, ask for more details. Again, thank you to all the helpful comments even if they didn't end up working.
ZenDeveloper said:
Thank you to all the help, but eventually I got into the phone. For anyone who may encounter a similar problem in the future:
After the phone reboots enough, it resets all preinstalled apps and removes any user installed ones and goes into safe mode.
Click to expand...
Click to collapse
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
hatoxda said:
May I ask how long it took to "reboot enough"? I'm having issue updating to Android 13. It got into boot loop (the 2nd time actually. I mentioned about it in another thread a few weeks ago. Today I decided to try again). Anyway I am wondering if there's anyway I don't need to reset the whole thing. What you described interested me.
Thanks
Click to expand...
Click to collapse
Sorry for the late reply,
I don't know how many times it needs to reboot to go into safe mode but it seemed like quite a bit maybe 20-30 times possibly like 100. But once it does it'll go through the initial setup screens and let you in without a password. It's very important to backup everything on your device before you mess with any system apps or update especially if you've previously messed with system apps. I however don't use google hence I didn't have a backup of anything and needed to get it off before hand.
It could also be possible that Samsung removed this back door in android 13 and just the act of trying to update it gets rid of it. I don't know I'm just throwing around ideas.
Rule #1 - if a OS is fast, stable and fulfilling its mission, let it be! Firmware upgrades/updates can and do break Samsung's.