Related
Having been a member on this forum for years I must admit it has been incredible the wealth of information I've gained from it. I've had all sorts of phones/pdas and I'ved used this site to help me get the most out of it and to help m "tame" the device and stop rubbish from the vendors being installed on there when I don't want it.
A couple of years ago I got an HTC Desire. Great phone although limited memory. I was happy with it. Didn't bother to root it or anything. I then got a Motorola Xoom. Didn't bother rooting that either. I got myself an HTC Sensation now. I decided one day that I was going to unlock/root the thing to see if I could do it.
Somehow, I think I managed it. I haven't really noticed a difference but then I haven't put a custom rom on it. On all my old Windows mobiles I always had a custom rom.
Now, going back to the Xoom. It's an original Xoom. I bought it in May 2011. It is running Android 3.2 after Motorola sent out an update. All is good.
However, I would like to have ICS on it. This is where my problems begin. I've tried following so many different how-to's on how to do this unyet none so far have worked. So, either I'm completely stupid or, the guides are not easy to follow or the process (that is always touted as easy) is not very easy.
So I am asking for help. Here is what I understand are the steps that I need to acheive.
1. I need to unlock the device
2. I need to install a recovery image
3. I need to install ICS
Questions: I *think* I have done 1. How do I check? After what I believe is a convoluted process, I have installed the Android SDK. I have the drivers for the device on the [Windows 7 64bit] PC and I can see it listed when I type adb devices.
Why do I need to unlock the device? What does the act of unlocking it do? When I followed this:
http://forum.xda-developers.com/showthread.php?t=1242241
I got to step 3. I typed in the first command:
adb reboot bootloader
After much faffing around I found out from another site I needed USB Debugging enabled. Nobody told me this. No, it isn't obvious that I need this.
The boot screen appeared and gave a message at the top and then I typed in:
fastboot oem unlock
I followed the instructions on the screen. I unlocked the device. It took a while. When it rebooted I found I had to set the device back up again as if it was the first time I'd used it. "Great!" I am thinking, I've lost everything. Thankfully I backed up what I wanted so I am not bothered. Slowly the apps appeared to come back after it synched with Google. I'm assuming stuff gets backed up somewhere.
I typed:
fastboot reboot
It rebooted.I typed:
adb reboot bootloader
It rebooted into the bootloader. Now here is where things started to go off track. I typed the next command:
fastboot flash recovery recovery-Tiamat-R4c-100611-1150-cwm.img
I get this:
unknown partition 'recovery-Tiamat-R4c-100611-1150-cwm.img'
error: cannot determine image filename for 'recovery-Tiamat-R4c-100611-1150-cwm.img'
So what now?
I cannot believe the process to unlock and flash a rom is so unbelievably convoluted. I've read dozens of walkthroughs, how-to's and forums and each one seems to be very similar unyet there is always something different on there to what I get on my screen or something doesn't happen quite the same way.
Here is what I am trying to acheive:
I have Android 3.2 on my Xoom and I would like it to be ICS.
We'll assume that I am completely stupid and need serious handholding to get to ICS. Is there anyone that can help with these seemingly simple steps?
One thing I keep reading is about the recovery image file. Is this related to Cyanogenmod? I am assuming as it is called a recovery image file it helps you get back when things go wrong.
Thanks and much love to the person that takes up the reigns and helps me out here.
Hi!
If you are rooted already that's pretty easy. But if not, try using LordAIOTool to root (yea it's mine and I think it's worth a try). After you are rooted flash a new recovery - download from development section - after, rename the recovery to recovery.img and then use the following commands on adb, fastboot and this recovery folder (simultaneously)
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot reboot
Then after keep clicking the vol- after 2s of your tablet appears on Motorola logo. Then keep cycling until appears Android Recovery then press vol+
You are on recovery now, just select install zip from sdcard...
Good luck
Sent from my MZ601 using XDA Premium HD app
If you wanted your xoom rom'd, then you could try wesamothman's guide: http://forum.xda-developers.com/showthread.php?t=1717402 It is great for beginners and the experienced alike.
This is for the wifi only xoom MZ604. There is another guide by him i believe for the MZ602
Do I need to flash a new rom to get root on my MZ604? What is the easiest way to just root the stock 4.0.4 firmware? I have no desire for a different rom. I just want to root it.
Hey there.
If you don't want to flash a custom ROM and only want to root it, try this:
1) unlock your bootloader.
2) thru ADB, flash a recovery image.
3) thru Recovery, flash superuser flashable zip: http://www.4shared.com/zip/g3yzbrIa/...?cau2=403tNull
I ran the first couple of steps to unlocking. That is as far as I have got. As I said, I have tried so many of these walkthroughs and not one of them has all the steps. They all make an assumption somewhere along the line.
For example: xxlordxx replied with:
"If you are rooted already that's pretty easy".
I'm not, that is the problem.
Again:
1. adb reboot bootloader
2. fastboot flash recovery recovery.img <---- This didn't work and gave me the error I pointed out earlier and that is where it all stopped. Noone explains what to do when it goes wrong.
Anything passed this stage is irrelevant until I can sort out the problem above.
yosterwp, you mentioned wesamothmans guide. I will try that one as it looks a bit more "dummies guide-like" and it is for my exact device which is the MZ604 wifi only. I hadn't seen this one as it was only posted a couple of days ago
Just so I know, can someone anser these questions? I'm sure they're very simple but I don't know.
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
2. Is unlocking the same as setting s-off?
3. If not, what is the difference?
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
5. What is Cyanogenmod and do I need it or is this another custom rom?
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Thanks for everything so far. I will let you know how I get on with wesamothmans guide.
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
wesamothman said:
Hi Snert.
Answering your queries:
1. Do I need to unlock the Xoom to put ICS or a custom rom on it?
yes.
2. Is unlocking the same as setting s-off?
I don't really understand what you mean by s-off... but unlocking is this: you unlock the bootloader that is considered as a security checkpoint of your device. It is locked by default. when it is unlocked, you can then install recovery image passing thru this checkpoint (allowed). without bootloader being unlocked, no rooting can be done. this is the very first step.
3. If not, what is the difference?
same as above
4. I assume the recovery img file is for recovering if things go wrong. Is that correct? Why isn't a recovery app on there for when OTA releases get pushed through? What else does the recovery do for me?
Recovery explanation details is here: http://www.androidcentral.com/what-recovery-android-z
5. What is Cyanogenmod and do I need it or is this another custom rom?
It is a different ROM based Firmware...
6. There are so many custom roms out there. Everyone says to choose the one that is suited to me but I don't know which ones are suited to me. Does anyone know of a list of the custom ones that are around and why I'd choose one above the other? (I am assuming this is a long shot
Go for the best custom ROM for your MZ604. It is from Team EOS.
Hope I answered your questions
Click to expand...
Click to collapse
You did
Much love!
I bootloader on my moto g XT1031 BOOST MOBILE
i accidently deleted something wrong obviously when trying to delete bloatware
i have been trying to access a link for the STOCK settings... Unfortunately my backups were erased/never saved/non existent.
I am completely frustrated and would really appreciate someones help.
I am currently able to use the mobile device but with no wifi, no data connection, no apps on the phone. I am unable to do anything data/wireless on my handset.
Here is My situation as is....
I have windows computer, i have power cord for phone ( USB?) i can not access the ever popular link that says is currently unavailable, and thats it. PLEASE take me through every step assuming that i know absolutely nothing because i DO NOT. I cant afford a new phone. I need all WORKING links and to be taken through every single little step. I am on day two of trying to do this myself and have given up. Please help me before i lose my mind.
p.s I do have internet acces via my Windows computer.
Assuming you have a custom recovery already installed, simply download a custom ROM via PC, drag and drop it on to the SDcard of your phone where you can easily find it via recovery.. Boot to custom recovery, do a wipe and flash the ROM./Gapps. There are several basically stock ROMs with slight tweaks in the Dev section. There also may be stock flashables. This will at least get your phone back operational until you can do the research in to recovering stock firmware.
There are many helpful people here, but for the most part you are encouraged to do your research and know how to recover from situations such as this without asking questions. All the info can be found on these forums with a few mins of research. I don't mean to come off as rude... But if you're dabbling into the world of BL unlock, rooting,flashing, modding, things happen and you will need to know your way around your device.
mbj731 said:
Assuming you have a custom recovery already installed, simply download a custom ROM via PC, drag and drop it on to the SDcard of your phone where you can easily find it via recovery.. Boot to custom recovery, do a wipe and flash the ROM./Gapps. There are several basically stock ROMs with slight tweaks in the Dev section. There also may be stock flashables. This will at least get your phone back operational until you can do the research in to recovering stock firmware.
There are many helpful people here, but for the most part you are encouraged to do your research and know how to recover from situations such as this without asking questions. All the info can be found on these forums with a few mins of research. I don't mean to come off as rude... But if you're dabbling into the world of BL unlock, rooting,flashing, modding, things happen and you will need to know your way around your device.
Click to expand...
Click to collapse
Like i said i have been trying to accomplish this for two days now. I really feel like there is nothing i can do. I just simply dont understand what im doing given my current level of knowledge pertaining to the aforementioned query. I do not think you are coming off as rude and i appreciate you taking the time to share you imput with me. Its just that when you say "flashables" and "Boot to custom recovery" i become confused as to what that means. sigh
as i have previously mention my level of patience has grown thin which in turn has raised my level of frustration. If you wouldnt mind taking the time to point me in the right direction it would very much be appreciated.
thank you very much
-DR
1.) Follow this guide to unlock bootloader/flash a custom recovery via PC: http://forum.xda-developers.com/showthread.php?t=2684234
2.) Here is a link to obtain a STOCK flashable zip for the Boost Mobile XT1031, along with a "optimized" version which has already been debloated. Whichever you choose. Download the ROM and move it to your phones SD. Boot into the custom recovery (above guide tells how). Once in recovery, do a wipe or factory reset. Install/flash the .zip you put on your SD:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
Hopefully this helps and you can also learn along the way. All of the information you need is on this forum. It can all be confusing and frustrating at first, but once you get the hang of it there's really not much to it.
There may be a better way of going about this, but these steps will get you back to stock in the easiest way I can think of with little to no knowledge of customizations. Once you get more familiar with everything and do your research on whatever result you're trying to obtain, it will get easier and easier to understand and do.
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
luan96 said:
Hello guys. I just bought a used Samsung Galaxy J5 (SM-J500FN) with android version 5.1.1. The previous owner told me that it is rooted. Nothing seems weird with the phone other than when i try to factory reset it it takes me to a "bios" kind window where i have to manually choose to delete all data (hard delete i think its called), that and when i normally turn on the phone, at the top left corner it says "set warranty bit kernel". I was just wondering how do i go about installing custom roms since its already rooted, and can i unblock the default carriers (T-mobile) block for other sim cards. When asked how he rooted it (what method was he using) he said he just used Odin. I dont know much about rooting so, whatever you can tell me as to the handling of the phone would be amazing. Any other guides to installing some custom roms and making the phone easier and faster ( i only want functionality, don't care much about the UI) would be greatly appreciated. Thanks in advance.
Click to expand...
Click to collapse
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
That's what I love about Samsung, as long as you have your ducks in a row, the files and tools are extremely easy to use, a 4 year old could do it.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Thank you, ill be sure to check them out. Although, i would like to do the entire process from the beginning (root it again myself since i have no idea what the previous owner has done) and then try to install custom roms and other cool features rooting offers. I read that the KNOX security on samsung phones can pose some problems, any thoughts on that ?
Thank you again for your response.
ShaDisNX255 said:
For starters, I'd head over the J5 forum
Galaxy J5 Forums
Or here's a great post that includes a lot of stuff to get started on reading:
https://forum.xda-developers.com/galaxy-j5/how-to/galaxy-j5-root-twrp-roms-news-tips-t3620892
But the basics are: To flash a custom ROM, research what a custom recovery is, how to flash a custom recovery to your phone model and after that, flashing a custom ROM is as easy as loading the .zip file to your SD card and selecting it in the custom recovery.
I'd also research on how to flash to stock, as this is a life-saver in case you accidentally do something wrong. Pretty much you need to know how to flash via Odin (yes, learning how to use Odin is important to us Samsung users).
Don't worry though, it's not that big of a pain, Odin is pretty easy to learn
Click to expand...
Click to collapse
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
I've got no experience with Linux, sorry. SuperSU disables knox so there's nothing to worry about.
luan96 said:
Also, i use Linux so i hear the alternative to Odin is Heimdall, anyone have any experience with it, or should i just do it on a Windows PC?
Click to expand...
Click to collapse
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Droidriven said:
If you're a Linux user and you have knowledge of using terminal commands then you should have no trouble setting up Hiemdall. Getting full USB functionality set up for the device in Hiemdall can be a pain if you aren't familiar with that kind of thing.
But, having a Windows PC will make a lot of things very simplified for you. A Windows/Linux dual boot system would be very handy to you if you can set that up. Then you could also use Kies/SmartSwitch if it ever comes to a point that you need it.
There are some handy rarely used instances with Linux when it comes to Samsung. They have no fastboot like other devices so only adb is usable. I think they primarily centered around Windows being the preferred OS to interact with their devices.
Click to expand...
Click to collapse
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
luan96 said:
Thank you for the info. I already have a dual boot on my pc with windows. I am an experienced Linux user and setting up Hiemdall should not pose a problem, but i opted to go for Windows since as you said makes things simpler.
Still looking for guides and tutorials on how exactly the root process goes. Doing research, so i guess its going to be a late night. If you have any links or pages you can guide me to for my Samsung J5 it would be amazing. Right now am looking around this forum and wherever the links lead me.
Thank you again.
Click to expand...
Click to collapse
First, just to make sure that you are not walking blindly into some potential traps.
1) download the root checker app from Playstore, use it to verify whether the device is actually rooted.
2) power the device off, wait 5 seconds, hold volume up+home+power, when it boots past the logo, let go. It should boot to recovery, tell me what you see. Does it say TWRP with grey buttons on a black screen? Or does it have an android lying on his back and have options listed?
3) verify whether or not the bootloader is unlocked or not on your specific device model number with your specific build number/android version, if it's locked it will create problems if you try to flash custom recovery. Though you can flash CF autoroot with locked bootloader.
Then I'll help find what you need to do what you are looking to do. It may be simpler than you think.
If he in fact used Odin and the device is rooted, he did one of three things.
1) flashed custom recovery(TWRP) via Odin then flashed SuperSU.zip to root, not possible with locked bootloader.
2) flashed CF auto root via Odin, potentially leaving stock recovery if your bootloader is locked.
3) flashed a pre-rooted stock firmware via Odin, not likely though.
The first 2 being more likely than the last one, the second one being the most likely if your bootloader is locked.
Edit: @luan96, edited for more information.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
-Hope- said:
I would recommend using the command line to flash the twrp instead of the GUI if you want a simple process in linux
Run a terminal as a superuser (sudo)
heimdall flash –RECOVERY filename.img
Do step 1 and 3 you gave before before doing this
Or just flash the twrp image using Odin
J500FN twrp
https://dl.twrp.me/j5nltexx/
Click to expand...
Click to collapse
I'm going to use Odin for this. Since I'm quite new to the rooting community I dont want to mess things up on the first try. I'd rather get comfortable with some standard stuff before I proceed to try different variations. Thank you for your input. Though I would still like to know if I should use cm auto root or do a manual root. The difference is not quite clear to me yet. Again, thank you for your input, it is appreciated.
luan96 said:
@Droidriven Thank you for the info. After a rough night of research i realized what i need to do. According to root checker, my phone is not rooted, and the recovery seems to be stock. This is very weird, since the phone is obviously not just the stock version that came from T Mobile. Im guessing its probably a badly done root or one that was removed. Anyways, this is how i am planing to proceed:
1. Turn on OEM Unlocking and USB Debugging from developer versions
2. Download CM Autoroot for my specific phone ( i do not know what is the difference between "normal" root and autoroot, but autoroot seems to be simpler and offers the same thing. Please correct me if i am wrong, i would love to know how to do a manual root as well if it has more benefits).
3. Volume down+home+power to get to the download screen
4. Launch Odin that comes with the autoroot package
5. Plug my phone into the USB and wait for Odin to add it.
6. Select the autoroot md5 file from the folder and begin the flashing process
7. Hope for the best and that my phone is still functional when it auto reboots.
After this i should check with Root Checker weather its properly installed or not. If it is, and i see the SuperSU application i continue to installing the custom recovery ( through some research i found out that TWRP is the best choice for me). Installing the custom recovery should be as easy as auto rooting the device. I should download the files from an official website, and flash them using the same process i did for AutoRoot.
After that its mod heaven. With my understanding so far, TWRP lets me install custom roms, and other things i might need.
This is what i plan on doing as soon as im done with a little more research. If anyone has any tips, corrections or general information on what to expect or do please share.
Many thanks to every contributor on this thread.
Click to expand...
Click to collapse
Flashing CF autoroot will simplify rooting, again, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as your bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
Flashing CF autoroot will simplify rooting, afain, just make sure you have the correct autoroot for your specific model number and firmware, flashing the wrong one can softbrick or hardbrick your device, this would require flashing stock firmware via Odin to repair if softbricked and more serious methods to restore if hardbricked. There isn't much difference in effect with the different rooting methods. They all get the job done about equally.
Just make sure that you verify that your bootloader is in fact unlocked BEFORE you flash TWRP. As stated earlier, if it is locked, it will certainly cause issues and you'll have to restore stock recovery and/or stock firmware.
As long as you're bootloader is unlocked then your outlined plan should be good to go.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
luan96 said:
Well, looks like i messed up somehow. I was fiddling around the recovery mode and Odin mode. Those were the only two screens i could view besides normal booting, so i was looking for any info.
Recovery Mode https://ibb.co/hotYZ5
Odin mode 1 https://ibb.co/nFfVE5
Once on the recovery mode, i selected "reboot to bootloader" hoping to find info if its locked or not. I got redirected to this screen
Odin Mode 2 https://ibb.co/kqhtZ5
And then i did what i think is the dumbest thing this year....i removed the batery and now when i try to turn on my phone -
Blocked https://ibb.co/kkOd1k
Please tell me i did not brick my phone without even trying to root it first. My understanding is that i accidentally wiped the current OS (softbrick?) and now i have to flash a new one and then continue with what i had planned. Or is this a small problem that can be fixed easier? Or a more serious one ? Good news tho maybe, i think that the bootloader is unlocked ?
Thank you @Droidriven for your info so far, you have been extremely helpful.
*EDIT* - Pictures didnt link correctly.
Click to expand...
Click to collapse
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Droidriven said:
It looks to me like they attempted to root the device but didn't do it correctly.
FRP can be a pain to deal with. Some can be bypassed easily, those that have trouble bypassing must sign in with the original owner's original Gmail and password used to activate the device.
The method of bypassing FRP varies from device to device.
Did you factory reset in recovery? If so, that's why you FRP blocked you.
If you have stock recovery then you should not have been able to wipe out the OS using stock recovery, typically, only custom recovery can do that, unless you did something accidentally that somehow corrupted/wiped your OS.
If the OS is gone, you'll have to flash your stock firmware via Odin and start over from the beginning.
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
Click to expand...
Click to collapse
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
luan96 said:
Thank you. At least its not just a paperweight. I'm installing new software on it with Kiesk 3 right now. Hope that works so i can do the rooting and TWRP install soon. I pressed "reboot to bootlader" to try and find out if its locked or not, but then it got me in download mode (without having to press up volume to contionue). After i turned off my phone by removing the battery, the OS was gone.
Click to expand...
Click to collapse
Did you get this restored with Kies?
Droidriven said:
Did you get this restored with Kies?
Click to expand...
Click to collapse
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
luan96 said:
Yes, i did. Worked like a charm, and even got the new 6.0.1 android on it. Also installed TWRP, and just finished installing Xposed Framework, now waiting for it to boot up ( i hear it takes some time). Seems all well so far. If any problems pop out ill be sure to post about it. Also thinking about making a new thread just to help newbies like me who really just want to remove some bloatware, and install some nice modules and not heavily mod the phone. You have been very helpful during this process. Many thanks to you ^-^ .
Click to expand...
Click to collapse
If you have issues with Xposed causing a bootloop, you can flash the Xposed uninstaller zip in TWRP to remove it, then troubleshoot why it bootlooped and try again.
Are you using the Touch wiz marshmallow Xposed framework?
I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
I'm fed up with people on this forum. I keep trying to engage people in a discussion, a conversation to explain some things to me and No one seems willing. It's like there are No Rooting gurus that can answer my simple questions. On a forum full of Android developers, I'm very disappointed, I thought i'd get tons of help. If you read this, Please consider staying to have a discussion/conversation with me.
Preface to The Discussion:
I have used both Android and Linux in the past, I know what Super User is, I use it in Zorin 12 Linux and own a rooted (kingroot) android tablet. I am trying to get information on rooting my Figo Atrium phone by trying to understand Rooting better in general. perhaps this discussion will make since to you and together you can help me find a way to root my phone - But I Must have a back and forth or I'll never understand this. - I know there are many exploits to root a phone used by tools like kingroot. I know these exploits are many and varied depending on your phone's CPU architecture, and software and not all root tools with work with my device. . I know the bootloader has to be unlocked and one must have USB Debugging enabled in Developer Options. I know some phone manufacturers make tools that help you root your phone (MTK Droid Tools) So far, none of these tools can root my phone.
Let's Start The Discussion Here:
I was able to not root but my Upgrade my phone from Lollipop to Marshmallow. I did this using SP Flash Tool and these instructions (which were badly translated and which as you can see by the comments in the video, I had to correct due to bad translation) See this video and comments by me to understand. https://www.youtube.com/watch?v=EEIJM2YjNzE - I used SP Flash Tool and a Rom Figo provided. After I figured out the botched instructions, I was able to upgrade my device with no problems.
Question 1: Isn't this essentially the same process that is used for Rooting? It proves my bootloader is unlocked and the phone does have the ability to flash a new Rom. <- Based on That, doesn't it seem to you that my phone would be in fact Rootable?
If you think so, tell me why, if you think Not, tell me why.
Question 2: If you think So, then: Someone suggested to me that using a tool like Magisk or SuperSU may be able to root my device. Does this seem likely to you based on what I've told you so far? No one in the SuperSU sub forum can answer this question.
If you think No, then we'll discuss this more. I'll wait for your replies. Thank you.
Rooting is, simply said, placing a 'su' binary in the system folder. SU means switch user, when you give that command you're instructing Android to give you root user privileage. OEM's don't want that to happen so they won't include it in their ROMs. Tools like supersu are made to copy that 'su' file to the system partition. There are a lot of ways to explain this, I'm just giving you something quick and easy to understand.
Now regarding your questions;
1) Flashing anything requires the bootloader to be unlocked on most phones. BUT MTK phones don't. (Except some HTC phones). SP Flash Tool can flash any partition without needing to unlock. It's dangerous security wise, but this means its also easier to root.
Infact all MTK phones are rootable. So don't worry about that.
2) How to root? The best way to root is with supersu. (You can also try magisk if you want to use Android Pay).
You need a custom recovery like TWRP first.
I found one here which is for your same CPU. https://www.needrom.com/download/twrp-recovery-13/
^I am just giving you a link to recovery which uses the same CPU so It may or may not work. PLEASE take a backup of your original recovery before doing anything.
Now download SuperSU zip file from here https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.82-201705271822.zip
Don't open it, just keep it in your sd card.
Flash the recovery using SP Flash Tool (check only the recovery box and select this file). Now unplug the phone and press Volume Up+Power Button to boot into recovery.
Then if it says swipe to allow modifications, swipe.
Now goto Install->Select the Supersu.zip file you downloaded->Swipe and reboot.
That's it! You're rooted!
Thanks.. again, you've answered things others couldn't. Much appreciated.
You say, " You need a custom recovery like TWRP first.
I found one here which is for your same CPU. https://www.needrom.com/download/twrp-recovery-13/
^I am just giving you a link to recovery which uses the same CPU so It may or may not work. PLEASE take a backup of your original recovery before doing anything."
Lets say Twrp doesn't work. What is this for, just to re-flash your original rom in case twrp fails at making a backup? ( I assume the tool makes your installed rom flashable in case the root doesn't work and you need to revert back to your original system) I have the SP Tool and the Rom for Marshmallow that works with my device from Figo. Can I use that if Twrp fails - or am I not understanding what twrp is used for? Just checking before I start this. Otherwise, I'll try to follow your instructions to the letter and see what happens.
Still Looking ?
STILL Looking? IF so, a few thoughts .... It is a nice phone for the price. The newer version eventually coming out looks even nicer, and for now, it is still my backup phone to my Figo Gravity. Discovered Figos when I got totally fed up with BLU phones.
ONE - If you have upgraded your Atrium to Marshmallow, as I did, none of the rooting methods that worked on Lollipop will work, so forget about them.
TWO - Down in Developer Settings you need to make sure OEM unlocking is allowed.
THREE - ASSUMING you have a TWRP build that will work, it is pretty simple. Take the ROM image that FIGO sent you and replace the "recovery.img" file with the TWRP (re-name it recovery.img and save the old one as recovery.old JUST IN CASE) file. It will be much larger than the factory ROM recovery image and that's fine. The scatter table, if you read hex addresses, provides for enough space to do this. Flash ONLY the recovery (TWRP) image, and be sure to DOWNLOAD ONLY with the SP FLASH tool. If uncertain, DO NOT PROCEED. It can be a real pain in the arse to re-do things if you accidentally format or upgrade things you didn't mean to. ASSUMING that worked, you can boot into TWRP by holding down the power / volume buttons (I assume you are familiar with this sequence).
FOUR - it is entirely possible that the next time you boot the thing normally, TWRP will be blown away. Happened to me a few times. There is some setting down in the boot image that causes this and I will have to dig up my notes to see exactly what the heck it was. It required taking apart the boot image - I used Carliv - fixing the one setting, and then re-packing and re-flashing it, BUT, you can ALWAYS keep replacing the TWRP image as needed. Inconvenient, but better than a sharp stick in the eye.
FIVE - when booted into TWRP, you should be able to flash SU, which will give you root, and it should STAY rooted after that unless and until you uninstall SU. FLASHIFY is STRONGLY recommended as a VERY useful app for rooted devices. TWRP, if you are unfamiliar with it, is SO MUCH MORE than just a recovery replacement. Handiest whole device backup there is. Has saved my bacon on several devices through numerous acts of personal stupidity. :crying:
SIX - IF ALL ELSE FAILS, you can ALWAYS revert to the factory image ROM. Just DOWNLOAD ONLY rather than Upgrade and DO NOT Format.
Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.
Ganapatya said:
Hi all,
My op6 is stuck, unable to reboot normally with the famous Qualcomm Crashdump mode message.
The phone has the bootloader unlocked, with TWRP recovery.
1 day ago I could access the recovery even reboot with the power+volume buttons, but it got to a point where it crashes all the time, unable to do anything.
Currently is only able to enter fastboot mode.
I have heard about the MSMDownload Tool.
- Does this tool keep the files/data in the internal memory?
For me the most important thing is to be able to recover the data.
The qualcom dumpcrash mode returns several different messages like:
- stack-protector kernel stack is corrupted in:--schedule*0xB90/OXOd0 (not exact numbers)
- fatal exceptinforece_signalinject.isra.8
Is there any chance of trying something?
I am extremely anxious and worried about the situation
Please help.
Click to expand...
Click to collapse
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.
lm089 said:
to start: it's good thing that you can get into fastboot mode. From there you should be able to do a complete re-install of your device, e.g. using the official LineageOS instructions.
Now to your situation: unfortunately you don't write too much about it like, is your phone running stock OOS or some custom ROM? If it's a custom ROM I'd say you open a topic in the according thread. Then: how much do you know about flashing recoveries, ROMs etc.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
In that case I would start all over (and that's how I got out of a similar situation several months ago): flash recovery, flash latest OOS to both slots, factory reset / wipe everything (to remove any encrypted data you won't be able to access anyways), flash you ROM of choice incl. other part like GAPPS, if needed, do basic setup and then finally try to recover anything that is in you backups.
I wish you a lot of patience and good luck, you'll need it, I'm afraid.
Click to expand...
Click to collapse
Thank you for your reply.
is your phone running stock OOS or some custom ROM?
Click to expand...
Click to collapse
Stock OOS, android 10, last release.
Then: how much do you know about flashing recoveries, ROMs etc.
Click to expand...
Click to collapse
I have basic experience installing customs roms, rooting, twrp, unlock fastboot...following tutorials, of course.
Regarding your data: in your current situation it may be extremely difficult if not impossible to secure any personal data now. How I understand it you cannot access the crucial partitions from the bootloader, at least I never heard of methods to get there. Although, people more knowledgeable than me may know of ways. So I do hope you are having recent backups at hand, on your PC or where-ever.
Click to expand...
Click to collapse
here someone says that in theory it would be possible if you have the usb debugging enable, but silly me I had it open but I deactivated it I think, so I'm not sure if I have access or not.
OnePlus 6 Stuck At "Qualcomm Crashdump" Screen All A Sudden | Data Retrieval Critical
Hi good people at XDA. This is my first post on this website and I am absolutely hoping to receive help from you all to find a way out of the depressing and extremely anxious situation I'm in. I was using my OP6 normally today and while I was...
forum.xda-developers.com
Code:
adb devices
mkdir "C:\RECOVERED_DATA"
adb pull /sdcard C:\RECOVERED_DATA
and then finally try to recover anything that is in you backups.
Click to expand...
Click to collapse
but if I do all that flashing process any backups that are in the internal memory will be erased, right?
I had photos, files, whatsapp chat history, documents...etc and they were all in the internal memory. It is not a great loss but it is important for me to be able to recover it.
in your current situation it may be extremely difficult if not impossible to secure any personal data now
Click to expand...
Click to collapse
for me it is more important to recover the files than to recover the phone. your words are discouraging
I have read other posts and maybe being able to install on top (dirty install) the same rom I have, would leave the system as it, is being able to access my files. Not even installing the whole rom but extracting the boot image from the rom and then installing it. but I don't know if I can install a rom or boot image from fastboot, or if I need to have a working TWRP first.
It is said here:
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82257413
- https://forum.xda-developers.com/t/...over-without-data-loss.4080725/#post-82261087
Ganapatya said:
your words are discouraging
Click to expand...
Click to collapse
of course that is not my intention. I just try to be realistic
As I wrote in my post, my knowledge is quite basic. I know what I read , and what I experienced with my different devices. So again: you may find instructions and real-life stories showing you ways out of there.
My experience is that you cannot connect your OP6 phone to your PC via ADB while in bootloader / fastboot mode.
a) It's either one or the other: bootloader <=> fastboot or recovery / system <=> adb. Other devices may have different options but we're not talking about Samsung but about OP.
b) I did some additional research last night but I couldn't find a single source talking about *read* access to user data from fastboot. All you can do there is flash i.e. overwrite partitions
c) keep in mind that most probably your personal data are encrypted. So even if you find a way to access your personal data from bootloader / fastboot you may not be able to read it
d) I never used MSMtool, never had to. But I did some more research about it. It looks as if you could re-flash stock ROM using that tool but to the cost of wiping everything. At least that is what the tutorials I found are saying
That said I'd say you don't have much to lose and can go trying out some things.
From my experience the qualcomm crashdump error can have it's source in a malfunctioning recovery solution; I had that when flashing a wrong TWRP version that would not be in harmony with the previously flashed OOS firmware.
From what I read our devices don't have a separate recovery partition, instead it somehow lives somewhere/somehow in the boot partition (experts: please don't crucify me if that is wrong ). So if that is the case one idea would be to extract the boot image from the stock ROM image then flash that to /boot/ from fastboot. Don't know whether that really works and helps, but in theory you would have a default boot partition and kernel *without* a conflicting recovery solution.
In case you're successful you may be able to boot into system and make backups of everything that's valuable to you.
Again: this is extremely wild guessing here, and you'll have to read in a bit on how to properly extract parts of the ROM image.
I also would *strongly* recommend that you continue asking for help in a more technical thread like the LOS19.1 one or Funk Wizard's thread about unlocking and flashing our OP6.
I wish you all luck you need!
I think your best bet it a HW solution, get someone to:
1. replace the modem IC, it's the possible cause of the qualcomm crash
2. solder a direct connection to the internal memory so you can recover your data