Related
Hi all, I'm running a rooted A500 (Android 3.1 build number Acer_A500_4.010.13_COM_GEN2) using the 2.6.36 Honeyvillian 1.0 kernel (so I could OC) and would like to upgrade to a rooted ICS. But since I changed from the stock kernel I get a little confused trying to follow other threads on what to do. The threads seem to start out on topic but tend to drift and for somebody like me, that can make it very hard to understand. I'd like to stay away from a custom ROM, no insult to the hard working dev's intended. You guys have saved alot of my devices from ending up on the top shelf of the closet. I'd like to upgrade to a "stock" rooted ICS with proper bootloader, kernel, etc. If I decide later to try a dev's ROM then I'll always have that option, but since I've never messed with ICS...stock may do all I need. I'd like to root for OC because some of the things I do seem to run better if the device is OC'd. So, what I need are a clear set of instructions on what to do. OTA's dont work, I'm guessing thats because of the root and kernel. Any help would be appreciated. Thanks.
There are 2 threads with Stock rooted ICS roms in the developer section. Read each and choose the one that suits you. Also, you may need to separately update the bootloader. To do this there is a new tool in the developer section called afterota 1.02. This will help automate the process for you.
Thanks Cruise, but thats where the problem comes in. I've read over the threads you mentioned and I get lost. Because the threads are a generic install method and cant be refined to match my exact situation I dont know where to start. I dont know if I need to return to stock kernel before I do anything else or if I can flash the new stuff the way it is. Do I need to flash the bootloader first or the ROM and what about flashing recovery? Thats why I asked for a clear step by step, the Dev threads tend to be a little hard to follow for somebody with my novice knowledge.
realityrat said:
Thanks Cruise, but thats where the problem comes in. I've read over the threads you mentioned and I get lost. Because the threads are a generic install method and cant be refined to match my exact situation I dont know where to start. I dont know if I need to return to stock kernel before I do anything else or if I can flash the new stuff the way it is. Do I need to flash the bootloader first or the ROM and what about flashing recovery? Thats why I asked for a clear step by step, the Dev threads tend to be a little hard to follow for somebody with my novice knowledge.
Click to expand...
Click to collapse
If you want to go completely stock (stock kernel, non-rooted), then you need only to install one of the Stock ICS Roms. This set's your bootloader back to a stock condition. So that's simple enough. You can do this through CWM
You said you're on Honeyomb right now. So my suggestion, is to follow these steps to upgrade your a500 to ICS.Go Here and read the steps;
http://forum.xda-developers.com/showthread.php?t=1622425
Pay attention to step 4. You have a choice. Stock Rom with Full Root, or (in small print (stock rom no root).
If you decide to install Stock Rom No Root, then skip steps 5 and 6. Just copy the file to your EXT SD Card, boot to your recovery (pwr & Vol-) and install Zip From SD. It'll be a done deal. Recovery gone, ICS Stock bootloader and rom.
I have you do steps 1-3 because I want you to write down your UID!!!!!! It's the only thing that will save you if something messes up.
Then you can decide if you want to root and install some custom stuff later.
MD
MD, can you run setCPU w/o Root? I didn't think so. Since this OP requests the ability to OC specifically I think that the steps listed would all need to be followed in Civato's post.
RR, Here are the steps I recommend, it's an opinion, and I think the best route to take as a fairly novice rooter, I've done my A500 many times and BN Nooks, but nothing else and am not a DEV, but have professionally been in IT for 20 years...so I use novice loosely here...
First, know why you're getting your CPUID:
http://forum.xda-developers.com/showthread.php?p=25429111#post25429111
Don't forget to BACKUP!!
Second, select which ROM you want on your tab, I recommend putting a couple on the MicroSD card so that you can test them. DON'T INSTALL ANYTHING, JUST PICK A COUPLE OF ROMS AND PUT THE ZIPS ON THE SD.
Don't forget to BACKUP!!
Third, follow the steps in the post that MD listed, read twice, run once...
http://forum.xda-developers.com/showthread.php?t=1622425
Don't forget to BACKUP!!
Fourth, flash one of the ROMs you chose previously while in recovery. Can't give you steps on this because they are all different unless you're just using the option in step 4 of the above post (stock w/ root)
Don't forget to BACKUP!!
Fifth, not sure if you can OC the stock w/ root or not, but if not pick a custom ROM and test several, they're all great, and see what fits your needs best. I use Flexreaper Extreme and love it, posted below, but look at ALL of them and find the one you like best, they're all GREAT! We have great DEVs here.
http://forum.xda-developers.com/showpost.php?p=22964651&postcount=1
Don't forget to BACKUP!!
Good Luck, Have fun, and did I mention to make sure you Backup before each step so that you can get back to that point if you run into issues, and make sure you write down or put in a text file on a different device your CPUID...both very important.
Good luck again!
-DB
Thanks everybody for the info but I think I'll be staying on HC for now. The linked threads are the problem I mentioned in the OP. If you look at those threads with novice eyes they are incredibly hard to follow. Not sure why I cant find simple instructions but I do appreciate everyone's help. Maybe somebody will come up with a guide for dummies. Until then I guess I'm stuck with HC. Thanks again for the info.
Mate, it can be daunting even to experienced flashers...
My advice, go to this thread - http://forum.xda-developers.com/showthread.php?t=1622425
This has been cleaned up to make it easy to understand...
I use the manual method to go to apx mode but each to their own...
Now, follow each step. Make sure each step has been followed EXACTLY. Don't skip ahead or you will regret it, sooner than later...
If you have a doubt, go back a step.
Good idea to read through to the end first, especially the bit about checking you sdk...
Good luck....
Step 1: Install Acer drivers. DONE
Step 2: Get cpuid. DONE used afterota, got cpuid and SBK.
Step 3: Get SBK. DONE (see Step 2) I guess I could verify my cpuid and SBK
using the link in this step.
Step 4: Place ROM's on SD card. DONE
Steps 5 & 6: Enter APX mode and Installing ICS bootloader. NOT DONE
I downloaded the apx utility tool and the V7 flash package. The flash package does NOT contain an .a500apx file. The utility tool instructions say to select the .a500apx file NOT the .zip. Where do I find the correct .a500apx flash package? The last step in the Automated Flashing Tools section says to turn off the tablet and power on. I've read you're supposed to flash a ROM before turning off the tablet. Which one is correct? Can I do this with my current configuration as described in the OP or do I need to return my kernel to stock? And last...is ICS really worth the trouble? Thanks again for everybody's input. I do appreciate everybody taking the time to help out.
realityrat said:
Step 1: Install Acer drivers. DONE
Step 2: Get cpuid. DONE used afterota, got cpuid and SBK.
Step 3: Get SBK. DONE (see Step 2) I guess I could verify my cpuid and SBK
using the link in this step.
Step 4: Place ROM's on SD card. DONE
Steps 5 & 6: Enter APX mode and Installing ICS bootloader. NOT DONE
I downloaded the apx utility tool and the V7 flash package. The flash package does NOT contain an .a500apx file. The utility tool instructions say to select the .a500apx file NOT the .zip. Where do I find the correct .a500apx flash package? The last step in the Automated Flashing Tools section says to turn off the tablet and power on. I've read you're supposed to flash a ROM before turning off the tablet. Which one is correct? Can I do this with my current configuration as described in the OP or do I need to return my kernel to stock? And last...is ICS really worth the trouble? Thanks again for everybody's input. I do appreciate everybody taking the time to help out.
Click to expand...
Click to collapse
According to the written steps., you have to download the flash package you want to use from here;
http://a500bootloaderflash.tk/bundles/20120527/
Save then to the same directory you unzipped the tools.
Just checked and everything is in order, so looks like you missed a step
Actually, you really don't have to flash a rom before restarting. If you have a ICS rom installed, more than likely it will boot. (I hope) However, most custom roms have kernels altered to work with the unlocked bootloader. But I would try with your current ICS configuration. If you have any issues, then you can install the custom ICS rom that you saved on your SD Card.
Is it worth it? I think so. Eventually, all support for HC based roms will end. It's the nature of the beast. Most people will be on ICS, and if you have issues with HC, you may not get any recent support.
It's like having a Froyo rom, and trying to get support when most are on Gingerbread and moving to ICS.
You will get responses like "upgrade your device". I will in the near future, end all support for my HC based roms.
MD
Moscow Desire said:
According to the written steps., you have to download the flash package you want to use from here;
http://a500bootloaderflash.tk/bundles/20120527/
Save then to the same directory you unzipped the tools.
Just checked and everything is in order, so looks like you missed a step
Actually, you really don't have to flash a rom before restarting. If you have a ICS rom installed, more than likely it will boot. (I hope) However, most custom roms have kernels altered to work with the unlocked bootloader. But I would try with your current ICS configuration. If you have any issues, then you can install the custom ICS rom that you saved on your SD Card.
Is it worth it? I think so. Eventually, all support for HC based roms will end. It's the nature of the beast. Most people will be on ICS, and if you have issues with HC, you may not get any recent support.
It's like having a Froyo rom, and trying to get support when most are on Gingerbread and moving to ICS.
You will get responses like "upgrade your device". I will in the near future, end all support for my HC based roms.
MD
Click to expand...
Click to collapse
Thanks for the response MD but I still get confused on the step to download the flash package. When I save the file to my computer it no longer has .a500apx in the file name or extension. for example, "a500-icsv6-pubrecovery0.2.a500apx" (from the index of bundles) is downloaded and saved as "a500-icsv6-pubrecovery0.2.zip" so do I extract it and select that file when asked by the utility tool? The guide for the tool says not to select the .zip but to select the .a500apx file. but I dont see one to select.
Also, you said I didnt have to worry about flashing the ROM before restarting. I am currently running HC 3.1 so will an ICS bootloader boot to a HC ROM.
Again, thanks for taking the time to answer my questions. It is really appreciated.
realityrat said:
Thanks for the response MD but I still get confused on the step to download the flash package. When I save the file to my computer it no longer has .a500apx in the file name or extension. for example, "a500-icsv6-pubrecovery0.2.a500apx" (from the index of bundles) is downloaded and saved as "a500-icsv6-pubrecovery0.2.zip" so do I extract it and select that file when asked by the utility tool? The guide for the tool says not to select the .zip but to select the .a500apx file. but I dont see one to select.
Also, you said I didnt have to worry about flashing the ROM before restarting. I am currently running HC 3.1 so will an ICS bootloader boot to a HC ROM.
Again, thanks for taking the time to answer my questions. It is really appreciated.
Click to expand...
Click to collapse
Ok, the link I sent you, is an index of all apx files. It should download as an apx file (I just now checked, and it downloaded and saved as an apx.)
Not sure why they are saving as zips on your system, as none of them are in a zip format. Try doing a "file save as"
Sorry for confusion about rom. I forgot you have an HC rom. I'm running several threads right now for folks with issues. Downlaod an ICS rom to your SD card, so you can install it after you update your bootloader.
MD
EDIT: If you still have issues getting the apx files, let me know, and I'll re-package them in a real zip file and upload it for you.
Moscow Desire said:
Ok, the link I sent you, is an index of all apx files. It should download as an apx file (I just now checked, and it downloaded and saved as an apx.)
Not sure why they are saving as zips on your system, as none of them are in a zip format. Try doing a "file save as"
Sorry for confusion about rom. I forgot you have an HC rom. I'm running several threads right now for folks with issues. Downlaod an ICS rom to your SD card, so you can install it after you update your bootloader.
MD
EDIT: If you still have issues getting the apx files, let me know, and I'll re-package them in a real zip file and upload it for you.
Click to expand...
Click to collapse
Thanks MD, trying to download the apx files doesnt work for me. Not sure why but .zip is the only option I'm given even if i use "save as". So if you could upload the files for me I'd appreciate it. Also, since I will have to disconnect the tablet from the PC after flashing the bootloader can I just power it off, disconnect from PC, reboot into recovery and then flash the new ICS ROM? I also want to be sure that coming from a stock (but rooted) HC rom with a custom kernel wont affect anything. Thanks again for all your help.
realityrat said:
Thanks MD, trying to download the apx files doesnt work for me. Not sure why but .zip is the only option I'm given even if i use "save as". So if you could upload the files for me I'd appreciate it. Also, since I will have to disconnect the tablet from the PC after flashing the bootloader can I just power it off, disconnect from PC, reboot into recovery and then flash the new ICS ROM? I also want to be sure that coming from a stock (but rooted) HC rom with a custom kernel wont affect anything. Thanks again for all your help.
Click to expand...
Click to collapse
I zipped 4 apx packages for your 500. They have the ICS Booltoader and different recoveries. Unzip them to the same folder as your installation package.
http://www.4shared.com/zip/9TE6rTH-/500Bootloader_package.html
Yes, after you finish the bootloader/recovery installation process, turn tablet off. Press and hold Vol- and PWR till you see 2 lines of text in upper left corner, then release both. This will be your recovery menu. From here, you need to follow the instructions from the Rom page where you got your new Rom for the installation. Pretty simple really.
Also, I can't advise you on which recovery to use. I haven't tried the public recovery or TWRP yet.
MD
Thanks MD. Got the files downloaded. I'm gonna read over the threads a few times and make sure I havent missed anything and I also want to research some of the ROM's available. I'll probably give it a try in the next few days. Thanks again for all your help.
**UPDATE**
After reading the threads multiple times and following the instructions carefully I am now running ICS 4.0.3 with updated bootloader!! Everything went fine with only a couple problems that I was easily able to overcome. I'd like to address those problems so if anybody else has problems, 1: when entering the sbk its important to note that the spaces between the sets of numbers ARE needed, and the 0x at the beginning of each set has to be typed with a lowercase "x". 2: I used ezterry ICS 1.031.00stock- full root with busybox, and more tweaks and a500 public recovery. Following the instructions for this ROM I used the "clean up tablet" option in recovery. This DOES NOT do a full data wipe. So first boot had my custom boot animation and all my other apps and settings still there. ICS didnt like this and kept forcing reboots. I had to do a full data wipe and all is good now. I'm on ICS rooted stock and OC'd and loving it. Thank you all for your help, without your input I dont know if I would've tried this but I'm glad I did and I really appreciate everyone taking time out of their busy schedules to help some guy in NY get some ICS love. Thank you all again!
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
the lemming said:
Hello
My phone tells me that it is ready to update to Kit Kat.
Before I install Kit Kat I would like to learn how to go back to Jelly Bean if things go t1ts-up.
So, I would like to learn how to root my phone?
I would also like to learn how to backup everything including the Jelly Bean operating system, and I would like to know how to revert my phone back to Jelly Bean?
Please forgive my ignorance, but this whole process genuinely scares me. I have only ever rooted my Samsung Ace phone once and the experience left a bitter taste in my mouth.
I did manage to root my phone. I also thought that I had created a backup but when I tested the backup I discovered that my phone got wiped and I ended up with a brick. I eventually found an official Samsung ROM but it wasn't the one I wanted and it caused a few problems, especially with the Bluetooth feature.
I hope you can understand or appreciate my apprehension with even contemplating such a task on my expensive Nexus 4.
Cheers muchly
Click to expand...
Click to collapse
You might want to check out the Wugfresh's toolkit if you are not incline with technical stuff. The toolkit is in the Development section.
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
the lemming said:
Hello
I have no idea what Wugfresh's tool-kit is.
Sorry
Click to expand...
Click to collapse
I would suggest that you study up and follow this guide here. http://forum.xda-developers.com/showthread.php?t=2010312
I was like you when I first got the nexus. Didn't know what to do and the steps seems to be so complicated. Hell..I even took couple of days to finally succeed in installing the drivers. And for me I think it is better to learn the basics of using adb before trying out the toolkits. If you start with toolkits and you will later on rely entirely on the toolkits. This is not good as some problems, the toolkits might not be able to solve it for you.
Btw, look into original android development for wug's toolkits. It is pinned there. Should be easy to find.
Sent from my Nexus 4 using xda premium
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Here is my attempt to make you learn :-
1. Say Bye Bye to your phone OS version.
2. Open Command Prompt or Terminal.(Assuming, you have SDK & Drivers installed)
Code:
adb devices
It shall return you the device id.
3. Reboot to BootLoader
Code:
adb reboot-bootloader
4. Check for your device's recognition in FastBoot Mode.
Code:
fastboot devices
5. I assume you have all the files(Factory Image tar.gz extracted to a folder)
just type :-
Code:
flash-all.bat
BOOM...
You are now on stock KitKat !
Now, To get a Custom Recovery (IMHO go with TWRP),
1. Download latest recovery from the official website.
2. Type when in FastBoot Mode.
Code:
fastboot flash recovery openrecovery-twrp-2.6.3.4-mako.img
(Or whatever the name is)
3. Reboot your device.
Now, to get the ROOT ACCESS, after booting up the device,
1. Download the latest UPDATE-SuperSU zip from here.
2. Keep it somewhere in DEVICE STORAGE.
3. open TWRP RECOVERY
4. FLASH that ZIP
5. HIT THANKS !
Have Fun ...
Welcome to the Flashing Fraternity !!! LOL
miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
BOOM...
You are now on stock KitKat !
Click to expand...
Click to collapse
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
the lemming said:
Hello
Thank you for replying but I fear that I will not be following your advice at the moment.
I initially asked how to ROOT my phone so that I can learn how to do backups and recoveries. My phone is ready for the Over The Air official upgrade.
I want to take things one step at a time rather than causing problems by blindly following code.
Sorry
Click to expand...
Click to collapse
If you want official OTA update of KitKat you should update it, and after that unlock bootloader and root phone. That way nothing will go wrong.
If you unlock bootloader and root your phone OTA update will cause problems like stuck in bootloop(your phone will be stuck on nexus logo and it will never boot into android)
If you want to learn about rooting I suggest you this http://forum.xda-developers.com/showthread.php?t=2367406
this is excelent tutorial how to root your nexus 4 http://forum.xda-developers.com/showthread.php?t=2018179
and if you are more comfortable to hear and see somebody do it you can check out this page it have video of full process and pictures for every step http://nexus4root.com/nexus-4-root/how-to-root-nexus-4-windowsmac-osxlinuxubuntu/
Good luck!:cyclops:
miku3191 said:
You seem to be taking interest in Rooting and stuffs. I would suggest you to get handy with a few ADB and FASTBOOT commands and you won't need any toolkit ever in Life !!!
Its very very very easy in Nexus Devices.
Good luck!:cyclops:
Click to expand...
Click to collapse
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
the lemming said:
This process is an absolute nightmare.
All I want to do is back-up my Jelly Bean phone operating system and have it safe in case the OTA Kit Kat goes wrong. I thought that this was sensible and safe practice before doing any updates, especially something as serious as a system update?
I have now tried several Tutorials on how to root my phone and all I have succeeded in doing is wiping my phone clean and returning it to Factory Settings. The latest Tutorial was here
http://forum.xda-developers.com/showthread.php?t=2010312
I followed the following advice to this point
1) All of the files that are required, need to be in one (i.e., the same) directory. It does not matter what it is called, but all the files need to be in there, with NO subfolders. EVERYTHING needs to be extracted into this one directory;
2) Download the attachment from the end of this post and extract the contents to the directory created in step 1. (Latest version for Windows is here). Note: if all you want to do is unlock your bootloader, skip to step 7 in this section (C).
7) Reboot your device into bootloader mode (by turning it off, hold volume down, and press and hold power) and plug it into your computer;
8) Open a command prompt in the same directory (i.e., make sure you are in the same directory as your files are located). You can hold the shift key when you are in the folder in Windows explorer and right-click in a blank spot and it will open a command prompt.
I then get to the bit about rooting
E. Optional -- Root
If you want to get root access follow the steps below. (And no, this will not flash a custom recovery, and not, it will not make you "not stock".) Unlocked bootloader required. See steps above.
1) Download (to your computer) the latest version of CWM (from here) or TWRP (from here) for your device;
http://www.clockworkmod.com/rommanager/
http://www.clockworkmod.com/rommanager/developers/mako?name=Google Nexus 4
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
The point you are missing is that your fear is clouding your ability to simply read and comprehend the proper steps to take. My friend rooting your phone with a toolkit is a simple task but you ask what is Wugs toolkit instead of taking the time to search for it an read up. YOu do not want to root your phone but to have someone do it for you. I used to do this for people back in the days where I would log into their pc and root their phones from my home.
My friend its simple your bootloader is unlocked and now all you need to do is push a recovery over to your phone. Now go to the TWRP thread and download the image file and follow the instructions given to you to flash the recovery. I fear if following these simple directions are too much for you maybe you should simply leave your phone alone before the next step is you calling Google with an issue or having to buy another phone...
Sorry but thats my honest opinion....
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
the lemming said:
This process is an absolute nightmare.
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
Reading your posts, I understand your frustration. Here are my suggestions, 1) step away from your PC for a few minutes or an hour or get a cup of water, 2) put the phone aside, 3) read and re-read the information in Google Nexus 4 threads just to get the knowledge first and then start working on your phone. You will be doing fine. BTW, you should have a back up phone that you can use while working on your Nexus 4.
playya said:
Edit: Boot into bootloader and check to see if its says unlocked. If so then all thats left is flashing a recovery
Click to expand...
Click to collapse
Thank you for this useful bit of information.
the lemming said:
Thank you for this useful bit of information.
Click to expand...
Click to collapse
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Sent from my Nexus 4 using Tapatalk
---------- Post added at 02:51 PM ---------- Previous post was at 02:51 PM ----------
playya said:
You got it man I know but sometimes the truth hurts... You have been given all the information laid out for you in the posts above. If this is still too difficult for you your only other task is to actually have somebody do it for you this is nothing more than simply reading and taking your time. I tell you this with all sincerity I would rather see you stop now than later see another thread created by you saying possibly bricked
Take care
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
Sent from my Nexus 4 using Tapatalk
the lemming said:
And when I click the link I am blinded by options. This is a nightmare.
Could somebody please cut through all this hyperbole and just explain how I get ROOT?
I have been at this for 24 hours solid.
Click to expand...
Click to collapse
I trust that you have read the entire guide from that link you post. To get you see this clearly. Rooting is very easy. You just have to:
1. Install driver, download platform-tools (if you don't wanna download the entire android sdk) and SuperSU I trust that all the links are given in that guide.
2. Make sure you device is detected in adb. Copy SuperSU.zip into your device.
3. Unlock your device.
4. Push recovery. fastboot flash recovery recovery name.img
5. Reboot into recovery and flash SuperSu.zip
6. Reboot. Done.
Really..this is all it takes to perform a simple rooting. But if you're not the one who likes to read..and try to understand the steps. I suggest you not to mess with your device. You are more likely to brick it than make it better. The truth hurts but it is for your own good. Unless you prove me wrong. Then you are awesome instead
Sent from my Nexus 4 using xda premium
I recently received Acer Iconia A500 with stock 4.0.3 ROM (unrooted). I'd like to have root, flash recovery (prefer TWRP-like recoveries) and custom ROM (OmniROM 5.1.1 to get apps like MS Office/Word which 4.0.3 does not support). I've done a lot of background research on this matter but I'm really lost. There seem to be so many different methods of achieving this and none of them are written so that an unexperienced person (and I flash recoveries and custom ROMs many times a week to my Samsung phones) could completely understand what they do. There seem to be other problems as well such as dead links to installation files or executables that are problematic in Win8/10 environments (giving errors like 'install .NET 2.0 framework').
So here's what I currently understand. I get that I first need to root the A500 and that many rooting methods also unlock the bootloader (those are not familiar to me) and add an older recovery which then can be used to flash a newer recovery (with which I can flash ROM and GAPPS zips). I'vet got my ACER CPUID (used ES Explorer app to find it) and my SBK. I've copied zips and MD5s of OmniROM 5.1.1 V11 ROM, its GAPPS and TWRP based recovery REV2.0 beta4 to a MicroSD card which is inside the A500. I've got USB Debugging (and unknown sources) on.
Could someone please give me a good step-by-step guide with working links which describes how can I get from the current state of A500 (stock 4.0.3, unrooted, factory reset made) to the point where I can start flashing zips of recoveries and ROMs (which I know how to do)? I realize that this is an older device but for someone who has spent many hours within the last few days browsing XDA, Tegraforums and other places for information, there seem to be many A500-owners who still in 2015 are doing their first rooting and flashing experiments.
Please help!
I am in the same boat, totally overwhelmed by the information in many different places. My A500 is on 4.0.3 also.
So if someone would help US....I'd really appreciate it.
rampart51 said:
I am in the same boat, totally overwhelmed by the information in many different places. My A500 is on 4.0.3 also.
So if someone would help US....I'd really appreciate it.
Click to expand...
Click to collapse
you folks are all TEGRA OWNERS right? You should definitely check there instead...
Sent from my SM-G900V using Tapatalk
You can follow this which i wrote in other forum:
For basic step, follow if you are coming from stock. Make sure you flash all as mentioned in below forum
http://forum.tegraowners.com/viewtopic.php?f=9&t=363
In that forum, step2,
you can use Touchrecovery mentioned there or from: http://forum.tegraowners.com/viewtopic.php?f=8&t=1490
Also, for latest ROM, use the rom from first post of this forum.
Make sure you have Root access on tab, as well as you check MD5 sum for all file you flush it on the source from where you flush it. Usually, you put your files on microSD so check MD5 sum on MicroSD file.. (if you don't know how to, google it)
Basically, it is boiling down to below steps:
1. you need to root your device.
2. go to your existing recovery and install TWRP recovery. (http://forum.tegraowners.com/viewtopic.php?f=8&t=1490)
3. Once you install, go back to new recovery
4. tap on Partition Format
5. Tap on Storage. (Screen has only one big button)
6. Select Data from left side.
7. Select f2fs from right side.
This will format all your existing data. You will lose everything that you have.
8. Do same for Cache.
9. Reboot back in recovery to make sure that both partitions are formatted as intended.
10. Go back to main menu in recovery
11. Install ROM
12. Install GAAP.
13. Reboot.
14. Thank Thor.
Click to expand...
Click to collapse
I managed to get a Vista laptop so I've been able to get pass the compatibility issues with my Win10 PCs. However, I'm still a little unsure what to do. Could someone please clarify this for me? Can I use the quoted guide to get my A500 4.0.3 unrooted tablet rooted and with a recovery I can use to flash TouchRecovery, OmniROM and GAPPS zips? More specifically, does Step 1 work with 4.0.3 unrooted:
I wanted to write a consolidated tutorial for people on the latest/unrooted 3.2.1 OTA and how to flash it to rooted Jelly Bean ROM. If you follow step 1, it actually installs an old version of Touch Recovery for you, so you do not need to bother with Acer Recovery Installer. All links are derived from the FAQ stickied thread.
1. First you need to obtain root. Follow this guide to install a rooted 3.2.1 image.
[tab=30]All data will be lost. The 10 step guide is included as a PDF in the download:
[tab=30] http://forum.xda-developers.com/showthread.php?t=1307539
[tab=30]Confirm you have the Superuser app installed once completed.
Click to expand...
Click to collapse
I also found this piece of information from XDA:
Its an old thread used to upgrade you to rooted 3.2.1 -
It can also be used to downgrade/rollback/reset partition table - from ICS BUT there's a slight difference in the steps you need to take to do that...and alot of folks have come to grief here - so for the downgrade -
after running the "test.cmd" which checks the right drivers are installed correctly - run dotnetdetector.exe - follow the instructions UNTIL
You see a window asking you to connect your usb cable and that the EUU will check you "image versions" If you are downgrading DO NOT connect your cable!!!
This will "force" the "cannot detect your Iconia" window and then give instructions to put your tab into "manual apx mode" - once you have done that you can connect your cable - enter your cpuid - then you'll see the green status bar and the "update" will begin - it should take no longer than 10 minutes -
Click to expand...
Click to collapse
So which is it? Do I follow the 3.2.1 OTA method as is or do I take into consideration the alternative step to downgrade? Or does the method even work for A500 4.0.3 unrooted?
I can't seem to figure out how to downgrade back to a stock ROM after installing this:
lineage-14.1-20170331-UNOFFICIAL-trltetmo.zip (can't post link yet)
I believe it's the Nougat 7.1.1
I want to downgrade to 6.0.1 or 5.1.1
One message I see is "Recovery is not Seandroid Enforcing". Seems like all fixes suggest reinstalling stock ROM, which I'm trying to do, but can't.
Phone is a Samsung Note 4 SM-N910W8 (Rogers)
What's your steps to downgrade to 6.0.1? Did you download Rogers ROM and ODIN it(google is your best friend)?
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
If ODIN starts and stops immediately, you have a different problem. Did you install the Samsung Android USB driver properly. Anyway, you have a software issue, fix it first. I suggest you watch a few related video on youtube.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
Currently no response.
In the freezer... I'm waiting.
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
SUREFACE said:
It Sounds that You have a "FULL BRICK" !
The Only way, that REALY can Help is a "USB-JIG".
And Hope, that this One Brings Your Device back in Download-Mode!
You can Build Your Own One, see here : https://forum.xda-developers.com/galaxy-s2/help/guide-how-to-make-usb-jig-reset-binary-t1604707
Or Buy One! See Here: https://www.amazon.de/Download-Repair-Stecker-Samsung-Galaxy/dp/B004VN5ZYS
And You need a REPAIR ROM ! Take A Look here for Your Variant : https://mega.nz/#F!Ax0gxSzZ!Qq_eJWX678bQHBhn7BHNDQ
Hope that this will Work!
Click to expand...
Click to collapse
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Is your phone booting up and functioning? If it is, why are you talking about debrick? I'm assuming that you're "new" to all this. I suggest you read up(especially the stickies) and be comfortable before you go further.
ziggy1971 said:
- I have TWRP-3.1.0 installed
- Used Odin3 3.10.7, Odin3 3.10.6, and Odin3 3.12.3
- Downloaded stock ROM from here: https://www.sammobile.com/firmwares/galaxy-note4/SM-N910W8/
- Followed this tutorial: http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
I get virtually nowhere, Odin3 starts and almost immediately stops.
FYI: I had just posted here:
https://forum.xda-developers.com/note-4/snapdragon-dev/rom-lineageos-14-1-t3536401
just before I got a response here. My apologies, I'll link to the other post...
Click to expand...
Click to collapse
ziggy1971 said:
Not sure which I should follow first:
Debrick here: https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
or
The following from https://forum.xda-developers.com/showpost.php?p=72338162&postcount=2622
Since yesterday I did the following:
- reset my system with a backup image (Bare Metal Restore with True Image) I only have some basic software installed.
- downloaded and installed SAMSUNG_USB_Driver_for_Mobile_Phones_1.5.63.0
Click to expand...
Click to collapse
No, it doesn't boot up at all now.
I know I initially said "I" installed the custom ROM, I didn't, I bought it that way. The previous owner won't do anything to help. The only thing he did was provide a link to the ROM he had installed, nothing more, not even the tutorial related to it, I found that on my own (wait, he's made it more than clear how incompetent/ignorant I am as a person).
I've been searching and reading for 3 days straight now. Getting to the point again where I accept defeat, assume the money lost.
Moving on... I've rooted other phones before without issues.
I follow a tutorial on how to downgrade to a stock ROM.
http://www.androidrootz.com/2014/11/how-to-unrootunbrick-galaxy-note-4.html
Odin stops with various errors.
I could still boot device into TWRP-3.1.0
Reflashed LineageOS 14.1 ROM from SD to get it working again.
LineageOS 14.1 ROM would boot up, run for almost a minute and a half and shut down.
Pull battery, reboot into LineageOS 14.1 ROM, same thing.
Run Odin, connect device to computer, try to flash stock ROM, error again (different one). Somehow, it says "There is no PIT partition"
I followed this tutorial: https://forum.xda-developers.com/no...te-4-pit-files-repartiton-f-g-c-t-w8-t3282641
Odin says FAIL.
Now, it does NOTHING.
I follow this tutorial: Debrick here: https://forum.xda-developers.com/not...k-img-t3488114
Yes, the whole freezer thing overnight.
I have the latest USB drivers installed.
When I connected to the PC, an error popped up saying "...drivers not installed properly..." so I let Windows Update install the correct drivers.
I can connect to the PC now, press the power button for more than 10 seconds, eventually a popup message says "USB Device Not Recognized by Windows"
I've tried the following stock ROMs, 4.4.4, 5.1.1. I finally managed to download 6.0.1, but haven't been able to try it.
All I can say is that if you can boot into TWRP(I assumed you install the N910T version), then your phone is not bricked. All these "debricking" you're doing is potentially harming than fixing.
You assume the risk, when you buy 2nd hand. But based on what you're saying, it sounds like it may also have hardware issues(I don't think software will fix). Was it working when you got it? If you can return it, I suggest you do.
Another pc or windows version may work
A more trustworthy guide on using ODIN:
http://forums.androidcentral.com/am...w-flash-stock-rom-via-odin-new-interface.html
mnopy said:
Another pc or windows version may work
Click to expand...
Click to collapse
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
ziggy1971 said:
I will try with another PC, two batteries, different USB cables, different versions of the USB drivers, and so on.
Anything I missed?
Click to expand...
Click to collapse
QualcommDrv
this is the Qualcomm Drivers(x86 and x64, choose your system's version and install) .
Without that your pc will not recognize your phone.
Uninstall everything related to samsung from your pc.
Kies, smart link, usb drivers. Use revo-unistaller for this to be sure nothing have left behind.
Go to control panel>system>device manager and remove anything that is related to your phone . If prompt delete drivers associated with that, say yes. Reboot your pc
Have saved QualcommDrv, samsung usb drivers and Odin. These are the tools you are going to need and must have.
after uninstall everything, unzip and install QualcommDrv.
Take off your battery, press power buton for 10 sec . Connect the phone to pc (without battery)
QualcommDrv will install the correct drivers for your phone. After that If in devices and printers it is recognized as Qualcomm 8084 .... its ok to proceed . if not , check again drivers and their installation
If windows says device drivers are not correctly installed and prompt to download and install, stop and cancel it.
IT will replace the QualcommDrv and you will not be able to see your phone correctly.
You need to keep QualcommDrv installed. When this is done and you are sure its correct and working, unplug your phone and install Samsung usb drivers. Reboot pc
unzip odin in desktop (or where ever its easy to access).
with your phone freezed and battery charged try to go to download mode. If succeed, connect to pc and with odin try to flash stock rom. If not ......
https://forum.xda-developers.com/note-4/snapdragon-dev/note-4-debrick-img-t3488114
That what you need to have correct and working in order to START. THIS IS ONLY THE FIRST STEP
YOU HAVE TO UNDERSTAND
this is a hardware failure of the motherboard and will never will be completely fixed. These steps will only help you resurrect your phone and maybe give you the chance to be able to use it again.
It has nothing to do with software that failed to install. It was just the result and not the real problem, which is a diffect motherboard like thousand others. Sadly this is a common problem with Note 4 that happened to many users.
I have the same problem and I also bought it second hand knowing its problematic but not how much.
After that I realized the problem and the solutions to it. Every one of us is having a slightly different behavior of the phone.
I, for example cannt use the phone without the ext sdcard with unbrick image in it. When I take it out phone, will not start, reboot , do nothing.With the card in it its working almost perfect.
So have patience and read and search to know what you are dealing with.
Good luck
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
ziggy1971 said:
I managed to revive the Note 4 using a stock ROM.
Now, I have more questions like;
- Is this a problem on ALL models of the Note 4 or is it limited to a certain model?
Click to expand...
Click to collapse
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
dicksteele said:
I don't believe you truly downgraded. I'm assuming you were on a 6.0.1 bootloader running a compiled 7.1.1 ROM. It probably hosed some partitions, and other things. Flashing the Stock ROM normalized it.
Most of time flashing a stock touchwiz rom will fix the "damage" that results in flashing a CM ROM.
Click to expand...
Click to collapse
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
ziggy1971 said:
I have no idea what kernel, bootloader, etc. were/are used in the LineageOS ROM.
What I'd like to do is take a stock ROM and remove the unnecessary BLOATWARE and keep all the rest as it is.
Personal blurb: Why can't OS makers simply do that, make an OS!!! Windows, Android, it really doesn't matter, they're all the same.
Click to expand...
Click to collapse
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
dicksteele said:
There is nothing stopping you from doing that but you.
Don't waste your breath saying I don't know how. There are TONS of guides on XDA.
That's exactly how I started learning. With that desire.
And here's what was most likely on it
https://forum.xda-developers.com/note-4/orig-development/rom-cyanogenmod-14-1-t3506613
Click to expand...
Click to collapse
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
ziggy1971 said:
"I don't know how" generally isn't in my vocabulary. It's more like, where do I start, what do I need, where's a good tutorial explaining the what, how, and why of doing things.
Do I need to go all the way into the Java source code or are there other ways of removing some of the built-in apps?
Any tutorial/info suggestions are more than welcome. I'm not that familiar with the lingo of ROM customizing, so my searches are pretty much limited to that; "Android ROM customizing" is about the jist of it right now.
Click to expand...
Click to collapse
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
logosA said:
take a look here,
https://forum.xda-developers.com/note-4/general/guide-build-lineageos-14-1-trltexx-t3567885
here:
https://forum.xda-developers.com/chef-central/android/guide-android-rom-development-t2814763
and here:
https://forum.xda-developers.com/showthread.php?t=2467004
and maybe here:
https://forum.xda-developers.com/chef-central/android/guide-how-to-build-rom-google-cloud-t3360430
I cannt built but I can test, so go for it and tell us if we can help in the next step
Click to expand...
Click to collapse
Those are good.
Some more are here
https://forum.xda-developers.com/general/xda-university
https://forum.xda-developers.com/chef-central/android
https://forum.xda-developers.com/showthread.php?t=1272270
https://forum.xda-developers.com/showthread.php?t=2069130
https://forum.xda-developers.com/showpost.php?p=5626301&postcount=4
https://forum.xda-developers.com/showthread.php?t=1590192
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
There are essentially two ways to do what you want.
Use the unpack tool above, extract the system.img from a Stock ROM
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
I get my stock ROMs from here
http://updato.com/firmware-archive-select-model?q=n910c&rpp=15&order=date&dir=desc
Remove the bloatware or apps you don't want.
Use the app same app that you used to extract the system.img to repack it.
Use the https://forum.xda-developers.com/chef-central/android/tool-afaneh-tar-kitchen-t3603649
to build a tar and flash with ODIN.
Second option use a kitchen. I'm testing the one below today to see if it works.
https://forum.xda-developers.com/ch...0-0-deluxe-kitchen-graphic-interface-t3579100
SuperR works great. But you need a Linux environment to run it.
I use virtualbox on my Win10 machine. I use premade images from here
http://www.osboxes.org/virtualbox-images/
Personally I use the Ultimate Edition.
Or use cygwin. I gave you plenty of links to learn how that works. It's a pain that's why I use virtualbox.
Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.
Brotinger said:
Dear and knowledgeable readers!
Being a longtime lurker, your tireless work and dedication to the community have enabled me to unlock and root many different android devices over the years and I am deeply grateful this place exists.
Right now, I plan on adding the recently released
Lenovo Smart Tab M10 FHD Plus 2nd Gen [ZA5T0302SE / TB-X606F, I believe]
in the WLAN/4GB/64GB variant to my collection. Having grown accustomed to the luxury of root access, I was wondering if anyone already had some experience with rooting the device and would be willing to share his / her knowledge with me.
Especially, I was wondering if this guide for the TB-X605F, which I have successfully used in the past for my older model, would (in principle) be applicable, as long as I could obtain the corresponding firmware for the newer one, which might be available here (as soon as GD wills it).
Any advice / support would be highly appreciated!
[Sidenote]: To my best ability, I wasn’t able to find an existing thread on the topic of rooting the device in question and I hope to have chosen the right forum to post it in (or if the general Q&A would have been the better fit?). If not, dear mods, please be lenient with me and simply move the thread to the proper subforum.
Click to expand...
Click to collapse
If you download the lmsa tool, plug in the tablet and go to recovery it will download the full stock firmware. Then you can find it c/program data/LMSA/downloads.
I did that then downloads magisk manager. Extract the boot.img from firmware and put in storage of tablet. Then used magisk manager and patch the boot.img it will tell where it is stored. Extract from tablet and put it in same folder as adb/fast boot. Then put tablet in fastboot and fastboot flash boot magisk-patched.img. then fastboot reboot. The will be rooted with magisk
I forgot. You must unlock bootloader to do this.
Dear 11mackey11,
thank you so very much for caring enough to share your knowledge with me!
So the guide I mentioned earlier is pretty much applicable for the newer model as well? What a relief!
I am also grateful for the hint on how to obtain the stock firmware. For all the dirty things I did to my devices in the past, it never became necessary to put the LMS-Assistant to use, but I will gladly change that now.
As soon as my device arrives, I will try to root it as you suggested and will report back how I fared.
Again, many thanks!
It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!
Brotinger said:
It took me some time to finally get to it … delivery problems with the device … busy work schedule …
… anyhow, I now took the leap and am happy to report that, thanks to your advice, I was able to add another rooted device to my ever-growing collection. “Worked like a charm”, as they use to say.
To repeat myself, I am very grateful for you taking the time to respond to my question and reassuring me that this was the path to follow.
Honestly, thanks!
Click to expand...
Click to collapse
Hi. I just purchased the same tablet. I would appreciate it if you could write up a guide on this forum. It would be a help for everyone.
I'm not even sure how you unlock the bootloader on this thing!
Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).
Tutorial
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I want to apply it to my device, have you tried this method?
Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.
b4nd0ler0 said:
Yes, tried and failed miserably. The tablet is not correctly rooted as reported by Root Checker. The su binary is there and shows it's Magisk but no root proper.
Will try again and report back when done.
Click to expand...
Click to collapse
thanks, I'm waiting for news from you. The tablet is sold very much in our country. like this in the world. I'm sure the developers will do something about this device.
b4nd0ler0 said:
I found this tutorial specific to the X606F https://forum.frandroid.com/topic/2...u-lenovo-tab-m10-fhd-plus-tb-x606f-sans-twrp/ alas in French but Google translate makes a decent job out of it
Click to expand...
Click to collapse
I rooted my device with this method
this method doesn't work
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
This method is working!
Use the Official Lenovo website to access your original "rom" file and get the "boot.img" file.
Program: Lenovo Rescue And Smart Assistant https://lnv.gy/3d8FHLi
For an article on how to download the Rom file via the program, see here. (Step 3)
https://bit.ly/2yE1nQf
Good Luck!
adroid_user said:
Hello dear Android users...
I've got the 3/64GB version of this device (ZA5T0300US) and this method of rooting did not work for me. When I check root in Magisk Manager, it says ctsProfile:false & basicIntegrity:true, so root doesn't work. I tried multiple times and every time had this same result. My ROM version is TB_X606F_USR_S100055_2001030016_V5.196_BMP_ROW (extracted ROM folder name). Are you sure your root actually 100% worked? What is your ROM version?
Click to expand...
Click to collapse
You did not enable Magisk Hide
mingkee said:
You did not enable Magisk Hide
Click to expand...
Click to collapse
That was it! Thanks! You're smarter & more helpful than Google!!! ))
Hi.
After i root the tablet, i tried to delete youtube and gdrive. Then i restart the tablet but it stuck in fastboot mode. Not booting.
i couldn't install stock rom. What i must do
I did this..
i patched the boot img from the lenovo program. and i like to shut down my devices when i dont use them and now i cant make it boot. im stuck in a bootloop and its says orange alert when i boot the device. i can only get into the fastboot menu. when i try to boot with vol + and power nothing happens and when i release it starts up again in a bootloop. i cant shut it down either. it just loops and loops. cant do the rescue thing with the program either.. anybody that knows how i can fix this?
I have an out of topic question regarding this tablet.
Can The Lenovo M10 Plus (2nd Gen) 10.3" TB-X606F Output Display via HDMI to TV ???
I tried using a powered USB-C to HDMI adapter to output/mirror the tablet to a TV, but it didn't work.
Brotinger said:
Hi and congratulations on your purchase! The TB-606F is a solid device in my book.
Although I have by now rooted more than a dozen android devices and guess I have at least somewhat of an idea of what I am doing, I am by far no pro on the issue. Basically, I consider myself more a “guide user” than a “guide creator”, still.
But as I have benefited from the kind- and helpfulness of this community many times before, I can’t leave this call for help unanswered.
The thing is, nonetheless, I would really like to refer anyone poised to root their TB-606F to the guide for the TB-605F which I linked to in my initial post. Rooting the TB-606F, in principle, demands the user to undertake the same steps as for rooting the TB-605F.
There are, from the top of my head, only two noticeable differences or variations from that guide which I discovered:
1) firmware
As I still haven’t found a reliable source to obtain the necessary stock firmware by download from the web, the advice of fellow user 11mackey11 comes in very handy who, in response to my initial post, pointed me to the LSMA to download the firmware from your very own device.
2) unlocking bootloader
At least with my device, the fastboot commands known to me to usually unlock the bootloader (as are “fastboot oem unlock-go”, “fastboot oem unlock” or “fastboot flashing unlock”) did not do the trick. I had to resort to the command line of “fastboot flashing unlock” to finally make some progress. This might be an outlier with me device, though, as 11mackey11 did not mention the issue.
Again, I will gladly provide any assistance I can offer, but as for writing up a guide, I would mostly carbon copy turboperson123’s guide for the TB-605F mentioned above anyhow and it does not seem right to take credit for his contributions.
But if you had any specific question, please don’t hesitate to ask and I will answer it to my best knowledge (which might not be much).
Click to expand...
Click to collapse
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.
unlock not possible
CMX939 said:
Hey, thanks for all this useful info. I'm a noob when it comes to rooting. I have hit an issue, that you guys could probably easily advice me. I have got up to where you enter "fastboot flashing unlock" it comes back with something like "waiting for any device". How do I get past this point? I have tried pressing volum up as I saw on a guide however no luck.
Click to expand...
Click to collapse
I have the same issue, "waiting for device" and adb dies.
I assume, the latest lenovo updates (Android 9) block unlocking.
The current! LMSA tool does not allow to restore an old separately downloaded firmware