Hello friends.
Need couple advices.
Just became an owner of this phone.
No ROMs available, nothing yet, phone is new, I understand.
But,
1) I can`t enter neither recovery nor fastboot ("no command" with fallen robot with red warning in stomach instead of recovery and some factory mode instead of fastboot).
2) Drivers.. what`s with them? Any advice? (adb at least, PC doesn`t see the phone, except file transfer)
3) twrp?) root?) xposed?))) (android 7.0)
Will be very grateful for any help
Great questions. I have also ordered the phone but have not yet received it.
Would you like to tell us a bit about the phone? Does it work well? Do the stereo speakers work or is one speaker just a fake?
-Tiz- said:
Great questions. I have also ordered the phone but have not yet received it.
Would you like to tell us a bit about the phone? Does it work well? Do the stereo speakers work or is one speaker just a fake?
Click to expand...
Click to collapse
Thanks)
Works fine, a bit heavier than i expected, but now i like it.
stereo is fake, as usual
Already managed to enter recovery, fastboot, to connect from pc in fastboot. But still fail with adb drivers.
Found scatter file, that should suit, and now going to try readback firmware from the phone.
Then want to experiment with different TWRPs, and so on
On 4pda, they tellin about androidpay problems
My cam is ok, but one`s guy from 4pda - just terrible, may be he need to factory reset.. we`ll see
that`s it for now
I have this on order from Amazon. I'm really hoping someone with the skills will be able to get TWRP and Lineage setup for the S60. I'm a noob at this, especially about MTK devices. How hard would it be to port over a build from an existing phone with the same general config (Helios P25, 6 + 64 GB)? I have concerns after reading about finding malware on the X5 Pro and I'd like to mitigate that.
Those of you that already have your S60's, are you aware of any pre-installed adware or other unwanted software? Seems to be a very common issue on Doogee handsets....
What is the real weight of the Doogee S60 handset please? Various spec sites and retailers have it listed from 173g to 337g! They can't all be right. Doogee don't list the weight on their website so I expect it to be bit heavy. I will be really grateful if someone who has one can put it on a scale and weigh it.
I've just received mine.
It's 289grams
The truth at last
fingery said:
I've just received mine.
It's 289grams
Click to expand...
Click to collapse
Thank you a lot.
At last some genuine information!
Doogee never answered my emails and don't list the weight in their specs. I did get a reply from one retailer who said it is 202g and they get their specs direct from Doogee so it must be correct. I was suspicious so thought I would ask here where there is no commercial pressure to deceive.
It is a bit hefty at 289g so will now look for another rugged phone - any recommendations?
Just received today.
297 gr as you can see in attached pic.
I am also interested on rooting, TWRP... and also very interested on Bluetooth+ plus ANT+ service. I don't know if this o is possible in this phone, but very interested to me for connect with heart rate monitor ANT+ (this works very well with my previous Nexus 5).
Any information will be appreciated!
Thanks.
Ruben
PD: Sorry, pic is on Google photos and I can't attach it or putting a link to it!
Curiousdrummer said:
Thank you a lot.
At last some genuine information!
Doogee never answered my emails and don't list the weight in their specs. I did get a reply from one retailer who said it is 202g and they get their specs direct from Doogee so it must be correct. I was suspicious so thought I would ask here where there is no commercial pressure to deceive.
It is a bit hefty at 289g so will now look for another rugged phone - any recommendations?
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Having spent a few hours setting up my S60 yesterday i have a few issues. Can anyone clarify if this is just me or are we all seeing similar :
Fingerprint reader - easy to setup and seems to detect quickly however once configured it's very poor in use. More often than not the device fails to recognise my print and unlock.
NFC - Annoying notification "NFC service. Touch to view settings" cannot be hidden/removed.
NFC - Android pay not working. Error message saying device may be unlocked or rooted etc.
Build details etc shown on attachment.
I heard somewhere that S60 is prerooted, maybe thats issue with Android Pay?
Chamelleon said:
I heard somewhere that S60 is prerooted, maybe thats issue with Android Pay?
Click to expand...
Click to collapse
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
fingery said:
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
Click to expand...
Click to collapse
I have set upa third part application to pay, and it seems to work, but I haven't used yet. I also have read the warning with Android pay, but in spain there are other apps supported by banks. But yes, it is annoying the nfc notification always on task bar.
And my fingerprint sensor is working correctly.
Ruben
Enviado desde mi Nexus 7 mediante Tapatalk
I find it hard to believe they pre-root the phone from the factory although kudos if they did. For those of you with your phones already have you installed any anti-malware and what has been the result? I've been reading up on the issues the X5 Max Pro owners have been having and I'm hoping to avoid that s***storm if I can.
fingery said:
Shame they market it with NFC and using it to Tap and Pay but Android Pay isn't supported on it.
Any idea if there's any way around before i spend hours on it?
Click to expand...
Click to collapse
on many Chinese phones, Android Pay does not work because google servers do not certify!
their certification on a certain phone requires financial costs.
But Android Pay is easy to run having root rights
TWRP and ROOT access will be ready soon!
STOCK ROM + TWRP + ROOT + XPOSED (is said to be buggy)
First of all i should thank a lot and redirect all regards to this very man serg2327, because all that below is totally his merit
Firstly, speaking about drivers, I didn`t install any extra, just the ones the phone did automatically. You only need to connect ur phone to ur pc in different states (e.g. turned off, recovery, fastboot) and all will be installed by itself (except adb drivers)
STOCK ROM
Was made from full (64gb) memory dump.
I cant post links, i`m very sorry
U can google them at the theme of doogee s60 at 4pda.
Or, may be serg2327 will post them here
1. Unpack the firmware
2. In SP Flash Tool point to the scatter file containing in firmware
3. Flash any partition u want (I flashed all of them and everything was fine)
TWRP + ROOT *(+XPOSED)
twrp is ported from BV8000
there`s a touchscreen bug, but there`s also some temporal solution
supersu is also taken from BV8000
Recovery could also be flashed thru SP Flash Tool, u just need to tick it in download menu and put the right path, but in this case, due to a touchscreen bug u will need an otg cable and a mouse, otherwise u won`t be able to flash supersu and that will cause in loosing twrp after booting system.
That`s why we will flash recovery thru fastboot, because there during the first boot - touch is available, but only for the first time, afterwards it will also fail.
So,
1. Download and place recovery.img somewhere, copy the path. I place it just in C:\ for convenience.
2. Download and place supersu.zip into the /sdcard of your phone (do it while your phone is on, before proceeding further, because in twrp my pc couldn`t see the phone)
3. Turn off the device, then press and hold together "pwr" and "vol+" until the screen turns on, then u see a green robot with a red warning in the stomach, then press and hold "pwr" and then just slightly press "vol+" (don`t hold it, and press only after "pwr" is held), u`ll see the stock recovery menu, choose with "vol-" fastboot mode (or bootloader, don`t remember, it is second from upwards), press "pwr" to enter this mode, u should then see just a small FASBOOT written on a black screen.
4. Connect the phone to the pc, open cmd.exe as an Administrator, type:
fastboot devices
u should see ur phone by its serial (like adb devices)
if everything is ok, go next.
type in cmd:
cd C:\ (or other path where the recovery is lying)
fastboot flash recovery recovery.img
fastboot boot recovery.img
then u`ll get ur phone booting in twrp, and touch should work this time
5. Flash supersu from /sdacrd
*5.1. If u like, can also flash xposed (it is beta version, is said to be buggy) at this very moment, while u have ur touch available
6. Wipe dalvik cache and boot to system
*7. For using xposed u need an installer (ticking modules, etc)
8. Open supersu, it will ask for a binary update, press cancel and forget about it.
9. That`s it, u have twrp + root.:good:
p.s. The firmware is deodexed, that means we can freely clean chinese system trash.
And, one more great thanks and regards to serg2327 . It`s more of his knowledge than mine
link to firmware / backup: https://mega.nz/#!APhWya7B!nNrDImupeIaPyPAvIrFxGyyfoZEAIO-DEAy2XFtCDIM
link to TWRP: https://mega.nz/#!NHpBlY5C!RPVpVCUuTslLOrcf_bjL4pBYOGblcrRlN8CQ9I7cIbY
in the TWRP the sensor does not work, control via the otg cable through the optical mouse
after the TWRP firmware you need to boot into it and install the root, otherwise the android system will restore recovery
link to patch root: https://mega.nz/#!0HRHzbia!rX1iMekfYymzSzq0AtTT96-lELMziirBIAF3kpe_BCc
regret to tell, but firmware is odexed.. 80-90%, it accidentally happened that during brief look i saw couple apps from that 10-20% deodexed, the rest has .odex files
I'm expecting my phone today, so I'll post impressions over the weekend. Any news about about a Lineage port?
My s60 issues so far..
Hi, i have a s60 for about 2 weeks now and i can tell its not without issues:
1. Screen comes ON with no reason, as IF somebody tryes to unlock with finger print, it and says "too many attempts, try later" .It happends quite often and it goes every 30 seconds or so.. Then stops.. Half an hour latter starts again... Annoing..
2. Finger print unlocking-hit and miss... Sometimes it unlocks as soon as you touch it, sometimes doesn't work at all..
3. Loud speaker ,again, sometimes on full volume you get loud and crisp sound, even then one of them is fake, but next time, out of nowhere sound becomes so crappy , like from ripped speaker, doesn't take high piches at all, even IF you tune volume half way dawn.. like its broke sudennly.. latter OK again.. That affects sounds, like call or notifications- sometimes its loud and clear, sometimes you just miss them..
4. Calling 2 out of 10-12 calls, -you dont hear them, well you do, but so quite, that you just can't make up the words. And then it fixes itself..
5. Camera is inposibble to focus where you want. It hunts a lot.. In the menu settings for ISO and shutter speed set to auto and greyed, like its there, but you can't change it-gimmick??
Over all-battery life is great, screen is superb with very natural color reproduction, camera is very good then you get it in focus. Dynamic is clear and loud then it works.. Call quality is superb then it works. Never dropped WiFi conection, Bluetooth connects instantly and never had an issue, reception very good.
Hope all thouse problema are software related and can/will be fixed by update, becouse its a nice phone. Love the size of it.
Related
Guys i really need your feedback and advice on this situation. Okay I was trying to install the Rom CNA. 3.5.0 (JB). But my battery was low (stupid me) and i install the ROM with no problem, but when the phone rebooted it went to the Motorola logo and i was stuck. I tried the volume down button which is the NV recovery but my phone turned off due the low battery i guess. And it seems my option could be fast boot but i don't know how to operate it. My question is that can i get out of this situation with a pre-charged battery, or a software from the internet. I really need your advice on this one?
swaggerdagger said:
Guys i really need your feedback and advice on this situation. Okay I was trying to install the Rom CNA. 3.5.0 (JB). But my battery was low (stupid me) and i install the ROM with no problem, but when the phone rebooted it went to the Motorola logo and i was stuck. I tried the volume down button which is the NV recovery but my phone turned off due the low battery i guess. And it seems my option could be fast boot but i don't know how to operate it. My question is that can i get out of this situation with a pre-charged battery, or a software from the internet. I really need your advice on this one?
Click to expand...
Click to collapse
Yes, you'll need a charged battery.
After you get one, enter the recovery and do all the necessary wipes (cache, dalvik, data, etc.) and reboot your phone
If it doesn't work, you may reapply the rom via recovery, avoid applying SBFs, as they may brick your phone.
Can't you just charge the battery while the phone is off?
I know I can on mine, but I'm not sure what's needed for that (like, do you need a bootable system?).
ravilov said:
Can't you just charge the battery while the phone is off?
I know I can on mine, but I'm not sure what's needed for that (like, do you need a bootable system?).
Click to expand...
Click to collapse
Or charge the battery by using EBC...
Sent from my MB860 using XDA Premium HD app
bimasakti85 said:
Or charge the battery by using EBC...
Sent from my MB860 using XDA Premium HD app
Click to expand...
Click to collapse
What is EBC? and how do i use it ?
just hook up the phone in fastboot and issue this command "fastboot -w" then reboot and you should be good
swaggerdagger said:
What is EBC? and how do i use it ?
Click to expand...
Click to collapse
External Battery Charger.
android-DEP said:
just hook up the phone in fastboot and issue this command "fastboot -w" then reboot and you should be good
Click to expand...
Click to collapse
Any steps or guidelines you can give me to get fastboot to reboot my phone to normal ?
which rom did you flash last on your phone? Was it gingerbread or CM7 based or CM9 based?
Depending on your answer to that question, you can try a few things to restore your phone using fastboot.
If it was let's say some CM7 based rom, you can locate a stock CM7 kernel and download it. Extract the zip file to pull out the "boot.img" file and put it inside the same folder you're running fastboot.exe from.
Once that's done, reboot your phone into fastboot mode, and connect it to your PC via usb cable and real quick just type "fastboot devices", that command just shows you which devices it's currently connected to via the fastboot interface and you should see your phone listed with it's serial number showing which tells you that you can continue the procedure..
then do a wipe of any data which might interfere with the new kernel by typing "fastboot -w", don't worry, you won't lose any personal files like pictures or contacts..
after thats done then type out "fastboot flash boot boot.img" which will flash the new kernel onto your phone.. phone's not booting past the initial Dual-Core screen can sometimes be attributed to a bad flash of a rom, kernel not properly being written to the device in cases where the updater script couldn't mount a partition to extract the boot.img to before writing the raw data to your device. The updater-script which is just like a batch file, it just goes down line by line running commands and does not halt on errors to let the user know that something failed. So if something failed during the flash process and you didn't successfully flash some parts of the rom normally, it could still finish the installation and all you'll get it Installation Completed type message where you think it's all good but in reality some parts of the installation didn't complete.
Perhaps the rom didn't properly perform the necessary prep work of wiping cache and dalvik cache. Not exactly always an issue as it depends on the circumstances of what you're installing and what you had installed prior.
I've had a few roms here and there that put me in your shoes, the solutions I've always found to work was to first try something basic like wiping the cache of the device and reboot. If that didn't work, then this is where you could try flashing a new kernel.
Since you did the proper wipe of data, you can make sure the kernel gets installed properly as you isolate the installation from the entire process.
It takes 3-5 seconds anyway for fastboot to flash files anyway so theres no harm done anyway so long as you get the proper compatible files for your setup. Reboot the phone afterwards and give that a shot.
Unless you tried to flash a PDroid patch on your phone, which requires you to have a working rom installation to begin with from which you pull files to patch so you can flash them over the current installation, you should be able to boot.
If you still cannot boot, then reboot into recovery and open up the ADB interface in command prompt and run this command
Code:
adb logcat > "c:\logcat_dump.txt"
and just kick back for a few minutes while it dumps the entire log into the root of your drive in a text file named logcat_dump.txt... press the Windows symbal key(its between the CTRL & ALT buttons on the left side of the keyboard), while holding that press the letter R to bring up a run window box where you type in "%SystemDrive%\logcat_dump.txt" and hit enter... post the log here and you can get more feedback on where the issue is
android-DEP said:
which rom did you flash last on your phone? Was it gingerbread or CM7 based or CM9 based?
Depending on your answer to that question, you can try a few things to restore your phone using fastboot.
If it was let's say some CM7 based rom, you can locate a stock CM7 kernel and download it. Extract the zip file to pull out the "boot.img" file and put it inside the same folder you're running fastboot.exe from.
Once that's done, reboot your phone into fastboot mode, and connect it to your PC via usb cable and real quick just type "fastboot devices", that command just shows you which devices it's currently connected to via the fastboot interface and you should see your phone listed with it's serial number showing which tells you that you can continue the procedure..
then do a wipe of any data which might interfere with the new kernel by typing "fastboot -w", don't worry, you won't lose any personal files like pictures or contacts..
after thats done then type out "fastboot flash boot boot.img" which will flash the new kernel onto your phone.. phone's not booting past the initial Dual-Core screen can sometimes be attributed to a bad flash of a rom, kernel not properly being written to the device in cases where the updater script couldn't mount a partition to extract the boot.img to before writing the raw data to your device. The updater-script which is just like a batch file, it just goes down line by line running commands and does not halt on errors to let the user know that something failed. So if something failed during the flash process and you didn't successfully flash some parts of the rom normally, it could still finish the installation and all you'll get it Installation Completed type message where you think it's all good but in reality some parts of the installation didn't complete.
Perhaps the rom didn't properly perform the necessary prep work of wiping cache and dalvik cache. Not exactly always an issue as it depends on the circumstances of what you're installing and what you had installed prior.
I've had a few roms here and there that put me in your shoes, the solutions I've always found to work was to first try something basic like wiping the cache of the device and reboot. If that didn't work, then this is where you could try flashing a new kernel.
Since you did the proper wipe of data, you can make sure the kernel gets installed properly as you isolate the installation from the entire process.
It takes 3-5 seconds anyway for fastboot to flash files anyway so theres no harm done anyway so long as you get the proper compatible files for your setup. Reboot the phone afterwards and give that a shot.
Unless you tried to flash a PDroid patch on your phone, which requires you to have a working rom installation to begin with from which you pull files to patch so you can flash them over the current installation, you should be able to boot.
If you still cannot boot, then reboot into recovery and open up the ADB interface in command prompt and run this command
Code:
adb logcat > "c:\logcat_dump.txt"
and just kick back for a few minutes while it dumps the entire log into the root of your drive in a text file named logcat_dump.txt... press the Windows symbal key(its between the CTRL & ALT buttons on the left side of the keyboard), while holding that press the letter R to bring up a run window box where you type in "%SystemDrive%\logcat_dump.txt" and hit enter... post the log here and you can get more feedback on where the issue is
Click to expand...
Click to collapse
My phone keeps turning off, it doesn't even reach the logo and it wouldn't even hold a charge...... .Its best i order a extended battery with an external charger?
No, no need to order a battery, there's nothing wrong with your current battery.
This was exactly the same way I first soft-bricked my first atrix long long ago. The battery would not charge no matter what I did and I could not flash anything onto the phone because the charge was too low and kept getting lower. It eventually fell to the point where it was like less than 5% charge left on the phone.
For some stupid reason, the Atrix does not recharge the battery when you do not have a proper working installation currently on the phone, like a corrupt install where something didn't do what it was supposed to do.
The catch is that once this happens and you have a corrupt install of whatever rom half-ass installed that doesn't boot, perhaps maybe even if the rom improperly wiped out the recovery so you can't boot into recovery, the phone will not recharge itself anymore. This is one MAJOR reason why you should always flash your phone with a FULL battery charge, not because it's cool to have a full battery icon on the statusbar, but when the fit hits the shan and things go wrong, you have some spare life left to be able to to try flashing something else to recovery your phone with before it drains too low.
You have 2 options at this point, you basically have to find a full charged up battery to use for about 10 minutes. Reason I say you have to find a battery and not just say find someone with an Atrix is because you can also use the battery from the Motorola Droid.
This was what I did once I finally found someone near by with a Droid, I borrowed their battery for 10 minutes to restore my phone and it worked like a charm.
Atrix battery model is BH6X and the Droid battery is BH5X which is the same size but has a weaker mAh. Long term I dont know how safe it is to continually use that battery but for something like restoring your phone, using that battery is perfectly ok unless you have a friend who has an Atrix also. Have him charge his battery up to full and then swap batteries with him so he can continue charging while being able to use his phone and you will have a full charge which buys you enough time to recover your phone before you drain the battery from flashing.
This was the exact reason I purchased this charger & battery just in case of just in case
Only thing is that this generic battery is 1800mAh 6.7Wh and the factory battery is 1880mAh 7.0/7.1 Wh but I never had any issues with the generic battery.
You can optionally get this nice Dual Dock Cradle + 3 batteries
Here's another option, 2000mAh battery with external charger
The way I solved my issue was to download a fresh copy of a 2.3.4 SBF file and a good copy of RSD Lite. Once I popped in the battery into my phone, I hooked it up to RSD Lite and just let it do it's job to restore everything back to square 1. Locked bootloader, not rooted, deodexed or zipaligned. But back then these things didn't matter as long as I was able to recover my phone and not have to pay $125 to send it to AT&T insurance dept. just to get a refurbished one in exchange.
I truly believe this is one situation which does earn the necessary required use of an SBF file to be flashed with RSD Lite. There's risks involved with flashing SBF files and so it's best to avoid them altogether but there are only a handful of certain situations which do call for their use such as recovering\restoring your device from an unusable state.
Definitely do some more reading about the matter and what your options are here. You're going to have to keep an eye out for the pros vs. the cons of using certain methods to recover a soft bricked phone. I'm sure last thing you want your phone to be is a hat weight right? lol, but do yourself a favor and read up more about this before you decide your course of action. Don't just start flashing anything that pops up that seems like it will work
android-DEP said:
You have 2 options at this point, you basically have to find a full charged up battery to use for about 10 minutes. Reason I say you have to find a battery and not just say find someone with an Atrix is because you can also use the battery from the Motorola Droid.
Click to expand...
Click to collapse
You mean Droid X, right? The Motorola Droid use the BP6X, as the Motorola Milestone / Milestone 2, and it's really small when compared to the BH6X.
Yea thats what i meant, can't keep up with these incredible nexus droid htc photons prophilactic splendifures flux-capacitator names they went overboard with on naming android phones in the last 2 years. It's ridiculous when you have to think back to which model some phone was last year that you might've had but not sure because it looks like 10 other phones and the model names all sound like comic book super heros or something.
Specially a few years ago when I used to repair the hardware internally on iphones, blackberry & android smart phones. Sometimes I'd be so sure without a doubt in my mind about getting the right parts for phones and then later realize it's in the same family but a diff model #. Good thing with Android they atleast make parts to fit exactly or not fit at all. Like a safety net coupled with common sense, if it looks identical and does fit, then it'll work, otherwise its not compatible. Just like these 2 batteries, so regardless if it's Droid X or Droid DeathShovel Excalibur Pluto Carbide Titanium XIII Deluxe, the model number of the parts is the most important thing to look for
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The spare charger and battery I bought actually never needed to be used for a situation like that again as after the first time it happens to you, you learn a lot of info on how to not land in the same spot again in the future. It is how ever useful if you like to flash roms a lot and sample different ones frequently. it's nice to have a battery in the phone you can use while having another one on charger to swap over once your current battery drains. This way you never need to be plugged into a charger via usb to recharge anymore.
---------- Post added at 09:50 PM ---------- Previous post was at 09:37 PM ----------
I just stumbled upon this online, this is a must have for anybody with an atrix and it's only $20 free shipping HD motorola dock with remote control
UPDATE (04/29/2013): If you are having issues with rooting or jelly bean is too unstable, there is another way. I found this a while back, but did not know that JB had a lot of bugs. First off, all credit goes to Apache Thunder. First off you want to download PHA44IMG. Now open the zip (do not extract), and look for android_version.txt. Where it says "mainver" change the number to 2.12.651.5 (JUST THE NUMBER, NOTHING ELSE!) Now Save the file while it is still in the zip. Now copy the zip to your SD card without putting it inside any folders (basically the root of your SD card). Once you do that, go into your boot loader (take battery out, put it back in, hold down Vol Down + Power). Wait for the white screen to come up with the three androids at the bottom, and once it finds the file, then you can hit Vol Up, and it will re-load the stock software. Obviously, this will overwrite ANYTHING you have on the phone itself, so if you need to back up something, then back it up (common sense). I hope this helps.
Well, I have been looking, and looking, and looking. I just could not find a way to root this device. The codename for this phone is called "Kingdom." So I am not sure if this works on the Sprint version, but I can confirm this works directly on Boost Mobile on ICS. I am going to make this guide as easy as possible. I take NO credit for what is in this guide, only for posting it here. I seen guides, but they are either out of order, or just do not make sense. This is my first guide, so I do not know how to make it fancy or what not. Before you criticize the way the guide is set up, make sure the information is correct. This works for me, and it is the right and easy way to root the phone. I used forums before, but this is new to me. I wrote this guide from memory from a phone that I did literally three hours ago.
------
What this guide will do for you is root your device, and install jelly bean software. Before you go any farther, please back up ANYTHING you want. Your SD card will not be affected but you will lose apps (that can be re-downloaded), contacts, SMS messages, etc on the phone. Your contacts can be restored using Gmail. Just be aware that I am not responsible for ANYTHING that happens to your phone. However, I can help you if you need it, though.
------
Here are the people possible for this guide:
LOLINTERNET
2fast4u88
------------
The things you will need:
Boost Mobile HTC EVO Design 4G (please upgrade to ICS, it makes things so much easier)
Internet
Patience
Skills to Read
Ensure that HTC drivers are installed. If you have Win7, they should automatically install.
Basic/Novice computer skills
Common Sense
Here are the files:
boosthtcdesignevo4g-root.zip
cm-unofficial-kingdom.zip
gapps-jb-20120726-signed.zip
----------
First thing is first, you need to unlock your bootloader. This is very easy, and quick. If you are familiar with HTC phones, you are probably familiar with htcdev.com. If not, then you are in the right spot. First off, go and visit www.htcdev.com and register with a valid email address. It is very important you provide a REAL email address, because you will get a file emailed to you. Now, after you register, go to the home page, and click on "Unlock bootloader," and Get Started. which is the second icon. After that, there will be a list on the right hand side. Go all the way to the bottom and select "All Other Supported Models" and click "Begin Unlock Bootloader." There will be two popups, on the first one, click Yes, and on the second one, click check both checkmarks, and click on "Proceed to unlock." Scroll down to the bottom, and click the green button, and do the same on the next page.
Now, that we have that out of the way, we have to get a special token inside of your phone. To get this, we will need to use fastboot. Go ahead and extract the boosthtcdesignevo4g-root.zip to your computer. I recommend using the C:\ folder and in a new folder called "root", as it will make it easier to navigate. In fact, this guide will imply that it has been extracted to C:\root. Once it is extracted, click Start, and type in "cmd" and hit enter. If you are not on Windows Vista/7, then click Start>Run and type in "cmd." This is our command prompt, a black screen. Now navigate to where you extracted the files at, in this case, we will type "cd C:\root" (or whatever you extracted it to. Now take out the battery, and put it back in. you will hold down the Vol Down and Power down button. A white screen should pop up. If not, try again. You are in the right spot if it says "**LOCKED**" in purple. Use the VOl Down to go down to "Fastboot" and hit the Power button (kind of like the Enter button). If it says something like "reading PH4IMG.zip" in green, don't worry. Let it finish, and when you see the options again, use Vol Down and highlight fastboot and hit the Power button. Connect your phone via USB, and it should switch from Fastboot to Fastboot USB. If not, unsure that you USB connection is secured.
In the command prompt, type in the following without quotes "fastboot oem get_identifier_token." You will get a long screen of numbers, that will start with <<<< Identifier Token Start >>>>. This is probably the most hardest part, which is copying the token correctly. You want to right click and hit Mark. Now start at the first "<<<<" and end it at the "<<<<< Identifier Token End >>>>>". It should look exact like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
.
Now, once it is highlighted, right click, and it will be copied. Go back to the browser, and scroll down to the bottom, where it says: "My Device Identifier Token:" and right click on the white edit box, and paste it. and click submit. If you get errors, re-copy it, and try again. Like I said, this is the hardest part, so that means this whole process is pretty easy. Anywho, once you have done that, you should get a confirmation about a file being emailed to you. Remember that email I told that should be real, well this is it. Check your email, it should be from [email protected] and the subject should be "The key to unlocking your HTC Device". Check the email for attachments, as it should be a file that says Unlock_code.bin. Copy that to C:\root. Now go back to the command prompt, and type in "fastboot flash unlocktoken Unlock_code.bin." Now once you do that, your phone should go to a black screen, and it should look like this:
All you have to do is hit the Vol Up button, and hit Power. There you have it, your bootloader is unlocked.
-------------------------------
Now here comes part 2A of the rooting process. We need a custom recovery. Go back to that white screen on your phone, the HBOOT, and select Fastboot again (just like last time). Once you have selected that, go ahead to your command prompt and type fastboot flash recovery recovery.img. Once that finished, you have clockwork mode recovery. I am not going into details what the recovery does, as there are a PLETHORA of information about it. Just know it is one of the special things you need.
Here is part 2B. Next, look in the C:\root folder, and get ready to copy the Superuser-3.0.7-efghi-signed.zip file onto your SD card on your phone. You need to get to the white screen again on your phone, you know taking at the battery, ya-da-da-ya-ya. Anywho, just use Vol Down to go down to RECOVERY, and you will see a black screen with blue text. You will use Vol Up/Vol Down to select items. Go down to mount and storage and hit Power. Then select USB storage. Once you do that, you should see it pop up on your computer, and just copy the zip over. While we are at, copy over cm-unofficial-kingdom.zip & gapps-jb-20120726-signed.zip. Just keep this file at the root of your SD card, it will make things MUCH easier. Now, just choose, "Go Back" and select "Install .zip from SD Card." Make sure you do not select the one with "update.zip" as this is the wrong one. Once, you do that, hit Vol Up, to go to the bottom first, and go up until you get to Superuser-3.0.7-efghi-signed.zip, and hit the Power button. Then you will see a whole bunch of No's, obviously, you will want to click on Yes - Install Superuser-3.0.7-efghi-signed.zip. That should be quick, and simple. Guess what, your phone is rooted!!! Select reboot now, and you can verify it by installing the "Root Checker" app from the play store. You also may need to contact Boost Mobile, to re-activate your phone. Once you download an app that requires root, it will get permission from Superuser, which is basically the "root police" on the phone. If you are aware of the root, select "Grant," if not, select "Deny." Common sense.
------
Now time to install jelly bean. This is simple as well. Just go back to the white screen, like we did a hundred times already throughout this whole process. Select RECOVERY, and this time, we will go to install zip from SD Card, just like last time. Go ahead and select cm-unofficial-kingdom.zip and install it, just like the last time. DO NOT REBOOT YOUR PHONE! Once you are done with that, do the same thing for gapps-jb-20120726-signed.zip. Now go ahead and reboot the device. Now you are not only rooted, but have the Jelly Bean software as well. Follow the on-screen prompts, and you will be able to use your phone
----
Again, I am not responsible, for anything that happens to your phone, and of course you void your warranty. If you have any questions, please do not be afraid to ask me. If you need more help, I am always happy to help.
Out of curiosity, will this allow me to pop in a non-Boost SIM such as one from T-Mobile or AT&T?
I think there is an app on the play store. But from what I remember the global sim function is locked
Sent from my Carbon-ize Evita using xda-developers app
Thanks but
Hello and thanks for your guide. I just would like to say that perhaps you could add a notice in VERY BIG LETTERS to remember to backup your ROM before proceeding before or after you Root your device! I followed your guide to the letter and without thinking (Obviously) did not do a stock recovery and am now screwed. I have been fighting this problem for 2 weeks because no one has a current stock image that has the latest Boost PRL61009 and other (Radio) issues, the list goes on. Also when you do this (and it works great I must say!) your now at a newer HBoot version and can not go back without another nightmare problem (Main Version Older error). So just as a precaution against people like me who go line by line (with blinders on) please insert the precaution to Back UP! Thanks again.:crying:
awesome
Thank you so much for this guide.
I have been wanting to install jelly bean for quite awhile now.
Quick question(s)
1. Is there any way to get the official boost mobile wi-fi hotspot application installed ?
I noticed the official one uses less battery. I don't mind paying for the ability to tether my phone.
2. Is there anything broken with rom such as video recording and sms.
Once again thank you so much for posting this guide.
HELP
Alright so, this morning I attempted to restore my phone to factory defaults and it did not like that. I am rooted so my bootlocker is unlocked. When I attempt to go into recovery, the phone reboots and goes to an image of the phone with a red triangle/exclamation point in it. As of now my phone is unusable so any help woould be greatly appreciated
Followed the guide,with some problems
Probably didn't read the guide well.
Couple of things
1) this is for the us cellular network
2) used titanium backup, it didn't work when I tried to restore everything back to original
There are some good things with the jelly bean rom, but 4g is missing and here are some other things that I am nor happy with so I want to flash back to the original boost mobile stock rom
I have access to another stock boost mobile evo design 4g phone, so if there is anyone that know if it is possible to coy the stock rom and transfer it to my modified handset, I would greatly appreciate it.
Thanks
Well I can update the guide to go back to stock. Thank you for putting the bugs out there.
Also. This is boost mobile not us cellular. If us cellular works, then I will update the guide. However it is intended for boost mobile. I just moved, so when I unpack my PC, I will update it to reflect stock ROMs.
Sent from my Carbon-ize Evita using xda-developers app
t_haggerty said:
Alright so, this morning I attempted to restore my phone to factory defaults and it did not like that. I am rooted so my bootlocker is unlocked. When I attempt to go into recovery, the phone reboots and goes to an image of the phone with a red triangle/exclamation point in it. As of now my phone is unusable so any help woould be greatly appreciated
Click to expand...
Click to collapse
How did you attempt to restore? From the ROM or the boot loader?
Sent from my Carbon-ize Evita using xda-developers app
boogiedownandroid said:
Thank you so much for this guide.
I have been wanting to install jelly bean for quite awhile now.
Quick question(s)
1. Is there any way to get the official boost mobile wi-fi hotspot application installed ?
I noticed the official one uses less battery. I don't mind paying for the ability to tether my phone.
2. Is there anything broken with rom such as video recording and sms.
Once again thank you so much for posting this guide.
Click to expand...
Click to collapse
I heard that MMS has a hard time working well. As far as the hotspot, not sure. You can check then market
Sent from my Carbon-ize Evita using xda-developers app
Carbon238 said:
Hello and thanks for your guide. I just would like to say that perhaps you could add a notice in VERY BIG LETTERS to remember to backup your ROM before proceeding before or after you Root your device! I followed your guide to the letter and without thinking (Obviously) did not do a stock recovery and am now screwed. I have been fighting this problem for 2 weeks because no one has a current stock image that has the latest Boost PRL61009 and other (Radio) issues, the list goes on. Also when you do this (and it works great I must say!) your now at a newer HBoot version and can not go back without another nightmare problem (Main Version Older error). So just as a precaution against people like me who go line by line (with blinders on) please insert the precaution to Back UP! Thanks again.:crying:
Click to expand...
Click to collapse
EDIT: OP has been updated to revert back to stock.
Thanks for the info. I wrote this guide from experience and was able to flash jelly bean and go back to stock. I will upload a image file so you can flash stock and still keep root. Sorry for everyone who is having issues.
Sent from my Carbon-ize Evita using xda-developers app
Shows carrier as us cellular and not boost mobile???
Overall good post followed the steps and downloaded the zip files. Trying to,get back to stock rom and having problems. Noticed that the carrier shoe us cellular, thought the rom was for the boost mobile evo design 4g phone. Could this be the reason I am having a problem flashing a boost mobile rom?
Anyone have a stock rom for boost mobile evo design 4 g, purchased feb 2012, trying to get back to original state, thanks
Shouldn't matter. That pha4img.zip should work just fine. This guide is intended for boost mobile
Sent from my Carbon-ize Evita using xda-developers app
Nice Rom
This is a really nice rom, just one question, is the rom being worked on, or just being provided. This looks like the same rom that 2fast was working on, but that thread seemed to go dead, so I am wondering if it has been picked up again and if we are going to see all the features of the phone working soon.
Can you help me back to stock rom
Herc08 said:
Well I can update the guide to go back to stock. Thank you for putting the bugs out there.
Also. This is boost mobile not us cellular. If us cellular works, then I will update the guide. However it is intended for boost mobile. I just moved, so when I unpack my PC, I will update it to reflect stock ROMs.
Sent from my Carbon-ize Evita using xda-developers
Click to expand...
Click to collapse
htc evo design boost mobile
:good:,,ok first i want to let u know guys my english is not perfect,,i want to said thanxxx for this post i did step by step and my htc evo is workin perfect with jelly bean also i waste like 3 days trying to find the best way to unlock root my cell this one help me to do evrithing plus jelly bean is easy and im glad this post is perfect,,,,,thaxxx again and all credit to this guy thxxx again
Any news on this working for the US Cellular version(Hero S)? Just got one to replace my cappy and I'm having a lot of trouble trying to find a good up-to-date rooting guide, and roms, for this Hero S. Also trying to figure out what ROMs are available to me.
So now what...
Hello and thank you for the guide, very easy to follow. I am having one small issue however which is after installing the last two zip files the gapps and unofficial. zips my phone is stuck at the boot screen showing the Alien Android character and the CMX | CyanogenMod 10 at the bottom and does not go any further. So where did I screw up? Please help asap Thankyou,
Joeatheist
Attempted to reload stock software and no
after following directions to reload stock software It seems to stick while on white screen after loading takes place it says Parsing.... [PH44IMG.zip and goes no further. Yikes! Everything was fine until I tried to load those last two zip files and install jelly bean it was rooted and ICS loaded up just fine then once I went for jb this thing is useless. Any help would be greatly appreciated guys. Am I just being impatient is it gonna take an hour or two for this parsing message to clear? I s the re a way ouit of thisa/ Did I brick my phone? Anyone? Bueller...? Bueller...?
Respectfully,
JoeAtheist
---------- Post added 21st September 2013 at 12:49 AM ---------- Previous post was 20th September 2013 at 11:54 PM ----------
Well, I ended up pulling the SD card. Went to white screen and hit factory data rest. rebooted and it still tried to load CMX mod. And it booted fully! Apps are restoring and all is good in the world again. Thanks for baring with me and thank you for the root guide. Very happy so far. Whew!
Respectfully,
JoeAtheist
cmx
so I followed all the instructions and completeted everything. Only problem is(and it is a bit of a big one) when I went to reboot after installing the last two zip files the screen just stays stays at the screen where it displays some human like figure and the word "cmx cyanogenmod 10" is on the bottom. I know it isn't frozen since the blue animation at the bottom continues to happen but it never makes it way to the home screen. Anyone know how to fix this?
---------- Post added at 07:44 PM ---------- Previous post was at 07:11 PM ----------
aimtimes100 said:
so I followed all the instructions and completeted everything. Only problem is(and it is a bit of a big one) when I went to reboot after installing the last two zip files the screen just stays stays at the screen where it displays some human like figure and the word "cmx cyanogenmod 10" is on the bottom. I know it isn't frozen since the blue animation at the bottom continues to happen but it never makes it way to the home screen. Anyone know how to fix this?
Click to expand...
Click to collapse
Ignore this post. Followed Joeathesist's post and let it sit a little big longer this time and it worked! Jelly Bean is now running
Hi everyone,
I bought a No.1 X2 (001mobilephone) about 3 months ago, I have tried every version I can of PC > Phone rooting software and .apk's plus tried using a few similar tools that use ADB. (inc kingoroot, kingroot (chinese), SRS, oneclickroot, towel, androidroot, etc)
I cannot get the phone rooted and I do not want to wait, phone-less, for a month (at least a month to send to the manufacturer who was supposed to have rooted before it was shipped - and who knows if they will send it again without root).
the phone (may?) seams to have partial root, when i installed led manager, and have since done a wipe, the led settings seamed to have stayed with my custom email and other notification colours.
Specs/software is:
Qualcomm MSM8916
android 4.4.4
Kernal 3.10.28
[email protected] #2
Thu Jan 29 09;58:34 cst 2015
Anyone able to help?
Thanks
Markatkins said:
Hi everyone,
I bought a No.1 X2 (001mobilephone) about 3 months ago, I have tried every version I can of PC > Phone rooting software and .apk's plus tried using a few similar tools that use ADB. (inc kingoroot, kingroot (chinese), SRS, oneclickroot, towel, androidroot, etc)
I cannot get the phone rooted and I do not want to wait, phone-less, for a month (at least a month to send to the manufacturer who was supposed to have rooted before it was shipped - and who knows if they will send it again without root).
the phone (may?) seams to have partial root, when i installed led manager, and have since done a wipe, the led settings seamed to have stayed with my custom email and other notification colours.
Specs/software is:
Qualcomm MSM8916
android 4.4.4
Kernal 3.10.28
[email protected] #2
Thu Jan 29 09;58:34 cst 2015
Anyone able to help?
Thanks
Click to expand...
Click to collapse
Chinaphonearena.com: Sponsor Forums Official No.1® Forum NO.1 X-Men X2 4G LTE rugged 3-proof Smartphone
Hi, same phone, same problem. The above site might be interesting for you. No.1 supplies Qualcomm software and the phone's firmware with a tutorial to root. I succeeded in putting firmware on a bricked X2, but still did not get root access. But I am a newby, so give it a try. Good luck
UNBRICK no.1 x2 using original ROM
Thanks for this, i now have access to the ROM, and if you can understand the instructions its possible to install the ROM again.
I just did this today, however its partially rooted, as was my phone when I received the X2.
I need to now try to use kitchen and a bunch of other tools as described here to try and install Su and/or root the rom: en.miui.com/thread-21539-1-1.html
if i am sucessful i will post instructions, for now here are clear instructions on how to (should work as tested on my x2) unbrick X2 with this software.
1. download this: "ht tps: SLASH SLASH drive DOT google DOT com SLASH file SLASH d SLASH 0ByeMRyNUHsNRdGc0Qk1jQlJIb3c SLASH view" (i have less than 10 posts so cannot type full url, replace SLASH SLASH with // and DOT with .)
2. extract the rar (download trial of winrar or similar to extract (noobs))
3. launch the setup.exe from the folder you extracted too. (remember where it is installed)
4. extract the X2.rar to a folder (new folder on desktop or my docs)
5. right click (win 7, 8 10) and run as admin (the installed program from desktop called "QMSCT")
6. open the "setup" menu in QMSCT and click "configuration"
7. make settings look like the picture in: "ht tp s: SLASH SLASH drive . google . com SLASH file SLASH d SLASH 0B2M8OmUI5XS-SGtudHYwS0tLZGc SLASH view?usp=sharing"
all check boxes and fixed options must be identical, i have highlighted red
8. insert (red again) the file names shown in the picture (they will be in the original extracted rar where you launched the setup program or in the directory you installed to).
9. in the bottom field locate the folder where you extracted the x2.rar, this folder location is the folder you must browse to and select in the bottom of the settings screen. Only care about the red markings i made, i will now tell you below how to get the information you cannot change yet in the settings.
10. first SAVE, exit the settings, then exit program.
11. plug in no.1 X2 Mobile, while phone on hold power until options appear, then hit restart, before it turns off and vibrates, hold down both volume buttons and then also press and hold power... do'nt let go until phone vibrates and turns on to a blank screen... sometimes it will restart, just do it over again and again until it boots up blank (screen has lit up back/grey)
12. when screen blank windows will install driver. NB: Unfortunatly i had issues here and it took a windows 10 tech preview install 10041 build x64 to do this, however it did not get fiddly i just had to try xppro, win 10x64 on a laptop and then my desktop to work it out, also I was following chinese instructions that had been translated and were not perfect to begin with. So any win 7, xp or 8 might need to source which driver to install from no.1. Windows 10 tech preview is free and can be put on another partition easily if you search (noob) on xda or google i am sure someone will have covered it.
13. unplug phone, launch QMSCT again as admin, go into settings and click "Start setup process" then click ok on dialogue box. now plug in phone and hold vol buttons again, then power and hold all 3 down until it reboots into the blank screen. if all works a port will be found (1-8 i think i saw in my many attempts) once it has found it and you see the information on the screen look similar to my screen shot, click on save. note your port will maybe differ, and if it does not work, restart application and phone again and repeat. when it saves, exit configuration, exit application and then you need to restart application
14. if all is right, plug in phone, hold the 3 buttons in order again, and the application will start flashing it. DONT UNPLUG UNTIL RED OR GREEN shown in app.
RED=fail - go back through my instructions and the supplied "flash tutorial.docx" in the RAR (you extracted this at the begining - the pictures may help more than the instructions they gave)
GREEN=Woohoo! all done, unplug phone and do the power button combo, it will restart (might need to do combo a few times)
NB: settings stay the same once this application is set up, so you do not need to go through all again in future, just launch app and then plug in phone and do 3 button combo.
I hope this helps, if you are good with CUSTOM ROM creation, feel free to see if you can get this rom rooted and flashed and tell me/readers of this forum... if anyone wants a real challenge, root this rom, make the kernal 64bit and not 32bit and then post here.... this is what I want to do eventually if i can work it out.
good luck any bricked x2 owners
Fixed X2 boot loop and not being recognised while bricked
Mjfh said:
Chinaphonearena.com: Sponsor Forums Official No.1® Forum NO.1 X-Men X2 4G LTE rugged 3-proof Smartphone
Hi, same phone, same problem. The above site might be interesting for you. No.1 supplies Qualcomm software and the phone's firmware with a tutorial to root. I succeeded in putting firmware on a bricked X2, but still did not get root access. But I am a newby, so give it a try. Good luck
Click to expand...
Click to collapse
Ok so if you are still bricked (as I temp was) use this program: qtadb . wordpress . com SLASH download.
it fixed my x2 which was in boot loop, could not use adb or the flash program to even see it, win 10 was not recognising anything driver wise.
just extract from the x2.rar with all the boot img etc: boot.img and recovery.img
locate most recent android sdk/platform tools folder when asked for it
click on the corresponding "flash recovery" in qtadb and locate the extracted image, do the same with the boot img tab and find your boot img
that's the order i did it in, i may have reset phone between them and cleared cache by holding vol+ and power and using boot loader. I had installed an msm8916 file to root, that apparently does not... ah well we live and learn.
looking for solution to turn that x2.rar into a rom.zip as kitchen does not work with it. maybe im doing something wrong?
anyway phone on again so the search continues...
X2 missfunctions.
Markatkins said:
Thanks for this, i now have access to the ROM, and if you can understand the instructions its possible to install the ROM again.
I attached a Word Document with information and questions about this X2 device, which is too hard to recover to update ... and an buch of missfunction. ( camera error : can't connect to the camera; 4G LTE does not function, only 3g; battery life normal as 2000 mAh; )
I expect your answer or comments very soon.
Best Regards.
tomas abrego garcia.
Click to expand...
Click to collapse
X2 reset successfuly - EASY way
I attach PDF files with instructions to reset the phone X2.
I expect very soon someone help us to ROOT it !!!!
Best Regards.
help!!
Hi
This forum is the closest thing I have found which might help me in my problem to fix my 1 week old X2.
I really enjoyed using it - I got it 2 weeks ago - and it was working fine for all the week then last weekend I had a few apps running and the screen froze. I rebooted the phone but it just stayed black and never came on again. It is a stock standard phone - and it has not been rooted or modified in any way. Someone suggested removig the battery then refitting it.
How is that done?
Is that a good thing to do?
What else can I try?
Has anybody any idea on what might have caused this?
I'm stuck!
Jeff_T said:
Hi
This forum is the closest thing I have found which might help me in my problem to fix my 1 week old X2.
I really enjoyed using it - I got it 2 weeks ago - and it was working fine for all the week then last weekend I had a few apps running and the screen froze. I rebooted the phone but it just stayed black and never came on again. It is a stock standard phone - and it has not been rooted or modified in any way. Someone suggested removig the battery then refitting it.
How is that done?
Is that a good thing to do?
What else can I try?
Has anybody any idea on what might have caused this?
I'm stuck!
Click to expand...
Click to collapse
Hi,
I have one as well: it is indeed fun to play with but it is not reliable. I had multiple issues with it in the past months. Therefor my advice is: send it back and claim your guarantee (especially if you want to use it as your primary phone). Otherwise use the unbrick advice from markatkins earlier in this thread (but you have to feel secure with android)
good luck
Mjfh said:
Hi,
I have one as well: it is indeed fun to play with but it is not reliable. I had multiple issues with it in the past months. Therefor my advice is: send it back and claim your guarantee (especially if you want to use it as your primary phone). Otherwise use the unbrick advice from markatkins earlier in this thread (but you have to feel secure with android)
good luck
Click to expand...
Click to collapse
Thanks Mjfh
Looks like I have to pay a premium on the freight via courier to get it back to China. The local postal service won't take it because it contains a (non-removable) Lithium battery.. I'm not sure about unbricking it as it seems it is a very complicated process - and seeing that it seems completely dead -(not any signs of life, no lights, no screen) do you thnk it is just a matter of a firmware reset? If I attempt to unbrick it - I lose the warranty right?
So my best bet I think is to depart with several tens of dollars for the freight and demand a replacement that will not bug out inside 2 weeks.
issue, try this
Jeff_T said:
Thanks Mjfh
Looks like I have to pay a premium on the freight via courier to get it back to China. The local postal service won't take it because it contains a (non-removable) Lithium battery.. I'm not sure about unbricking it as it seems it is a very complicated process - and seeing that it seems completely dead -(not any signs of life, no lights, no screen) do you thnk it is just a matter of a firmware reset? If I attempt to unbrick it - I lose the warranty right?
So my best bet I think is to depart with several tens of dollars for the freight and demand a replacement that will not bug out inside 2 weeks.
Click to expand...
Click to collapse
Look I had this issue regarding dead and not turning on... sometimes charging it for several hours and it would just come back to life, i believe it is a battery issue, reading battery (stock rom) and when it may say 15% for example, the battery is actually empty and it dies, the charging should make display turn on but does not for a long, long time.
if this does not work, hold down vol up or vol down plus power button, this can breath life into it (sometimes both up and down plus power) remember press all at exactly same time and hold for 10 seconds at least for reset (unless it comes back before 10 seconds)
been a while since i held my phone so check top of page for my instructions as it is in there
best of luck
markatkins
toomax.mx said:
Markatkins said:
Thanks for this, i now have access to the ROM, and if you can understand the instructions its possible to install the ROM again.
I attached a Word Document with information and questions about this X2 device, which is too hard to recover to update ... and an buch of missfunction. ( camera error : can't connect to the camera; 4G LTE does not function, only 3g; battery life normal as 2000 mAh; )
I expect your answer or comments very soon.
Best Regards.
tomas abrego garcia.
Click to expand...
Click to collapse
Nice work
you need to install all ports to make this work well... i am going off memory from over 2 months ago but if you can revisit my instructions and check how many ports i have to setup, it should get you a green light, i could see an error in a photo at bottom of word... something about ports, this may confirm my theory.
I will answer all the questions soon, once I have a phone in my hand (give me 2 weeks, and tinker while you wait )
hope this helps
Click to expand...
Click to collapse
Jeff_T said:
Thanks Mjfh
Looks like I have to pay a premium on the freight via courier to get it back to China. The local postal service won't take it because it contains a (non-removable) Lithium battery.. I'm not sure about unbricking it as it seems it is a very complicated process - and seeing that it seems completely dead -(not any signs of life, no lights, no screen) do you thnk it is just a matter of a firmware reset? If I attempt to unbrick it - I lose the warranty right?
So my best bet I think is to depart with several tens of dollars for the freight and demand a replacement that will not bug out inside 2 weeks.
Click to expand...
Click to collapse
just do what I did, post and tell them battery removed (tick the plane and ship boxes - should be on form for international post)
I looked up why battery is now banned, its stupid... thanks to the more dangerous li-pol battery types, starting fires in planes and stuff like exploding, the air transport authority decided to ban the li-pol (explodes and loads of fires every year) and in that they included the more reliable (not dangerous and very few accidents worldwide) li-ion which is what is in your phone... so batterys in general.
play dum, say no battery in phone and tick that box for sea/ship shipping
remember this is a 80 degree c proof phone, pressure proof and should be able to contain the fire, but a fire wont start...
otherwise pay AUD100 (convert to GBP or USD for a similar horrific amount no one should pay)
if your phone does explode or cause a fire in transit... i am not accountable, you do this at your own risk and risk of being fined etc blah blah... read about % of fires from li-pol and li-ion, you will see the chance is slim, slimmer once sealed in a phone that will give it a heat proof case to try and get past plus minimal air to fuel a fire... good luck fixing or sending
I found an app called KINGROOT and worked like a charm. It rooted my No.1 Xmen X2 with just one click, it even fix the Kitkat SD write problem in the process.
I had to erase the SD card after the rooting process for the fix to work and after the root, had to reboot the phone 2 times. Everything is working super fine so far. Hope this work for everyone!
Kingroot V4.5
http://forum.xda-developers.com/devdb/project/dl/?id=14250
Which exact rom version do you use ?
Is GPS working?
BR
Trying new root version...
denispunk said:
I found an app called KINGROOT and worked like a charm. It rooted my No.1 Xmen X2 with just one click, it even fix the Kitkat SD write problem in the process.
I had to erase the SD card after the rooting process for the fix to work and after the root, had to reboot the phone 2 times. Everything is working super fine so far. Hope this work for everyone!
Kingroot V4.5
http://forum.xda-developers.com/devdb/project/dl/?id=14250
Click to expand...
Click to collapse
I have just tested the newest software from kingroot as advised released by denispunk, I am amazed as I only downloaded the previous version a few weeks ago, no luck with the old version of "new_kingroot...", however I may be in a slightly different position to others as my phone seams to have an issue locked in (despite flashing and wipe of partition) where it has a partial root access of some form, so trying this now......................
Tried 2 times and failed, I want to ask all reading this to please download (rename from .zip to .apk) and attempt root on their x2 or x6800. if you fail click on the huge submit button as I have been doing this for some time in the hope that they would see demand and accelerate the process of making a workaround.
For all looking (that search for root x6800 online ) this should work the same % for anyone with the no.1 x6800 and the x2 [I have the X2 and got money back from insurance claim, so I also have x6800 on the way ] because the x2 and x6800 are the same rom from what I have researched, the only difference is the micro sd capacity, the 4g bands supported and a huge 6000mha battery in the x6800. most components otherwise are identical.
All reading please have a go...
if you are reading this you have an x2 or x6800 or know someone who does...
if your not very experienced or if you are experienced in ROM work, try point 1 and then try point 2 below, but please just do point 1 if nothing else
1) email No.1 and "beg" for a android 5.0/64bit kernel ROM for the x2 and x6800 to be released - I have done this and want to encourage you all to help me force the company to meet consumer demand, by setting a consumer demand. This 64bit update would increase the phones potential as it has a 64bit CPU, it currently runs 32 bit software which is slowing it down.
once done read point 2
2) I wanted to see if some experienced persons could visit the en.no1phone.cc site and download the M2 firmware (not a spelling mistake) as this device and the x2 use the same unusual ROM's which look similar in layout. my hope is we can bind parts from the 2 ROM's together to get a 64bit android version onto the x2/x6800... please understand I do know this will need work and will most likely not work ever but with the unique rom types I figure there is no harm in trying and someone might have the ability to open them and do some magic.
now the phones are physically different but No.1 use the same basic layout in their ROM's and the most basic possible stock android with nothing but background pictures added.
my hope, from what I can see in the files of the two ROM's, is that we can merge/build the OS, kernal and some of the information from the M2 ROM into the x2 ROM (I have supplied the x2 rom in the top of this post on page 1) and hope that its basic enough to maybe work with some tweaking, I know the CPU is different and that I am explaining this simply like a drag and drop, but if it does work we can get 64 bit software for our CPU's
if all else fails we can hope No.1 release what we ask for, and you can flash the original x2 rom back onto the device until they release it or someone on here gets through the ROMS and makes us our own.
denispunk said:
I found an app called KINGROOT and worked like a charm. It rooted my No.1 Xmen X2 with just one click, it even fix the Kitkat SD write problem in the process.
I had to erase the SD card after the rooting process for the fix to work and after the root, had to reboot the phone 2 times. Everything is working super fine so far. Hope this work for everyone!
Kingroot V4.5
http://forum.xda-developers.com/devdb/project/dl/?id=14250
Click to expand...
Click to collapse
Root worked
I finally sourced a slightly newer .apk and root worked. Kingroot will root no.1 x2 or no.1 x6800. So far used it to access battery stats with Xposed and installed one power guard to lower CPU speed to gain more battery. The device is very fluid still on 533mhz in power save CPU mode with I/O scheduler in "row"
I advise anyone looking for this phone rooted to visit the official www.kingroot.net site
Great news everybody, since my post asking for us to all send kingroot requests to support our device for root access, the number of requests jumped almost 30 points and they listened! Kingroot responded and now...
Kingroot.net will root the no.1 x2!
If you just landed here looking for the software to root the X2 or X6800 from No.1, please help us make this phone better, this forum helped get kingroot.net to enable root for the X2 so help us and say thank you by sending an email to no.1 regarding getting lollipop on the X2 and X6800.
You just need to...
Email: [email protected]
Skype: quecc1989
Or MSN: [email protected]
Ask for lollipop ROM to be made for the x2 and the x6800 and say it will make the phone faster and have a better battery life. Copy that if you like
Update on this: not only will the software give the phone a bit of a boost in power, it should improve battery life and I completely failed to mention before that we will have faster app boot times as well because we will get access to ART instead of Dalvik (Currently I cannot find a way to run ART in KitKat without factory resetting to get out of the nice boot loop it sticks me in).
For those unaware of what I am going on about, Dalvik is the runtime android is moving away from because it has to decompress each installed app before it runs, ART (android run time) installs app's already decompressed (more space used on install but fast launch). I find the x2's 8GB is plenty of internal space for applications so let's harass no.1 sales email and Facebook/twitter/google+until we get lollipop.
Official no.1 site is: http://en.001phone.cn
They use a picture for contact info but feel free to click on my links above for msn, Skype etc
Sorry if this was a ramble, but power of word is going to be easier than us taking and editing ROM's or making ROM's to get lollipop... If we harras them endlessly they will fold and build it for the phones and all it takes is one email each... Maybe a followup each too
toomax.mx said:
I expect very soon someone help us to ROOT it !!!!
Best Regards.
Click to expand...
Click to collapse
I hope the same for the No.1 X6800
forum.xda-developers.com/general/help/root-1-x6800-rugged-ip-68-phablet-china-t3254950
Not much people know the No.1 smartphones (the rugged ones are awesome for the price).
Update: I rooted the No.1 X6800 with 'NewKingRoot v4.62' app and after that buy the Super-SuMe-pro' app to keep it 'trustfully rooted and with SuperSU'.
When device is off, and I press power button and volume up button. Then I get a bootloader that can boot from MicroSD card.
So place the compatible Rom on MicroSD and re flash it.
This works for me with original x6800 rom on my x6800 phablet.
My boss recently acquired an S9+ and wanted to factory reset it maker sure it was clean before usage. Being 'the tech guy' it's been handed over to me to sort out. However there's something very weird with this phone. There's no Play Store, for a start. It's not disabled in the App settings, it's just not there at all. I tried installing an APK of the latest version, it installs and acts like it's updating an existing app, but when I try and launch the program is says there isn't an app installed to perform that operation.
I decided to just wipe the thing and start from scratch, but there's no option anywhere to perform a factory reset. NOTHING. No options in the settings and nothing in recovery (photo added for proof).
So I've decided to adopt a scorched earth policy and root the thing and install a fresh vanilla ROM. Except I CAN'T because I can't enable OEM unlocking. I've gotten into Developer option no problem, and OEM unlocking is there. I toggle the switch, press enable, press the blue Delete All button and... nothing. Well, not quite. Very briefly a box will pop up that bottom saying Reset but will disappear immediately. I'm utterly stumped!
Does anyone have any suggestions?
Spoiler: Picture
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Might be a rootkit... pre Android 9 versions are suspectable to ones that can infect more than the userdata partition. They need to be reflashed to eliminate it.
blackhawk said:
Might be a rootkit... pre Android 9 versions are suspectable to ones that can infect more than the userdata partition. They need to be reflashed to eliminate it.
Click to expand...
Click to collapse
Thank you for the reply. Any suggestions on how I might do that without OEM unlocking access?
Trism said:
Thank you for the reply. Any suggestions on how I might do that without OEM unlocking access?
Click to expand...
Click to collapse
May be no need to reflash if this is a normal state ie no rootkit or corruption:
How to Fix Missing OEM Unlock in Samsung Devices
In this tutorial, we have shared four methods that will help you to fix the missing OEM Unlock option in various Samsung devices and tablets.
www.droidwin.com
blackhawk said:
May be no need to reflash if this is a normal state ie no rootkit or corruption:
How to Fix Missing OEM Unlock in Samsung Devices
In this tutorial, we have shared four methods that will help you to fix the missing OEM Unlock option in various Samsung devices and tablets.
www.droidwin.com
Click to expand...
Click to collapse
Thanks again for the reply. I've just reflashed the latest Android version for this model (currently on 10) which passed successfully according to ODIN, however it's still exactly the same with the phone. No Play Store, no factory reset, unable to enable OEM unlock.
I'm going to attempt to install Android 9 instead and see if that works.
Just a matter of curiosity can you post s screen shot of you download ( odin ) mode
if your on latest firmware you can't downgrade to ver 9
spawnlives said:
Just a matter of curiosity can you post s screen shot of you download ( odin ) mode
if your on latest firmware you can't downgrade to ver 9
Click to expand...
Click to collapse
Don't have it to hand right this second, is the info you need in the picture I attached in my first post?
Trism said:
Don't have it to hand right this second, is the info you need in the picture I attached in my first post?
Click to expand...
Click to collapse
No
Download mode ( on your phone ) is the screen where you can flashed with odin.
No rush, but it can tell a bit more information.
Download Mode does not seem give a great deal of information. Is this the right screen?
Spoiler: Downloading mode
Trism said:
Download Mode does not seem give a great deal of information. Is this the right screen?
Spoiler: Downloading mode
View attachment 5392683
Click to expand...
Click to collapse
It's the right screen
Did you use recovery to boot into download mode or did you use the power/vol down/bixby buttons when booting phone.
Also when you flashed the phone with stock firmware did you do a clean install. ie: used the csc file.
and did you boss say if it's a new or second hand phone.
spawnlives said:
It's the right screen
Did you use recovery to boot into download mode or did you use the power/vol down/bixby buttons when booting phone.
Also when you flashed the phone with stock firmware did you do a clean install. ie: used the csc file.
and did you boss say if it's a new or second hand phone.
Click to expand...
Click to collapse
It's very much second hand. And I think I've partially solved the problem.
I did a full reinstall using Odin and did a Nand wipe in the process. This finally made an actually full reset of the phone as it took me through the setup process. However, it automatically install a Knox profile that locks it into Retail Mode, so I guess this is an ex-display unit.
My new issue is getting out of Retail Mode. If I open the app for that it makes me choose which store the phone came from, then it downloads a 9GB file that sets up the display demo. I've found the passcode (5444) to get into the Retail Mode app, however once it begins working it completely disables the keyboard, so I can't go back into the app to disable it again. Its all very annoying.
*EDIT* Well, I got around that and disabled Retailed Mode.... and the original problems are still there. No Play Store, no Factory Reset options, can't unlock OEM.
I have now actually found that the Play Store is installed on the device, but it's disabled and pressing Enable does nothing. I'm totally stumped.
Here's the shot of the download mode screen you asked for. No idea if it will help now, but I'm willing to try anything.
Spoiler: Downloading mode
Trism said:
It's very much second hand. And I think I've partially solved the problem.
I did a full reinstall using Odin and did a Nand wipe in the process. This finally made an actually full reset of the phone as it took me through the setup process. However, it automatically install a Knox profile that locks it into Retail Mode, so I guess this is an ex-display unit.
My new issue is getting out of Retail Mode. If I open the app for that it makes me choose which store the phone came from, then it downloads a 9GB file that sets up the display demo. I've found the passcode (5444) to get into the Retail Mode app, however once it begins working it completely disables the keyboard, so I can't go back into the app to disable it again. Its all very annoying.
*EDIT* Well, I got around that and disabled Retailed Mode.... and the original problems are still there. No Play Store, no Factory Reset options, can't unlock OEM.
I have now actually found that the Play Store is installed on the device, but it's disabled and pressing Enable does nothing. I'm totally stumped.
Here's the shot of the download mode screen you asked for. No idea if it will help now, but I'm willing to try anything.
Spoiler: Downloading mode
View attachment 5393323
Click to expand...
Click to collapse
I don' know to much about the retail mode except for the option in developer menu. I have never tried to turn it on/off.
Amonst other things from your download screen your OEM ( bootloader ) is on. Miight be because of the retail mode.
In regards to trying to enable play store maybe try using adb to enable it.
While l could be wrong i was iniatally thinking about some sort of MDM lock which will prevent you from doing stuff to your phone.
spawnlives said:
I don' know to much about the retail mode except for the option in developer menu. I have never tried to turn it on/off.
Amonst other things from your download screen your OEM ( bootloader ) is on. Miight be because of the retail mode.
In regards to trying to enable play store maybe try using adb to enable it.
While l could be wrong i was iniatally thinking about some sort of MDM lock which will prevent you from doing stuff to your phone.
Click to expand...
Click to collapse
Hm, I didn't know you could enable things like that through ABD. I'll look into that, thank you.
*EDIT* Holy crap that actually did it! I uninstalled then reinstalled Play Store through ADB and it's now enabled! Thank you, dude. I really appreciate your help!
So can you download, use apps from playstore.
spawnlives said:
So can you download, use apps from playstore.
Click to expand...
Click to collapse
Yep. Still can't factory reset, but the Play Store is working as expected. Installed a few things and reloaded several times. Everything is still there.
Trism said:
Hm, I didn't know you could enable things like that through ABD. I'll look into that, thank you.
*EDIT* Holy crap that actually did it! I uninstalled then reinstalled Play Store through ADB and it's now enabled! Thank you, dude. I really appreciate your help!
Click to expand...
Click to collapse
@Trism you literally saved my life, I had the same issue and resolved throug adb. Still disapperared the reset functions.
I bought this motherboard in china as used but it's from UK, a the first start enrolled with knox.
I think it was a display unit, not a live demo unit but a real demo unit with special enrollment.
Thank you very much
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
Give me some time working on it , u have spent so much time on this , can u spend little more . I may help u so let me do some research and come to u
DIVASM said:
Give me some time working on it , u have spent so much time on this , can u spend little more . I may help u so let me do some research and come to u
Click to expand...
Click to collapse
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy
Click to expand...
Click to collapse
stop_making_things_worse said:
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
can u try this
, if it is not wokring tell me
That is one of many videos and posts I have already seen and followed. The fundamental issue is not being able to unlock the bootloader in developer options. No amount of dancing gets "OEM Unlock" to display for me. Other threads indicate the 227U specifically does not have a way to unlock the bootloader, while 225/227 do.
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Make Self Root And Try
I have same frustration nothing is getting the oem to show up. I have some know how's with rooting ect my other tablet is my Frankenstein lol but unfortunately it's not one of these tabs. Any word on a fix ?
wesmat95 said:
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
View attachment 5936903
Click to expand...
Click to collapse
Hm interesting, if you boot to download mode, are you able to unlock the bootloader there?
wesmat95 said:
I have the SM-T227U from Rogers and I have the OEM Unlocking option by default. I am on TP1A.220624.014.T227UVLS5DWC5 build number.
Click to expand...
Click to collapse
This is a very interesting piece of information. I believe we can flash official firmware from samfw without worry, so I will try this route, however this specific build isn't available that I can see (it's old, they only have newest I guess?). I'll try the version they have and cross my fingers that it works and my SIM still works.
You did not have to do any steps, correct? OEM Unlock option showed without having to do the whole date/time dance?
stop_making_things_worse said:
This is a very interesting piece of information. I believe we can flash official firmware from samfw without worry, so I will try this route, however this specific build isn't available that I can see (it's old, they only have newest I guess?). I'll try the version they have and cross my fingers that it works and my SIM still works.
You did not have to do any steps, correct? OEM Unlock option showed without having to do the whole date/time dance?
Click to expand...
Click to collapse
No I did not. It just appeared in developer options. I just got this tablet about 7 months ago. Just got it out to do some development on it. I do have to mention that it is on the latest One UI update that appeared on my device a couple days ago. I did however notice that there are newer updates on SAMFW for it not available on my device. Maybe Rogers blocking update? Don't know. Found it wierd.
Wish39 said:
Hm interesting, if you boot to download mode, are you able to unlock the bootloader there?
Click to expand...
Click to collapse
Technically I should be able to. Haven't done it yet though.
Having the same problem. Everything I've tried so far can't even get to the OEM unlock to appear in debug. Pretty much hobbles doing anything. Is the freebie SM-T227U with android 13. Box has date of 05/09/23 so really new. Hardware revision 1.0 and SW is T227USQU4CWC2. Maybe a way to force flash older firmware and make OEM unlock work?
stop_making_things_worse said:
Other threads indicate the 227U specifically does not have a way to unlock the bootloader, while 225/227 do.
Click to expand...
Click to collapse
Really going to piss me off if true.
popeye2014 said:
Having the same problem. Everything I've tried so far can't even get to the OEM unlock to appear in debug. Pretty much hobbles doing anything. Is the freebie SM-T227U with android 13. Box has date of 05/09/23 so really new. Hardware revision 1.0 and SW is T227USQU4CWC2. Maybe a way to force flash older firmware and make OEM unlock work?
Click to expand...
Click to collapse
You could try flashing the Canadian T227U firmware using patched Odin, as it apparently can be bootloader unlocked.
We have AT&T and Verizon to thank for making Samsung permalock the devices they sell in the US.
Wish39 said:
You could try flashing the Canadian T227U firmware using patched Odin, as it apparently can be bootloader unlocked.
We have AT&T and Verizon to thank for making Samsung permalock the devices they sell in the US.
Click to expand...
Click to collapse
Thanks probably will try something like that. At this point might as well try even if end up bricking it. Really want it unlocked and the ability to use other carriers. Last thing I need is another tablet with just wifi. which is what it pretty much is being locked.
wesmat95 said:
Technically I should be able to. Haven't done it yet though.
Click to expand...
Click to collapse
I can't even get to bootloader. When it inters fastboot it just says interning fast boot and never actually does. I have no idea why
bencinilife said:
I can't even get to bootloader. When it inters fastboot it just says interning fast boot and never actually does. I have no idea why
Click to expand...
Click to collapse
Fastboot doesn't exist on Samsungs. They replace it with Download mode
stop_making_things_worse said:
I'm going to apologize up front for the tone of this post but I am so full of rage at this point that I just need to scream at something.
Goal: I am trying to get Android Auto to run on my new (free with a new line of service!) A7 Lite SM-T227U tablet. That is all. That is the fundamental only thing I want to do.
Quick Narrative: I did not even consider that this wouldn't be possible when I got the tablet. Like, please understand that It didn't even cross my mind that this would not be possible out of the box. The fact that Android Auto does not work by default on this device is absolutely insane. That it is not even in the app store is mind boggling. Google can blow me just for that. They have taken away my own decision making powers and made the decision for me. That is the most infuriating way to develop products for users. Stop making choices for me. So I downloaded a copy of the APK from somewhere (this is something I would normally never do because who knows what that APK actually is. I plug it into my car, big red screen, error code 22. Google telling me to go suck it. Rage.
The Final Problem: So in order to solve for the lack of Android Auto support, I apparenlty have to ultimately root the tablet. No matter which recipe I follow, doing a whole lot of firmware nonsense and romm'ing or whatever, or just going straight to systemize apps and installing the downloaded Auto APK I got as a system app - either way - rooting is required. Apparently that's not possible because the dev option for OEM Unlock doesn't exist on this specific variant of this model of devices.
I have tried the juggling bull**** options that is apparently standard on many Samsung devices, you know the dance: set the date back 8 days, or 10 days, stand on your head, rub your belly, dev aoptions on dev options off, etc etc.
No joy.
Is this ONE thing I want, using Android Auto on A7 Lite SM-T227U literally not possible specifically and only because I cannot root this device which is specifically and only because I cannot unlock the bootloader?
Should I just start buying Apple products?
Click to expand...
Click to collapse
I am literally going threw the same thing! i see everyone with different variants of the a7 lite doing this all day. I've tried everything to get the OEM Unlock option to pop up and literally nothing! Never ever thought it would just not be possible out the gate. Ive got the T227USQS5CWD1
Hardxcore_Cary said:
Never ever thought it would just not be possible out the gate.
Click to expand...
Click to collapse
Then you must not have purchased or used any North American Samsung devices in the past 5+ years.
Another user with a Canadian model reported having OEM Unlock (although I don't believe they've clarified whether they could actually do the BL unlock via Download mode).
So you could try flashing Canadian firmware
Update trying to flash Canadian FW to US (TMOBILE) tab:
Pulled both major versions up on samfw and tried differnet things. As a preface to outlining the issues I am facing, I have to state two things: 1) I have no idea what these files actually are. but 2) If I flash BL+AP+CP+CSC files that are for my carrier, it works fine (I've had to unbrick this by doing this several times). So, I can and have successfully flashed what is basically already the official FW for my device (SM-T227U_TMB_T227USQS5CWD1_fac <---this succeeds in ODIN).
I have now tried SM-T227U_RWC_T227UVLS5DWC5 and SM-T227U_RWC_T227UVLU4DWC2. I get different errors based on how I go about it, but errors nonetheless.
If I just blanket try BL+AP+CP+CSC I get
Code:
Non-KNL image not allowed: pit
If I use the BL+CP+CSC from my carrier and only the AP from RWC (I assume this is rogers), I get
Code:
Non-KNL Image not allowed: boot
For T227U_RWC_T227UVLU4DWC2 there's an additional error message of
Code:
Fused 5 > Binary 4.
RP Check Error: boot
Non-KNL Image not allowed: boot
I assume this is because the fw version doesn't match the "fused" version or something? I dunno.
Just reporting my findings.
EDIT: Upon further inspection of all the FW offerings, it appears only T227UVLS5DWC5 (Canada), T227USQS5CWD1 (US), and T227USQU5CWD2 (US) are even remotely viable due to device requiring U>=5 (sw/ver, bin value, whatever you want to call it). Unless there's a way around this?
I have validated that I can flash BOTH US F/Ws successfully, even though one is for a different carrier in the US. But the canadian version is a no-go due to the pit/boot errors noted above.