Hey Guys,
tried to install LineageOS on my mothers tablet, but forgot to unlock bootloader first, so i got a softbricked device like some other guys here.
Because i haven´t found a solution/tutorial here, i tried some things out and now i got a working device
Unbrick The Brick
I found a version in this forum, which installs a ofw -> https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
My Device was connected in this mode and via cmd : "adb devices" it was listet
{
"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"
}
After unzipping 0.rar, i startet a cmd as administrator, navigated with cd to the unziped folder and startet "flashall.cmd"
The Device starts again
Install OFW
Unfortunetly the Unblock Bootloader APK from Asus ended up with an error , i tried a lot with adb install *.apk and so on, but nothing worked out... Therefore i installed the latest OFW
You need an SD-Card and the latest Version (https://www.asus.com/Tablets/ASUS_MeMO_Pad_FHD_10_ME302KL/HelpDesk_Download/)
-> For me it is the "ASUS MEMo Pad FHD 10 LTE Firmware: V10.10.3.39 Only for WW SKU (Android 4.2.2)"
Copy the unzipped zip (you will see what i mean) to the SD-Card and unname it to "APQ8064_SDUPDATE.zip"
Insert the micro SD card into the tablet.
Turn off the tablet.
Press and hold Volume Up + Power Key, wait until the bootloader logo appears, and then the FW update process begins. (if this don´t work out try the APK "Recovery Reboot")
After the completion the device will automatically reboot.
Perform the factory data reset.
IUnlock Bootloader with the official APK
-> https://www.asus.com/de/supportonly/ASUS MeMO Pad FHD 10 LTE/HelpDesk_Download/ -> Utilities -> Expand -> "Unlock Device App"
Install TWRP
-> https://forum.xda-developers.com/android/general/recovery-twrp-3-1-1-0-asus-me302kl-t3609759
Install LineAgeOS
-> https://forum.xda-developers.com/an.../rom-8-0-0-lineageos-15-0-unofficial-t3693838
Enjoy
I had some hope when I saw this thread. I had problems with the bootloader unlock too.
slungshot said:
I had problems with the bootloader unlock too.
Click to expand...
Click to collapse
And it helped?
My advice to anyone trying to revive this old tablet is to just buy a new one, no matter what the cost and you will come out ahead in comparison to time wasted trying to resurrect this old beast. Still if you are like me and perhaps when you arrive here are "already in way too deep", here are some hints to get you going. I'm 2 weeks into playing with this thing but making good progress. Wishing I'd just bought a new one but since I usually forget everything I learned dealing with ROM builds a few weeks after I set it aside,I can't say I learned a valuable lesson so I'm not sure of the benefit.
First of all, to ensure you don't brick this thing, be sure to RESTORE TO FACTORY before unlocking. Then once set to factory defaults and you are configuring it anew again, when you get to the screen asking to sign into Google, then don't do it because if you do, when you run the unlock routine it will go into a loop asking for your Google ID and password. Then when you sideload in the Assus unlock app and also accept any upgrades that Asus provides if at this point you have never logged into Google, the only requirement of this unlock routine is that you have a working wifi accessed so you will never get into the Google ID loop if you don't have a Google sign-in account set up.
So, I've loaded every version, evaluated them and rejected all but 14.1 due to some quirk or another. My mistake was loading multiple zips after the unnlock (including Gapps up front, a no-no in my opinion) and this has left me yet to load any of the Gappas package yet, discovering that is what gave me my black screen initially. I now have a full suite of mapping software loaded and working plus many basic language tools and other apps that support traveling and using this device as a guide. I have side loaded about 25 apps and all is well so far without the play store. I have the GPS working (couldn't get it to work in 13.x and 15.x versions) and additionally I was able to load Magisk systemless, Xposed V25 systemless, XprivacyLUA and a long list of Xposed modules that all work perfectly, plus I have a functional root. I haven't tried any super secure apps like banking because I haven't even set up playstore. So right now I have a great functioning device that is not so Googled-up. I am not sure if I will load the 7.1 Gapps at this point now but I plan to get everything working on this device I can without Google Playstore and the other Google suite and see just how far I can get without Google apps. I do miss the voice typing, however.
Another thing that will get you confused with this tablet is the first time after flashing it with the TWRP recovery and just as you enter fastboot reboot on your computer and press the enter key for the very first time, you have to hold in the power button and up-volume button on the tablet at the same time you reboot with fastboot and if you don't when you reboot after the flash of the new recovery, the stock ROM will revert the TWRP recovery.img back to stock. I know, it sounds hard to believe but if you flash it and don't get the TWRP menu on the next recovery boot, this is what happened.
https://w3bsit3-dns.com/forum/index.php?showtopic=545744&st=2260
link not working
Related
Hi there, first of all I need to say that I'm sorry if I started this topic in the wrong section, second of all sorry for my english. Hope that I will be undrestood.
On my Nexus 4, I was running CM 11 custom ROM, and I've heard about the brand new one named Lollipop 5.0 . I've found Mako build for that new ROM and tryed to flash it via Rom Manager (Play Store). It runned smoth without any issues even if it's just an alpha release. But one day I've checked my storage tab, seen there that almost half of entire memory it was full, and I didn't had than just a few low space requiered apps. I tough about it and I realised that Lollipop ROM was installed OVER CM 11, of course not the ROM by itself but even if it wiped all data before to install the Lollipop, all junk stuff from CM 11 remain there.
So i wanted to reinstall a fresh copy of that Lollypop by using Nexus Toolkit.
Things would have been fine if my computer suddenly restarted while processing the flashing ROM, right after it wiped everything or something like that. Bad luck, huh?
So now I've got a soft bricked Nexus 4, where bootloader apparently still works but without recovery wich now it's replaced by and android dead icon and over that big red triangle, and when pressing the correct combination of volume + power buttons should give me fastboot, instead of that I'm stuck on "Download Mode". One more thing I forgot to mention, If I'll boot up device and run straight without pressing nothing, it will pop out the Google loading screen and it will stuck there, doing nothing.
{
"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"
}
I've read many threads about how to unbrick devices. Still got no answer because they refer at other soft brick posibilities, that includes pushing backups or what requires to simply flash them by fastboot or ADB, the problem here is that those posibilities will be great if I CAN get acces to my phone, what that means is I cannot run "USB debugging" to get my device being recognized by computer in this dead stage. Even my drivers are installed and "Download Mode" is active where should, as I read, grant me the acces to device even if it's not waked up completely. And second option to unbrick it leads me to the recovery mode (wich is dead) and restore from there a previous backup, and even if I had access to it, I DON'T have a backup.
So the big question for you guys about this annoying mishap: "Is there still a possibility to push files from computer to device, or I need to visit an authorized service?"
Thank you in advance. Peace.
Cosmin Petrisor said:
Hi there, first of all I need to say that I'm sorry if I started this topic in the wrong section, second of all sorry for my english. Hope that I will be undrestood.
On my Nexus 4, I was running CM 11 custom ROM, and I've heard about the brand new one named Lollipop 5.0 . I've found Mako build for that new ROM and tryed to flash it via Rom Manager (Play Store). It runned smoth without any issues even if it's just an alpha release. But one day I've checked my storage tab, seen there that almost half of entire memory it was full, and I didn't had than just a few low space requiered apps. I tough about it and I realised that Lollipop ROM was installed OVER CM 11, of course not the ROM by itself but even if it wiped all data before to install the Lollipop, all junk stuff from CM 11 remain there.
So i wanted to reinstall a fresh copy of that Lollypop by using Nexus Toolkit.
Things would have been fine if my computer suddenly restarted while processing the flashing ROM, right after it wiped everything or something like that. Bad luck, huh?
So now I've got a soft bricked Nexus 4, where bootloader apparently still works but without recovery wich now it's replaced by and android dead icon and over that big red triangle, and when pressing the correct combination of volume + power buttons should give me fastboot, instead of that I'm stuck on "Download Mode". One more thing I forgot to mention, If I'll boot up device and run straight without pressing nothing, it will pop out the Google loading screen and it will stuck there, doing nothing.
View attachment 2999210
I've read many threads about how to unbrick devices. Still got no answer because they refer at other soft brick posibilities, that includes pushing backups or what requires to simply flash them by fastboot or ADB, the problem here is that those posibilities will be great if I CAN get acces to my phone, what that means is I cannot run "USB debugging" to get my device being recognized by computer in this dead stage. Even my drivers are installed and "Download Mode" is active where should, as I read, grant me the acces to device even if it's not waked up completely. And second option to unbrick it leads me to the recovery mode (wich is dead) and restore from there a previous backup, and even if I had access to it, I DON'T have a backup.
So the big question for you guys about this annoying mishap: "Is there still a possibility to push files from computer to device, or I need to visit an authorized service?"
Thank you in advance. Peace.
Click to expand...
Click to collapse
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
3/4/15 NEW HOWTO ROOT & install TWRP on DL701Q/DigiLand 7" Tablet 4.4.2 KitKat
Ok, So you got your new Super Cheapo MTK8127 quad core Tablet from BestBuy or some other overpriced electronics emporium and want to install root and a custom recovery So it won't suck nearly as bad
Feeling hungry but don't wanna feed yourself??? Open wide......Here comes the airplane requesting permission to land
The Following procedure may "BRICK" your tablet and wipe your porn....You do so at your own risk, Neither Kneee or his lawyer claim to know ANYTHING about android....or anything else for that matter
THIS GUIDE WILL WIPE YOUR PORN!!!
If you've ever seen THIS:http://forum.xda-developers.com/chef-central/android/root-dl701q-install-twrp-touch-recovery-t2980339thread, You know that "iRoot/vRoot no longer works since updating to kitkat. I've BUNGLED my way into a solution, Hope it helps you too.....
THIS GUIDE ASSUMES YOU KNOW HOW TO USE ADB AND FASTBOOT (ENABLE USB DEBUGGING)OR AT LEAST KNOW WHAT THEY ARE AND DON'T SUFFER FROM GOOGLEPHOBIA
#1 Making a backup of this crap software when ADB , FASTBOOT and SP flash tool are working correctly is pointless (IMHO) (inm
Here's Everything you should need:
Stock ROM COURTESY...THIS DUMBASS https://drive.google.com/file/d/0B9DmzLnUt5tuaUtJS1FHcjNyX1U/view?usp=sharing
ADB_&_FASTBOOT_executables, no need to install, just extract the .zip to the directory of your choice and execute openCMD.bat with a right click + run as administrator. it will open a terminal window, you can run all your ADVB & FASTBOOT commands from there:https://drive.google.com/file/d/0B9DmzLnUt5tuM29vOTNHNEZya2s/view?usp=sharing
Driver installer & MTK_SP_FLASH_TOOL for MT8127 use this to install the drivers and flash the stock rom + custom recovery.img https://drive.google.com/file/d/0B9DmzLnUt5tudVlrSEtzSE1tWHc/view?usp=sharing
UBIFS_Modified_CWM FOR FLASHING UPDATE-SuperSU-v2.46.zip COURTESY Vampirefo: https://drive.google.com/file/d/0B9DmzLnUt5tueC04RDFVX3plTVk/view?usp=sharing
UPDATE-SuperSu-v2.46.zipflash this with vampirefo's modified CWM recovery image UBIFSRecovery4SuperSu.img" https://drive.google.com/file/d/0B9DmzLnUt5tuZjlmVm1Wc2tFUTA/view?usp=sharing
TWRP Setup.exe...Used to install TWRP recovery after flashing Stock ROM + Custom recoveryCOURTESY TWRP team & Protocol 9https://drive.google.com/file/d/0B9DmzLnUt5tuTVVJS2d2RERpbVk/view?usp=sharing
STEP 1: INSTALL THE DRIVERS INSIDE THE MT8127 SP_FLASH_TOOL.zip" file you downloaded It will install the mtk usb vCOM driver we need for the mtk8127. if u have questions PM vampirefo. after that, turn your tablet upside down, FIND THE reset hole and jam the nearest tiny object in there until the screen does something different (like go black) release the reset button, hold VOLUME DOWN and plug in the USB cord and the tablet should be reconized as a preloader USB VCOM Port device under "Ports" in Device Manager
{
"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"
}
So, the necessary driver to save this POS is at hand. after it's done installing the tablet will probably reboot and the remaining drivers will install. (EVEN WITHOUT THE OTHER DRIVER YOU CAN ROOT AND FLASH NOW)
Fire up the MT8127 SP flash tool (run as administrator) you downloaded and you should see this:
Click "Scatter-Loading" and select the scatter file located in the stock rom folder you downloaded and unzipped (you DID unzip it right?) and click the "RECOVERY" FIELD LOCATED HERE:
and select the recovery image you downloaded called "UBIFSRecovery4SuperSu.img......yay, you should be all set up and ready to go!
Make sure youve already unplugged the USB cable AND hit the reset button. HIT THE DOWNLOAD BUTTON (the program is now waiting for your device...no rush) HOLD VOLUME DOWN AND PLUG IN THE USB CABLE, the computer will detect the device, the program will proceed to shove a bunch of ones and zeros down the the tablets throat and it will reboot (hopefully to a mediatek logo).
If so, youre not as stupid as everyone says when u leave the room
Toss "UPDATE-SuperSU-2.46.zip" on a microSD, Power off the device, shove the SD in his home and hold POWER + VOLUME UP until you get prompted to select either RECOVERY OR FASTBOOT, we want recovery so make sure it's selected and press VOLUME DOWN to boot into recovery & install your SuperSU.zip and reboot
once the OS is fully running, run TWRP.exe as ADMINISTRATOR in AUTO mode, TWRP recovery should be installed and u should still have root, if not, you'll need to go into advanced, then mount system before re-installing from zip.
NOW learn ADB and fastboot so I can save my breath next time:
PS, all your GAPPS are gone....quit *****ing, I've got em here: htpa_gapps-modular-micro-4.4.2-20140608-signed.zip(pa_gapps-modular-micro-4.4.2-20140608-signed.zip 85.3MB) & HERE: https://drive.google.com/file/d/0B9DmzLnUt5tuSl9lME9VZnFJTU0/view?usp=sharing(pa_gapps-stock-4.4.2-20140608-signed.zip 267MB))
I have requested this thread be removed, you are using my stuff without permission, and even crediting yourself with the firmware, I took the time to download, you yourself have done nothing but take others work including mine without permission.
Hi, Im new to all of this and hope anyone could help me out.
I have a problem with my tv box because of installing
SuperSU.
First of all, my box is rooted from factory. Its a beelink gt king. But super su isnt installed like when you root a phone and it shows. So I tried to install it because I needed to hide my root from some apps/games. I installed magisk but I needed this supersu also apparently? Well, anyway I did. And then the problem of the binary occupied appears. So Im googleing some solutions and it says that first you need to install a previous version and then update from play store but in play store there is no more supersu.
But anyway I installed the previous version, asked me to reboot system, I did, and now I have a tv box that is stuck in the logo. Actually not in logo..it passes the beelink logo in about 2 hours, then comes the skull with glowy eyes and thats when it stays. I have waited hours for the skull to change to the homescreen to no avail.
The second problem is I have been trying to reset the box but I just cant do it or the system cant?. Its really stuck. Maybe Im missing something? I dunno. I push the reset button that is at the bottom in this box, then I plug the power cable, wait some time, release...but nothing happens.
What I am doing wrong?
Please help someone.
And can you tell me a method without a PC? Unbelievably I dont have a PC. And this phone cant be rooted or at least is very difficult to root or so they say (a galaxy note 4 verizon).
But at the end it doesnt matter. Whatever it takes to fix this box. Thank you.
GT KING SD Card Update
Hi Hansell1001, I did the same thing and faced the exact same issue. But i happened to have a PC. But i think this can also be done via a Phone and a SD card.
First download the firmware as per your model (As per your serial number under the box) to your phone.
Firmware: For C922X and SA9X and SB9X versions
http://t.cn/A6zQGfda
Firmware: For B922 versions（04.01.2020 add）
http://t.cn/A6ZNxNkM
Firmware: For S922 versions（04.01.2020 add）
http://t.cn/A6ZNxe7R
1. Now extract the content of the zip file.
2. You should see a folder called “sd_card”.
3. Copy the content of that folder (I.e factory_update_param.aml, recovery.img and galilei-ota-eng.xk.zip) to the root of SD Card.
IMPORTANT: (the SD card format must be FAT32)
4. Insert the SD Card to the SD slot at the side of the box.
{
"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"
}
5. Now remove the power cord of the GT King and with the help of a pin, press and hold the reset button at the bottom and insert the power cord.
6. Hold the reset button for 5 seconds till you see the Beelink logo and then release it. Hopefully you be on the recovery screen.
7. From this screen, select “Apply update from EXT” and select the update zip file.
8. Now the box would update properly and boot you back.
I fixed it
I fixed it more than a month ago. Thanks anyway.
I thought xda was quick.
Hansell1001 said:
I fixed it more than a month ago. Thanks anyway.
I thought xda was quick.
Click to expand...
Click to collapse
Ha ha Yeah but i just got the box in Jan i screwed in March so i was looking for a solution but figured it out myself. So when i saw your post, i thought it would be helpful but guess not. But anyway now this would be helpful to someone who may need it.
So let this be a reference for them
Guys, help! I got a GTKing in November 2020, a couple of weeks ago. It worked for a week or so, then it went into boot loop. Firmware is v 914p0 (dated 21 Oct 2020). I tried several things to no avail:
- When reapplying v 914p0, the device reboots to the boot loop
- When attempting to apply v 913p0or earlier, it says it won't apply an earlier version.
I hope someone will drop in some hint on how to get this @#!* box to work.
Cheers,
-Christos
I can't download that firmware
Fordac
Hello Everyone!
I need urgent help from you all because I am currently stuck in a very bad situation. Please please please!! Help me to get out of this. Let me start from the beginning of whatever I did. This is going to be a very long post so please bear with me.
Why did I try to root my device?
I have Realme 1 which works on Android 9 and does not support internal screen recording. So I thought rooting would help me and I would be able to create gaming videos.
1st Phase:
I researched about how to root my device.
I came to know that first I’ll have to unlock my bootloader.
I tried to unlock my bootloader and when I was running the necessary commands like fastboot reboot, it simply showed, “Waiting for device…..”
Now confused, I went to the Device Manager and uninstalled Android and its drivers from the category of other devices by mistake. Now, my problem was that, how to pass commands to my device?
Next, I deleted everything, and started from scratch. This time, I connected my device (via the same USB cable) and I did something (I don't exactly remember what I did, but ultimately it lead me to Windows Update, where I clicked on View Optional Updates and updated the driver. I am attaching a screenshot of what I had installed.
Next, I downloaded platform tools, extracted them and in the address bar typed cmd and did the following checks to ensure that my device can receive commands.
When device was powered on:
adb devices
Returned: _________ device
Next command:
adb fastboot (Something like that which took it to the fastboot mode)
Next Command:
fastboot devices
Returned: _________ fastboot
Satisfied that I was going on well, I unlocked the bootloader using the respective commands.
2nd Phase:
Now I knew, my bootloader was unlocked, so I did the next step.
I switched to fastboot mode.
Downloaded boot_patched.img for Realme 1 C.50
Next, I pasted it into the platform tools folder.
Next, booted my device into the fastboot mode, and gave the flashing command.
Confirmed it on my device using volume up key.
Gave fastboot reboot command to reboot my device.
Downloaded Magisk Manager and rooted my device successfully.
Downloaded RootChecker app to be sure and got the positive result.
I downloaded the apps I needed.
Problem Phase:
I had downloaded a banking app but it didn’t work because my device was rooted, so I searched, “How to hide root from banking apps?”
I came to know that the solution for this was on Magisk Manager itself. Magisk Hide
So, I opened the Magisk Manager and I was shown a prompt to download something (Or maybe I downloaded something from the settings? It was something like system host module or something like that) Now I don’t exactly remember whether my device rebooted or not, but let me continue.
So, I went to settings, enabled Magisk Hide, selected the app from which I had to hide root and opened the app. It didn’t work.
I searched the internet and saw that I had to reboot my device as well.
After I did that I faced a more serious problem. The app was still not working and my sim cards were disabled.
Now I panicked, I did the ultimate thing for which I had rooted my phone, I downloaded the game and the screen recorder. I chose the internal sound recording option, it told me to download some Magisk Module for it to work. So I did it.But it still didn’t work.
Now I was sad, I didn’t know what to do. Then ultimately I opened my RootChecker app and check the root status of my device and you guys won’t believe what I saw.
" No proper root access granted "
Super Problem Phase:
I decide that I’ll unroot my device. So, I set down to work.
I got to know that I had to uninstall the Magisk Manager completely. I did so and my device rebooted.
There came a wave of relief, my sim cards started to work.
I thought that my device was unrooted now, so I opened my banking app and it showed: “Your device is rooted! You can not proceed further.”
I was confused, I checked the rootChecker and it clearly said the same thing. No root access.
So, I searched the web again and I was told that if I remove some files like su and one more file (I don’t exactly remember the name) then my device will be unrooted. I donloaded the es file explorer but didn’t find those files.
I searched the internet again and found something new. If I reset my device, then the root will go away. I was very happy. I did a factory reset of my device and this time I didn’t check the banking app, I did one more thing which I was not supposed to.
Ultra problem phase:
I got to the fastboot mode using the same commands in the adb terminal and decided to lock the bootloader. I thought that the app had detected that my bootloader was locked so that may be the reason it was not working. I gave the command:
fastboot flash lock
(it was something like this, I don't quite remember)
I confirmed that I wanted to lock my bootloader.
And that led me to my doom.
I rebooted my device using the command.
My device never started.
After the logo, or to say while booting I was shown this error:
"The current image(boot/recovery) have been destroyed and can not boot. Please flash the correct image or contact customer care to fix it."
Then I though maybe I could just download the original boot and recovery file again then it would be all fine. I have those files and everything, when now I try to give those commands, they just show "Waiting for device...." Moreover the computer doesn't detect my device. The only thing I can do is just go to recovery mode.
Guys, I told you all everything that I knew please give me a detailed solution to the problem. I am also attaching some images so that you can see what exactly has happened.
Thanks in advance.
{
"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"
}
Sorry to say, but ... flashing unofficial/custom firmware and rooting has risk of bricking your device. And locking the bootloader was not the right/, best option
Maybe you have a chance to get it working again by flashing a complete firmware to it. Hopefully it will be successful after locking the bootloader
Hi there! I need some help, I am trying to root my device and need a boot.img, but I cannot find a Rom for the x9 anywhere online.
This is my first time doing this, I got this phone just to mess around with rooting. But maybe I bought a bad phone for it.
If there are no Flash Roms online, what are the next steps? Can I use a Rom for the e9 which released alongside this phone? Sounds like it wouldnt work.. but IDK.
Looking for help from the experts ^^
Any help is appreciated.
Finally found one! Took over 2 hours to download a 2gb file O,O but it's finally done.
Now I am having problems getting into bootloader mode.
In developer mode with both OEM unlocking and USB debugging enabled.
Used the correct cmd prompt (adb reboot bootloader) but the phone just restarts.
I've tried restarting while holding the volume buttons.
VOL Down = Factory Test Mode, nothing works as expected there.
VOL UP = A boot menu letting me select from ~10 options, one of them is Boot to Bootloader. Selecting that simply boots normal, nothing special.
I have followed three guides:
How TO Root Vodafone Smart X9 Magisk without TWRP Recovery
If your Smart X9 is rooted using Magisk without TWRP Recovery. You can control a lot of features such as you can remove unwanted software.
www.getdroidpro.com
Vodafone Smart E9 Unlock Bootloader with Fastboot Method
How to unlock bootloader on your Vodafone with Fastboot Method. You can install custom ROM, custom recovery, kernel, flash all data
www.mobilewithdrivers.com
All seem logical enough, many similarities between them. I just cannot get into fastboot mode.
I've seen LOADS of threads with this same problem on this forum. And none of them have any solutions. So I think this is the end of the road. If nobody has figured it out .. then I am just out of luck I guess?
HalpNeeded said:
Forget, your phone have only 3 buttons
Click to expand...
Click to collapse
Hi @joke19 !
I havnt seen any of the guides mentioning needing a certain amount of buttons :O
How does that factor in - does that mean it cannot be rooted for some reason?
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
{
"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"
}
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
HalpNeeded said:
Still having this problem, and I have followed a lot of guides to the letter. I cant see what I am doing wrong. Here's where I am:
Phone is visible on device manager and the drivers are up-to-date.
View attachment 5671635
PC is fully up to date on Windows 10.
I've got the lastest up-to-date version of platform-tools.
I'm using USB2.0 with the correct wires.
The phone is in developer mode with USB Debugging and OEM unlocking enabled.
I'm using the correct command lines. adb devices & adb reboot bootloader work as expected.
But none of these will work: fastboot devices, fastboot flashing unlock, fastboot oem unlock.
I just get < waiting for any device >
Can anyone help figure this out? I must be doing sooomething wrong. Everything online says its a driver issue, but then again, all the guides on how to fix that driver issue have been followed and completed. The first bullet with the image should also sort of verify that.
Praying some wizard out there has the knowledge I need to get this working! ^^
Click to expand...
Click to collapse
did you manage to get this working?