I'm sure theres no helping me, beings how im new to this, i run linux mint, not windows, and i made bad decisions to get here. i recently got a new moto g7 power with full intentions on using it as my guinea pig while i still had my old phone working. my plan was to not even install a sim card into my g7 until i had it properly rooted. i looked through all sorts of tutorials and tried many different things and learned alot along the way. long story short, ive been using the linux command line to do everything. i got my bootloader unlocked using the code that i requested from motorola. then i downloaded the 2 g7 ocean files, zip and img. i pushed the zip file into the /data/ folder, fastbooted from the .img file, got to twrp/ from there i went to advanced, install recovery Ramdisk, navigated to data, and selected the .img file. i tried this twice with no success, it would just boot normally and the twrp app wouldnt allow me to install the zip file, says its not rooted. so the last time i tried, i dont remember exactly how i did it but within the twrp recovery menu i found a way to boot slot b, but slot a was already selected by default. my thought was that i had installed the zip on slot b and not slot a. selected slot b, my phone shut off, and now nothing. just blank, wont even light a light, even if i plug it in.
i know that i shouldnt have been messing around with stuff i dont know much about, but hey, it beats watching the news right now, and that is why i didnt buy a 1000 dollar phone. also, i bought this phone from amazon prime, but im not sure id sleep good at night sending it back knowing i damaged it myself, however that was recommended to me. Thank you for any help/ info i may get.
Blank flash
jhomolac said:
I'm sure theres no helping me, beings how im new to this, i run linux mint, not windows, and i made bad decisions to get here. i recently got a new moto g7 power with full intentions on using it as my guinea pig while i still had my old phone working. my plan was to not even install a sim card into my g7 until i had it properly rooted. i looked through all sorts of tutorials and tried many different things and learned alot along the way. long story short, ive been using the linux command line to do everything. i got my bootloader unlocked using the code that i requested from motorola. then i downloaded the 2 g7 ocean files, zip and img. i pushed the zip file into the /data/ folder, fastbooted from the .img file, got to twrp/ from there i went to advanced, install recovery Ramdisk, navigated to data, and selected the .img file. i tried this twice with no success, it would just boot normally and the twrp app wouldnt allow me to install the zip file, says its not rooted. so the last time i tried, i dont remember exactly how i did it but within the twrp recovery menu i found a way to boot slot b, but slot a was already selected by default. my thought was that i had installed the zip on slot b and not slot a. selected slot b, my phone shut off, and now nothing. just blank, wont even light a light, even if i plug it in.
i know that i shouldnt have been messing around with stuff i dont know much about, but hey, it beats watching the news right now, and that is why i didnt buy a 1000 dollar phone. also, i bought this phone from amazon prime, but im not sure id sleep good at night sending it back knowing i damaged it myself, however that was recommended to me. Thank you for any help/ info i may get.
Click to expand...
Click to collapse
Most likely it's in Emergency download mode (EDL)
You will need a blankflash, several threads on this.
There's one here, that may work.
https://mirrors.lolinet.com/firmware/moto/ocean/blankflash/
Sent from my Moto E (4) using Tapatalk
EDL mode even though there is no sign of life whatsoever?
jhomolac said:
EDL mode even though there is no sign of life whatsoever?
Click to expand...
Click to collapse
There won't be anything on the phone, just a black screen, but it should show up on a PC's list of connected devices.
Sent from my Moto E (4) using Tapatalk
jhomolac said:
EDL mode even though there is no sign of life whatsoever?
Click to expand...
Click to collapse
Some phones will display a charge light some won't like he said it's in edl mode the PC sould display it and u should hear it make sound when u plugs the phone into PC on windows in not sure on Linux machine should b perty much the same on that aspect .One thing u might have to get different blank flashes for the different updates .If don't go the first time try again good luck
Thank you guys, i appreciate your time. sounds like i have to do some more research about flashing a motorola from linux. im somewhat new to linux as well.
jhomolac said:
Thank you guys, i appreciate your time. sounds like i have to do some more research about flashing a motorola from linux. im somewhat new to linux as well.
Click to expand...
Click to collapse
https://mirrors.lolinet.com/firmware/moto/ocean/ here is a blank flash that should get u going dose the PC recognise ur phone when u plug it in if dose open terminal an PC type fastboot devices if it sees it your in luck I can typ fastboot boot (the name of ur recovery) if it boot into twrp then u might b able to switch it to a slot. There is comands for fastboot to switch but I don't know them
My computer does not notify me when I plug in my phone. But I don't remember it doing that even when I used it before.thank you.
You might need to charge the phone. With a blank/black screen it can appear off when it's not. Thus draining the phone completely. It widely suggested to charge phones to at least 80% before tweaking/rooting.
I will feel like a real dummy if that's the case. It is now on the factory supplies charger. Haha. Crossing my fingers. Thank you
If I use command lsusd in terminal, my phone pops up as a Qualcomm wireless router. Command fastboot devices brings up nothing
jhomolac said:
If I use command lsusd in terminal, my phone pops up as a Qualcomm wireless router. Command fastboot devices brings up nothing
Click to expand...
Click to collapse
It's in edl mode, use the blankflash
Sent from my Moto E (4) using Tapatalk
I've never done a blank flash before, I thought it was done by using: fastboot flash command. But it doesn't seem possible if: fastboot devices doesn't bring everything up. I am on linux by the way
jhomolac said:
I've never done a blank flash before, I thought it was done by using: fastboot flash command. But it doesn't seem possible if: fastboot devices doesn't bring everything up. I am on linux by the way
Click to expand...
Click to collapse
You need QPST to interface with EDL mode. I don't know if anything in here works on Linux, but it definitely works on Windows 10.
QPST Utilities
decided to give this another try. i have managed to get a little further, however this is where i am getting stuck. i wish i was more savy with this stuff. any chance anyone could help me with this?
also, is it nessecary to have an sd card in the device when i do this?
blankflash_from_QCO30.85-18]# /home/joel/Desktop/blankflash_from_QCO30.85-18/blank-flash.sh
< waiting for device >
Motorola qboot utility version 3.40
[ 0.000] Opening device: /dev/ttyUSB0
[ 0.000] Detecting device
[ 0.005] ...cpu.id = 186 (0xba)
[ 0.005] ...cpu.sn = 2335135194 (0x8b2f55da)
[ 0.005] Opening singleimage
[ 0.005] Loading package
[ 0.013] ...filename = singleimage.pkg.xml
[ 0.018] Loading programmer
[ 0.019] ...filename = programmer.mbn
[ 0.019] Sending programmer
[ 0.318] Handling things over to programmer
[ 0.318] Identifying CPU version
[ 0.324] Waiting for firehose to get ready
[ 3.338] ...MSM8953 1.0
[ 3.338] Determining target secure state
[ 3.343] ...secure = yes
[ 3.387] Configuring device...
[ 3.394] Flashing GPT...
[ 3.394] Flashing partition with gpt.bin
[ 3.400] Initializing storage
[ 5.763] Target NAK!
[ 5.763] ...num_partition_sectors=61071360
[ 5.763] ...SECTOR_SIZE_IN_BYTES=512
[ 5.763] ...num_physical_partitions=3
[ 5.763] ...OEM_ID=74
[ 5.763] ...Product name=hB8aP>
[ 5.763] ...XML (0 bytes) not validated
[ 5.763] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
[ 5.763] Check qboot_log.txt for more details
[ 5.763] Total time: 5.763s
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_flash()->flash_simg()->do_package()->do_recipe()->do_flash()->gpt_flash()->get_storage()->init_storage()->firehose_do_fmt()->do_recipe()->NAK
sd_shadow said:
There won't be anything on the phone, just a black screen, but it should show up on a PC's list of connected devices.
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
What do I do if it doesn't?
I tried all the possible button combinations but still nothing.
uwucake2020 said:
What do I do if it doesn't?
I tried all the possible button combinations but still nothing.
Click to expand...
Click to collapse
Is there anything on the phone screen?
sd_shadow said:
Is there anything on the phone screen?
Click to expand...
Click to collapse
There isn't anything, and it doesn't seem to be in EDL mode. (I checked in the device manager)
uwucake2020 said:
There isn't anything, and it doesn't seem to be in EDL mode. (I checked in the device manager)
Click to expand...
Click to collapse
Spoiler: It may be hidden in Ports 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"
}
Related
The warning that shows after unlocking your phone through Motorola is nothing more than a boot logo. I found some compatible logos over in the Droid Bionic forum. There is a short guide to making your own pics work here as well as a stock img; links are up below for our communities contributions as well as a couple I made.
Stock image HERE, Thanks Skrilax_CZ
Community Contributions:
Thanks everyone for working on these & sharing w us.
dpwhitty11
sixxt9:
Batch1
Batch2
Adamoos
Adamoos Trigun
Make your own:
If running windows looks like we are stuck with Photoshop until someone ports a raw. Img extension for Gimp.
Make your pic 540x540, the outside pixel color dictates the surrounding color of the screen.
Flatten image, adjust color: select Image- Adjustments- Channel Mixer- Output channel red, change settings from 100 in red to 0 and blue to 100. Then select blue Output Channel and reverse the red and blue again, this time red is 100 and blue is 0.
Save as- select format and choose RAW then change the extension to .img
Now follow the install instructions below.
Full how to w Gimp instructions for linux users here
Quick disclaimer... I am not responsible... blah, blah, blah...
Ok, lets get to flashin.
Install Instructions:
Hereby6262 offered this to say about the most recent sdk.
Make, or download an image u like from here or Droid Bionic forums.
Once downloaded on your pc, move the img file to platform-tools folder(or where ever you have your fastboot interface).
Hold shift & right click the open folder w nothing selected, click "open command window here"
Type in:
adb reboot bootloader
fastboot flash logo "filename".img (no quotation marks, insert you file name).
(some computers require moto-fastboot? I assume you know your system.) You should see the push & install successfully finish.
fastboot reboot
Unplug usb & you should see the results immediately.
My contribution:
Roses, for the ladies.
{
"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"
}
Rider, for the gents, probably the reason you just got the roses for your lady.
BioDroid
Punisher
Found this here & edited to the correct format. Thanks bbelhorn.
Circuit
fallnSaint said:
Found some compatible logos over in the Droid Bionic forum. These aren't full screen but look a lot better than the unlocked bootloader warning most of us have been looking at for the last several weeks. I will be working on more options in the future as time allows.
There is mention of some paid app needed to flash these, but you can just use fastboot to install these for free.
Quick disclaimer... I am not responsible... blah, blah, blah...
Also, give a thanks to whomever you snag an image from.
Install Instructions:
Find an image u like from here: http://forum.xda-developers.com/showthread.php?t=1308852
Once downloaded, extract img if necessary, move the img file to platform-tools folder.
Put your phone in fastboot, open terminal in platform-tools, & plug in your usb.
Type in:
fastboot flash logo.bin "filename".img
fastboot reboot
Unplug usb & you should see the results immediately.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
That did not work for me, Im getting
C:\Program Files\Android\android-sdk\tools>moto-fastboot flash logo.bin thefinger.img
sending 'logo.bin' (854 KB)... OKAY [ 0.222s]
writing 'logo.bin'... INFOInvalid partition name logo.bin
FAILED (remote failure)
C:\Program Files\Android\android-sdk\tools>moto-fastboot reboot
rebooting...
am I missing something ?
tetrabyt said:
That did not work for me, Im getting
C:\Program Files\Android\android-sdk\tools>moto-fastboot flash logo.bin thefinger.img
sending 'logo.bin' (854 KB)... OKAY [ 0.222s]
writing 'logo.bin'... INFOInvalid partition name logo.bin
FAILED (remote failure)
C:\Program Files\Android\android-sdk\tools>moto-fastboot reboot
rebooting...
am I missing something ?
Click to expand...
Click to collapse
Did you also put thefinger.img in the android-sdk/tools folder? Run the cmd line from the same folder you have fastboot & the img file in.
Sent from my XT897 using xda premium
tetrabyt said:
That did not work for me, Im getting
C:\Program Files\Android\android-sdk\tools>moto-fastboot flash logo.bin thefinger.img
sending 'logo.bin' (854 KB)... OKAY [ 0.222s]
writing 'logo.bin'... INFOInvalid partition name logo.bin
FAILED (remote failure)
C:\Program Files\Android\android-sdk\tools>moto-fastboot reboot
rebooting...
am I missing something ?
Click to expand...
Click to collapse
Looks like u did, just checked the file size... let me try that file.
Sent from my XT897 using xda premium
fallnSaint said:
Looks like u did, just checked the file size... let me try that file.
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Ok, my bad, typo in the OP.
fastboot flash logo "filename".img
OP updated.
fallnSaint said:
Ok, my bad, typo in the OP.
fastboot flash logo "filename".img
OP updated.
Click to expand...
Click to collapse
excellent, worked great now.... thank you
tetrabyt said:
excellent, worked great now.... thank you
Click to expand...
Click to collapse
You are welcome. Glad to help out.
Sent from my XT897 using xda premium
fallnSaint said:
Found some compatible logos over in the Droid Bionic forum.
Click to expand...
Click to collapse
Gotta say thanks for this, I tossed the black background with the google on it. Soooo much nicer to look at.
KitsunePaws said:
Gotta say thanks for this, I tossed the black background with the google on it. Soooo much nicer to look at.
Click to expand...
Click to collapse
Oh, i feel ya. I almost went w that one myself, maybe next week. I plan to add some more here soon.
Course, this depends on how motivated I,m feeling & how much free time I am left with...
Sent from my XT897 using xda premium
OP updated, now includes a few of my own making, as well as a link to make your own work. Full screen is out of the question as far as my skills are concerned, I believe the bootloader dictates the size.
Found the stock boot logo here, thanks to jimmydafish. Posted a copy of it below for convenience.
Can someone guide me on how to flash with the OEM motorola and Sprint boots? New to Android, long time user of WM (TP2)
ericcire said:
Can someone guide me on how to flash with the OEM motorola and Sprint boots? New to Android, long time user of WM (TP2)
Click to expand...
Click to collapse
I assume that you have already installed android sdk as well as the moto drivers for this phone since you are unlocked. Just download the stocklogo.img in the post before yours, on your computer. Move it to wherever you installed the android sdk folder, put it in platform-tools folder. Plug your phone into your computer, hold shift & right click on your open platform-tools folder with nothing selected in the folder. Select open command window here.
Type in the command prompt:
adb reboot bootloader
Your phone will boot to fastboot, now type:
fastboot flash logo stocklogo.img
You should see it flash successfully, then type:
fastboot reboot
Your phone will reboot & you can unplug it.
This might help you out in the future: http://forum.xda-developers.com/showthread.php?p=3591882
Welcome to Android!
Sent from my XT897 using xda premium
fallnSaint said:
I assume that you have already installed android sdk as well as the moto drivers for this phone since you are unlocked. Just download the stocklogo.img in the post before yours, on your computer. Move it to wherever you installed the android sdk folder, put it in platform-tools folder. Plug your phone into your computer, hold shift & right click on your open platform-tools folder with nothing selected in the folder. Select open command window here.
Type in the command prompt:
adb reboot bootloader
Your phone will boot to fastboot, now type:
fastboot flash logo stocklogo.img
You should see it flash successfully, then type:
fastboot reboot
Your phone will reboot & you can unplug it.
This might help you out in the future: http://forum.xda-developers.com/showthread.php?p=3591882
Welcome to Android!
Sent from my XT897 using xda premium
Click to expand...
Click to collapse
Got it. No more unlocked bootloader warning! When booting, it only shows the Motorola boot logo, is there any way I can also have it run the sprint boot animation? Want it to look as stock as possible.
Thanks fallnSaint
---------- Post added at 01:19 PM ---------- Previous post was at 01:09 PM ----------
Figured it out myself! Learning the android platform.
Only things I am still unable to do (that I could on my TP2) are:
(1) Force Roaming - I downloaded and paid for Roam Control, but it still does not function.
(2) Wifi sharing - Downloaded FoxFi; It says it has activated the hotspot, but when trying to connect with my ipad it times out. When trying to connect with laptop it connects, but says no internet connection.
If your rooted try wifi tether from play store, sorry no direct link.
Sent from my XT897 using xda app-developers app
bryanfritz1 said:
If your rooted try wifi tether from play store, sorry no direct link.
Sent from my XT897 using xda app-developers app
Click to expand...
Click to collapse
Tried wifi tether and the open garden one. No luck. Will the defualt wifi hotspot in the settings charge my sprint account if I try that one?
ericcire said:
Got it. No more unlocked bootloader warning! When booting, it only shows the Motorola boot logo, is there any way I can also have it run the sprint boot animation? Want it to look as stock as possible.
Thanks fallnSaint
Click to expand...
Click to collapse
The boot animation should be stock unless you manually changed it. Pulsing moto logo followed by sprint, doesn't get more stock than that.
ericcire said:
Only things I am still unable to do (that I could on my TP2) are:
(1) Force Roaming - I downloaded and paid for Roam Control, but it still does not function.
(2) Wifi sharing - Downloaded FoxFi; It says it has activated the hotspot, but when trying to connect with my ipad it times out. When trying to connect with laptop it connects, but says no internet connection.
Click to expand...
Click to collapse
These have been covered in different threads:
Force roaming Photon Q General
Wifi tether Photon Q Q/A
Hopefully you can find some answers there.
Here's a little quickie I threw together.
Changed my DarkDroid logo from red to blue, then cut a screencap of Motorola's page for the Q to get the text.
Cool! Worked perfect thanks for these...that warning was getting on my nerves fo sho.
The Blue Dark Droid looks great as the boot logo. Thanks!
Sent from my XT897 using xda app-developers app
I just followed the steps outlined in the first post, however, the background of my image and the color of the screen above and below the bounds of the 540x540 logo are not the same black. Any way to correct this?
I haven't gotten any answers in the thread for unbricking and I don't want to triple post so I decided to open up this thread. Apparently the brick after downgrading has happened to a few others so they told me to follow the directions in the unbrick thread. One step tripped me up...
9. Now we restore the hboot.. replace /sdc12 with your device location that we discovered in step 3 and 4
Click to expand...
Click to collapse
The highlighted part specifically. Like I said I thought the sdc/12 replacement corresponded with the device number in the watch window but I was told it doesn't. Cool, that's understood.
There's a problem now though. I can't get out of QDL mode in order to go from seeing 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"
}
to seeing this:
I am now stuck in QDL Mode but Ubuntu can see the device. The last time I tried to do any further steps past 3 & 4 resulted in this...
Notorio said:
Quick update. This is what I get after sudo dmesg | grep "qcserial"
[ 7.037046] usbcore: registered new interface driver qcserial
[ 7.037084] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 762.099705] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 762.099734] qcserial 2-1:1.0: device disconnected
[ 883.505651] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 911.795216] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 911.795241] qcserial 2-1:1.0: device disconnected
[ 931.525335] qcserial 2-1:1.0: Qualcomm USB modem converter detected
[ 1195.600667] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1195.600685] qcserial 2-1:1.0: device disconnected
[ 1207.071036] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1221.119399] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1221.119416] qcserial 2-2:1.0: device disconnected
[ 1227.733317] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1349.655162] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1349.655178] qcserial 2-2:1.0: device disconnected
[ 1356.273714] qcserial 2-2:1.0: Qualcomm USB modem converter detected
[ 1634.585084] qcserial ttyUSB0: Qualcomm USB modem converter now disconnected from ttyUSB0
[ 1634.585097] usbcore: deregistering interface driver qcserial
[ 1634.585137] qcserial 2-2:1.0: device disconnected
[ 1660.474277] usbcore: registered new interface driver qcserial
[ 1660.474347] qcserial 2-2:1.0: Qualcomm USB modem converter detected
*scratches head* I'm wondering if I should just stop trying because I may be making it worse...
Click to expand...
Click to collapse
Hopefully I didn't brick it into oblivion. Yes this is user error but insulting my intelligence won't help matters. Please just help me out, I'm losing my mind over here
Update: I'm not sure why or how (it wasn't my doing) but I'm out of QDL mode but it disconnects & reconnects sporadically now. I can't connect long enough to see the expanded sdb lists though
EDIT: After I manually disconnect & reconnect I go back into QDL mode stuck
Have you tried opening a new terminal window?
There is a way out of it and into recovery. This link is for a different phone but may put you on the right track.
http://www.icsforums.com/forum/showthread/13791
AT&T HTC OneX
Android 4.1.1
ViperXL
Venomtester said:
Have you tried opening a new terminal window?
There is a way out of it and into recovery. This link is for a different phone but may put you on the right track.
http://www.icsforums.com/forum/showthread/13791
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Thanks, that thread has a lot more info in it than the one for the HOX (though they're made similarly so it's essentially the same thing).
I'm sifting through all 81 pages (up to page 42 now) while continuing to play with it in terminal. If I only need to see the sd* letter (b or c -- I already know it's b from a prior run) then I can skip those steps.
My issue now is, when I run the sudo ./emmc_recover -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576 command the result is: cannot find bricked device node.
I've searched both threads, nothing in either about this particular issue so I'm lost again
EDIT: Well I'm back to the sporadic in & out of Qualcomm, Inc. changes. It still won't stay connected long enough to write to the device unfortunately
Notorio said:
Thanks, that thread has a lot more info in it than the one for the HOX (though they're made similarly so it's essentially the same thing).
I'm sifting through all 81 pages (up to page 42 now) while continuing to play with it in terminal. If I only need to see the sd* letter (b or c -- I already know it's b from a prior run) then I can skip those steps.
My issue now is, when I run the sudo ./emmc_recover -f ./hboot_1.12.0000_signedbyaa.nb0 -d /dev/sdc12 -c 24576 command the result is: cannot find bricked device node.
I've searched both threads, nothing in either about this particular issue so I'm lost again
EDIT: Well I'm back to the sporadic in & out of Qualcomm, Inc. changes. It still won't stay connected long enough to write to the device unfortunately
Click to expand...
Click to collapse
The computer is not recognizing the drive on the phone. Did you check to see if it is visible and try to install drivers with an update through the computer?
AT&T HTC OneX
Android 4.1.1
ViperXL
Venomtester said:
The computer is not recognizing the drive on the phone. Did you check to see if it is visible and try to install drivers with an update through the computer?
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
It is recognized but when the phone is out of QDL mode it keeps disconnecting & reconnecting until it is back in QDL mode. One guy in that thread you linked me to had the same issue but his solution isn't working for me.
I'm trying to remember if I changed the hex values for the IMEI when I tried a few days ago. I don't think I did. If I flashed the p4 files without my IMEI is there a way to fix this & could this be my issue? Note I've already tried to adb & windows doesn't recognize the device. If there are any Linux commands I'll try those.
Thanks again for your help...
Notorio said:
It is recognized but when the phone is out of QDL mode it keeps disconnecting & reconnecting until it is back in QDL mode. One guy in that thread you linked me to had the same issue but his solution isn't working for me.
I'm trying to remember if I changed the hex values for the IMEI when I tried a few days ago. I don't think I did. If I flashed the p4 files without my IMEI is there a way to fix this & could this be my issue? Note I've already tried to adb & windows doesn't recognize the device. If there are any Linux commands I'll try those.
Thanks again for your help...
Click to expand...
Click to collapse
There are IMEI repair files At Hotfile, Mediashare and Rapidshare. You may be able to find one.
http://soft.udm4.com/downloading/imei_number_corrupted_how_to_recover/
AT&T HTC OneX
Android 4.1.1
ViperXL
Getting to the end of that thread you listed it looks as if I'm completely bricked, no fix in sight. This sucks
*sighs* May as well close this thread...
Notorio said:
Getting to the end of that thread you listed it looks as if I'm completely bricked, no fix in sight. This sucks
*sighs* May as well close this thread...
Click to expand...
Click to collapse
This is the last place that I know of to try.
http://forum.gpgindustries.com/show...air-for-50-Samsung-phones-HTC-AT-amp-T-unlock!
Sure wish I could have been more help.
AT&T HTC OneX
Android 4.1.1
ViperXL
Venomtester said:
This is the last place that I know of to try.
http://forum.gpgindustries.com/show...air-for-50-Samsung-phones-HTC-AT-amp-T-unlock!
Sure wish I could have been more help.
AT&T HTC OneX
Android 4.1.1
ViperXL
Click to expand...
Click to collapse
Oh no you've been more than enough help, the solution just wasn't attainable. Thanks again, I really appreciate it.
I'm going to send my phone off for JTAG repair, lucky for me it's only $60 (as opposed to buying a new one for $350)...
Notorio said:
Oh no you've been more than enough help, the solution just wasn't attainable. Thanks again, I really appreciate it.
I'm going to send my phone off for JTAG repair, lucky for me it's only $60 (as opposed to buying a new one for $350)...
Click to expand...
Click to collapse
Well I sure do hate it but like you said, $60 isn't too bad.
HTC OneX
Android 4.1.1
ViperXL
Hi,
I am in huge trouble. I bought this phone 2 weeks ago and 2 days ago installed android Q. This was mistake because after a some time phone was going to something called "Qualcomm dump mode" and that was it. Only thing to do was wait to battery goes down and restart.
So, I tried to go back, nothing from official ways works so I decided to go with TWRP and unblocking bootloader. And now I think I totally bricked my phone...
After command: "fastboot boot flash twrp.img" my phone only is restarting to 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"
}
( I don't know how to insert picture here)
Is it can be saved?? Or I screwed up all the way? Anyway thank you in advance for any kind of help.
My phone details:
Oneplus 7 pro ver. GM1910
you need the drivers id believe and in device manager on pc what you show is mtp with ! orob delete that restart device get drivers
I had the same. You can install the rom again via fastboot with Guac recovery (search on this forum)
Solex49 said:
I had the same. You can install the rom again via fastboot with Guac recovery (search on this forum)
Click to expand...
Click to collapse
I am getting:
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 0.946s
Click to expand...
Click to collapse
ecompton59 said:
you need the drivers id believe and in device manager on pc what you show is mtp with ! orob delete that restart device get drivers
Click to expand...
Click to collapse
I kinda don't understand. And I no longer can find my device in Device manager
@edit
Also I have this info:
Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.
djsubterrain said:
Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.
Click to expand...
Click to collapse
Unfortunately, it is not working and I read that: These ROMs can't be used to update or downgrade your phone but just to restore your phone[...].
I am, I think, I am, at andorid Q and want to back to android 9
Yep, I am getting this:
@edit
Ok, had 100MB free space on my hdd... Sorry about that.
@edit2
Ok, thank You men, I managed to go throgu, but now after booting I have black screen. Should I now try to install some roms?
KramarSenior said:
Unfortunately, it is not working and I read that: These ROMs can't be used to update or downgrade your phone but just to restore your phone[...].
I am, I think, I am, at andorid Q and want to back to android 9
Yep, I am getting this:
@edit
Ok, had 100MB free space on my hdd... Sorry about that.
@edit2
Ok, thank You men, I managed to go throgu, but now after booting I have black screen. Should I now try to install some roms?
Click to expand...
Click to collapse
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.
djsubterrain said:
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.
Click to expand...
Click to collapse
Still black screen. At least I have no problems with booting an .img files. Already installed TWRP from offical but when I copied zip file with rom it is not see it.
@edit
Ok, I installed a rom but now phone is still loading (this red dot with 2 white dots running around) and nothing is happaning
djsubterrain said:
Due to the change in version you should really go to recovery and do a factory reset. See what happens after reboot then.
Click to expand...
Click to collapse
Ok, dude, love You, phone is working fine now. Andoid 9, and all I need to to is install updates. Thank You very much for help. I will press "thank you" buttons as soon as I get home.
Thread can be closed.
djsubterrain said:
Connect your phone to your computer in Fastboot mode
Ensure you have installed the drivers for the phone : https://www.androidfilehost.com/?fid=3556969557455274390 (I've uploaded the drivers from Android 10 Open Beta 1 here too : https://www.androidfilehost.com/?fid=1899786940962579686)
Open a command window in the folder that the fastboot/adb tools have been installed to (By default the OnePlus drivers install those here : C:\Program Files (x86)\OnePlus USB Drivers\Android )
Enter the command fastboot devices
If you see a result from that command then the computer can see the phone correctly, if it's a blank line then it can't. In that case, try another usb port or cable.
Go here : https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Download the relevant package for the version you want to use
Extract the package and then run the flash-all.bat file
The script will then apply all default partitions for the version you have specified, this will wipe your data partition on the phone but, if you couldn't get into the phone in the first place, that's no big deal.
For good measure, once you have completed the install go into recovery and wipe the cache partition, I would actually use the factory default wipe option to start completely from scratch
Bear in mind though, you will still have an unlocked bootloader, to lock the bootloader again you would need to go into the developer settings and lock it and use the oem lock command
If you really want TWRP/Magisk back in then you'll likely need to use my workaround from here : https://forum.xda-developers.com/showpost.php?p=79961624&postcount=1210
Just use the fastboot getvar current-slot and fastboot set_active a or fastboot set_active b to track the active boot partition, that's very important for situations where the phone isn't booting correctly, a lot of the time it will be because you have the incorrect active slot enabled, in that case use the set_active command and the fastboot reboot command.
I would definitely recommend getting a usb drive you can use with the phone, there was an issue where TWRP couldn't see storage sometimes due to the difference between Android 9/10, using a usb drive to host the files you wanted to flash would help bystep encryption issues as the usb drive isn't encrypted.
I personally use these :
USB C to USB 3.0 Male Adapter : https://www.amazon.co.uk/gp/product/B07KXHNY5F
SanDisk Ultra USB Type-C 16 GB up to 130 MB/s USB 3.1 Flash Drive : https://www.amazon.co.uk/gp/product/B01BUSMYHC
When you use the drive it will make an "Android" folder, just throw your stuff in there, when you go to Install in TWRP you'll have a "SELECT STORAGE" button on the bottom left, that will let you use the usb drive, If you're using the File Manager in TWRP then it's listed under "usbstorage" in the main list.
Click to expand...
Click to collapse
My current slot is "a" but if I try to use fastboot set_active b or fastboot --set-active=b it shows: usage: fastboot [ <option> ] <command> and shows me all the fastboot commands
also if I try : fastboot boot "recovery_name".img it shows : downloading 'boot.img'...
OKAY [ 2.119s]
booting...
FAILED (remote: Failed to load/authenticate boot image: Load Error)
finished. total time: 2.162s
of course I tried fastboot flash boot "recovery_name".img and it flashes ok but when I try to reboot to recovery the bootloader pops up again
any ideas ?
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
It looks something like this: prog_emmc_firehose_8909_alc2.mbn
I don't know exactly what I did. I just flashed TWRP and booted in to it just to see if it was working, When I was done, I went to choose a partition to boot into, the first one said it had no operating system, I chose the second one which TWRP said had an OS. After that, the phone went dead and won't turn on. When I connect the phone to my PC, and go into device manager, the phone is listed as:
Qualcomm HS-USB QDLoader 9008. ADB doesn't see the phone, but QFIL does. I need the programmer file as well as a "rawprogram" file and a "patch0" file to flash the phone with QFIL.
Before I flashed TWRP, I unlocked the bootloader. I've unlocked the bootloader and flashed TWRP before and never had this happen.
Does a brand new phone only have the OS installed on one partition?
Could the programmer file be somewhere in the rom? In the sparsechunk files maybe?
Can the phone charge when its in this comatose state?
My nightmare began on Sunday night. I was waiting for a bus and a girl asked me to use the phone. While she was pretending to dial, a guy who she said was her brother(but probably wasn't) starts walking towards us. When he got close, she gave him the phone and they start running. I chased them and the guy says give me the passcode or I'll smash the phone. I said no and he smashed it on the ground and throws it over a fence. Then they ran back to the bus stop and stole my bike and ran away. I was able to recover the SD and SIM cards the next day. I have my phone backed up on the SD card.
What do you guys think their plan was? To steal my bicycle or my phone? Surely they knew the phone was useless without access to it. I could've rode away on my bike instead of chasing them. Before this all happened, they were standing across the street apparently casing me. I was doing something on my phone, so I didn't really notice them. Its not like they were professional thieves. They were just a couple of black kids around 20 years old from the ghetto. If they had a plan, it didn't make sense.
Heat84 said:
It looks something like this: prog_emmc_firehose_8909_alc2.mbn
I don't know exactly what I did. I just flashed TWRP and booted in to it just to see if it was working, When I was done, I went to choose a partition to boot into, the first one said it had no operating system, I chose the second one which TWRP said had an OS. After that, the phone went dead and won't turn on. When I connect the phone to my PC, and go into device manager, the phone is listed as:
Qualcomm HS-USB QDLoader 9008. ADB doesn't see the phone, but QFIL does. I need the programmer file as well as a "rawprogram" file and a "patch0" file to flash the phone with QFIL.
Before I flashed TWRP, I unlocked the bootloader. I've unlocked the bootloader and flashed TWRP before and never had this happen.
Does a brand new phone only have the OS installed on one partition?
Could the programmer file be somewhere in the rom? In the sparsechunk files maybe?
Can the phone charge when its in this comatose state?
My nightmare began on Sunday night. I was waiting for a bus and a girl asked me to use the phone. While she was pretending to dial, a guy who she said was her brother(but probably wasn't) starts walking towards us. When he got close, she gave him the phone and they start running. I chased them and the guy says give me the passcode or I'll smash the phone. I said no and he smashed it on the ground and throws it over a fence. Then they ran back to the bus stop and stole my bike and ran away. I was able to recover the SD and SIM cards the next day. I have my phone backed up on the SD card.
What do you guys think their plan was? To steal my bicycle or my phone? Surely they knew the phone was useless without access to it. I could've rode away on my bike instead of chasing them. Before this all happened, they were standing across the street apparently casing me. I was doing something on my phone, so I didn't really notice them. Its not like they were professional thieves. They were just a couple of black kids around 20 years old from the ghetto. If they had a plan, it didn't make sense.
Click to expand...
Click to collapse
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
When you install a rom on a Moto device with a/b system you need you to follow this
Pre-install instructions
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little
Click to expand...
Click to collapse
Click to expand...
Click to collapse
sd_shadow said:
Your device is in EDL Mode, it will charge in this state, also there is very little drain on the battery in this mode.
Motorola bundles these files as blankflash(es)
Try these
https://mirrors.lolinet.com/firmware/moto/racer/blankflash/
Click to expand...
Click to collapse
When I run blank-flash.bat, I get:
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
I don't know how the double quote happened and I don't know how to view the raw code to delete it right.
Heat84 said:
When I run blank-flash.bat, I get:
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()
->IO error
I don't know how the double quote happened and I don't know how to view the raw code to delete it right.
Click to expand...
Click to collapse
Try this
Moto G6 XT1925-6 "bricked" from normal use--blankflash not working
Hi all, My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white...
forum.xda-developers.com
sd_shadow said:
Try this
Moto G6 XT1925-6 "bricked" from normal use--blankflash not working
Hi all, My girlfriend's Moto G6 XT1925-6 (purchased via Best Buy, never rooted/modded) got slow one day, I recommended rebooting and then it never came back. The only signs of life are that when plugged into a computer or charger. the white...
forum.xda-developers.com
Click to expand...
Click to collapse
I tried that and I still get: ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
I read somewhere that Windows could somehow be interfering with the process. How can I do this in Linux? How do I get Linux Mint to see the phone and how do I know that its being seen?
I never expected to get help this fast! Thanks everybody.
So nobody knows where to find the files I need for QFIL?
Here is a page that talks about Sahara protocol errors and how to fix them. I'm not exactly sure which one applies to me: https://blog.hovatek.com/how-to-fix-sahara-fail-error-in-qfil/
I have a rawprogram file and a patch0 file, but I don't know if they will work with my phone.
I figured out that you can reboot the phone by holding the power button(by watching it disappear and reappear in Device Manager). When I run blank-flash.bat right after rebooting, I get this:
Code:
[ -0.000] Opening device: \\.\COM11
[ 0.001] Detecting device
[ 0.002] ...cpu.id = 286 (0x11e)
[ 0.002] ...cpu.sn = 1010000641 (0x3c336301)
[ 0.003] Opening singleimage
[ 0.003] Loading package
[ 0.006] ...filename = pkg.xml
[ 0.008] Loading programmer
[ 0.009] ...filename = programmer.elf
[ 0.009] Sending programmer
[ 0.131] Handling things over to programmer
[ 0.131] Identifying CPU version
[ 0.131] Waiting for firehose to get ready
[ 3.213] ...SM_SAIPAN 2.0
[ 3.214] Determining target secure state
[ 3.219] ...secure = yes
[ 3.307] Configuring device...
[ 3.317] Skipping UFS provsioning as target is secure
[ 3.317] Configuring device...
[ 3.483] Flashing GPT...
[ 3.483] Flashing partition with gpt.bin
[ 3.485] ERROR: do_package()->do_recipe()->do_flash()->flash_simg()->find_first_package()->not found
[ 3.486] Check qboot_log.txt for more details
[ 3.486] Total time: 3.487s
[ 3.487]
[ 3.487] qboot version 3.86
[ 3.487]
[ 3.487] DEVICE {
[ 3.487] name = "\\.\COM11",
[ 3.487] flags = "0x144",
[ 3.487] addr = "0x28FD74",
[ 3.487] sahara.current_mode = "0",
[ 3.487] api.buffer = "0x2570020",
[ 3.487] cpu.serial = "1010000641",
[ 3.487] cpu.id = "286",
[ 3.487] cpu.sv_sbl = "0",
[ 3.487] cpu.name = "SM_SAIPAN",
[ 3.487] storage.type = "UFS",
[ 3.487] sahara.programmer = "programmer.elf",
[ 3.487] module.firehose = "0x24D1248",
[ 3.487] api.firehose = "0x67D948",
[ 3.487] cpu.ver = "512",
[ 3.487] cpu.vername = "2.0",
[ 3.487] fh.max_packet_sz = "1048576",
[ 3.487] fh.storage_inited = "1",
[ 3.487] }
[ 3.487]
Now I get a different error which you see at 3.485.
I didn't feel like playing around anymore so I took it to Best Buy(where I bought it from).
While they wouldn't fix it, they actually allowed me to exchange it for another one. I chose an open box one (that was probably returned for a stupid reason since its in brand new condition) so I wouldn't have to wait a week for a new one. I also got a $74 refund(to make the exchange even). I never thought I would make out this good(especially since I didn't choose the tech support option when I bought it).
What's gonna happen with the one I gave them? Are they gonna send it back to Motorola? Or just recycle/scrap it? It would be really sad not to fix it since just needs a simple re-flash.
Well I bought this Calypso U318AA from a friend for cheap. It was his sons he got new phone. I bought it to root it. I was just going to do the magical root.. I've rooted several other phones in past. The world wide web has very little info well, no info on this thing. It's a Android 10. I'm not sure of even the best way to unlock the bootloader. I know it doesn't have nothing in developers options. On recovery reboot you can do a recovery boot and a fastboot as well as normal boot. Can't find anything but factory at&t stuff. So any info would be great. Thank you
dorkxperience said:
Well I bought this Calypso U318AA from a friend for cheap. It was his sons he got new phone. I bought it to root it. I was just going to do the magical root.. I've rooted several other phones in past. The world wide web has very little info well, no info on this thing. It's a Android 10. I'm not sure of even the best way to unlock the bootloader. I know it doesn't have nothing in developers options. On recovery reboot you can do a recovery boot and a fastboot as well as normal boot. Can't find anything but factory at&t stuff. So any info would be great. Thank you
Click to expand...
Click to collapse
I just received this phone from at&t. Found out mtk_client will unlock bootloader. so magisk root "should be" available after this unlock. I have not tried yet , i only unlocked bootloader earlier today. will keep looking for anyone else trying this and update as i find any info.
Twrp is working (mostly) for TINNO U318AA. (ATT&T Calypso)
still need to work out data decryption, and FatsbootD mode.
Device Tree: https://github.com/mrmazakblu/twrp-device-att_u318aa/tree/twrp-11
Device Dump: https://github.com/mrmazakblu/att_u318aa_dump
mrmazak said:
Twrp is working (mostly) for TINNO U318AA. (ATT&T Calypso)
still need to work out data decryption, and FatsbootD mode.
Device Tree: https://github.com/mrmazakblu/twrp-device-att_u318aa/tree/twrp-11
Device Dump: https://github.com/mrmazakblu/att_u318aa_dump
Click to expand...
Click to collapse
Phh aoap gsi a11 installs and runs good
mrmazak said:
Phh aoap gsi a11 installs and runs good
Click to expand...
Click to collapse
To clarify, let me tel you all which build version i have installed and outline the steps to get it loaded.
THIS IS NOT INTENDED TO BE STEP BY STEP GUIDE ONLY AN OVERVIEW
WHATEVER YOU DO ON YOUR DEVICE IS AT YOUR OWN RISK
system-squeak-arm32_binder64-ab-vndklite-vanilla
downloaded from :
Releases · phhusson/treble_experimentations
Notes about tinkering with Android Project Treble. Contribute to phhusson/treble_experimentations development by creating an account on GitHub.
github.com
!. Bootloader must be unlocked.
AT&T removed the enable OEM unlock from developer menu, but there is an excellent work around 'tool' to get around this.
MTK CLIENT will allow you to read (pull) stock firmware off from phone, much like spflash tool does, except with this phone and many other newer phones the manufacture has enabled security and authorization files to block sp flash tool , SOOOO, tools like mtk client try to stay a step ahead.
I only used the GUI options with the client, it was very user friendly , the tool has way more options than i needed to mess with.
GitHub - bkerler/mtkclient: MTK reverse engineering and flash tool
MTK reverse engineering and flash tool. Contribute to bkerler/mtkclient development by creating an account on GitHub.
github.com
2. Before flashing gsi, make sure you have pulled firmware from phone, so you have stock super.img. If you don't you will not be able to restore device when / if you mess up the vendor partition.
3. I disabled vbmeta verification .
will need stock vbmeta from pulled firmware.
boot into bootloader, (adb reboot bootloader , or reboot while holding the volume up button. You should get a boot menu)
Code:
fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img
(the last part need to point to you file location where ever it is)
4. Now we need to move from bootloader to fastboot. fastboot reboot command didn't work for me so needed to boot recovery first, then fastboot.
Code:
fastboot reboot
hold volume up button to get boot menu, select recovery
from recovery select reboot fastboot
in the fastbootd connection you will be able to flash gsi
the system area is not large enough to fit gsi , so you will need to remove the /product partition.
Code:
fastboot delete-logical-partition product
fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img
once completed use the screen menu to reboot back to recovery and perform factory reset.
With the exception of needing to use mtk client, the rest of these steps are standard android process. documented in many locations. I go to the android source first for information. \
Moving Fastboot to Userspace | Android Open Source Project
source.android.com
Thanks a lot mrmazak, I'm working on a step by step guide for newbies like me to expand on your steps to unblock and reflash the phone.
I was able to use MRK Client, unlock bootloader and put the phone in fastboot.
The problem I have is to find the right MediaTek driver for the device USB\VID_0E8D&PID_201C
Where did you find them? I tried Google USB driver from ADP but they use different Device ID and all MediaTek driver with same VendorID 08ED have old ProductID instead of 201C.
Any help on MediaTek driver so I can finish the guide and post the link here?
Specifically, I was able to connect via ADB but Fastboot requires a different driver which I'm not able to find
Thanks a lot for your help!
mrmazak said:
I just received this phone from at&t. Found out mtk_client will unlock bootloader. so magisk root "should be" available after this unlock. I have not tried yet , i only unlocked bootloader earlier today. will keep looking for anyone else trying this and update as i find any info.
Click to expand...
Click to collapse
Thats awesome thanks
inglele said:
Thanks a lot mrmazak, I'm working on a step by step guide for newbies like me to expand on your steps to unblock and reflash the phone.
I was able to use MRK Client, unlock bootloader and put the phone in fastboot.
The problem I have is to find the right MediaTek driver for the device USB\VID_0E8D&PID_201C
Where did you find them? I tried Google USB driver from ADP but they use different Device ID and all MediaTek driver with same VendorID 08ED have old ProductID instead of 201C.
Any help on MediaTek driver so I can finish the guide and post the link here?
Specifically, I was able to connect via ADB but Fastboot requires a different driver which I'm not able to find
Thanks a lot for your help!
Click to expand...
Click to collapse
Did not have to install any drivers special.
mrmazak said:
Did not have to install any drivers special.
Click to expand...
Click to collapse
Yes, I had Other \ Android device listed in Device Manager, so I tried disable signed driver and force install of these drivers: https://forum.xda-developers.com/t/...32-64-bit-driver-install-tutorial-m2.3267033/
Now, I have it visible as MediaTek PreLoader USB VCOM Port but if I type "fastboot devices" is not listed.
ADB is able to see it correctly:
adb devices
List of devices attached
AYMB5PKZCUEUUOSC device
When I restart in fastboot with "adb reboot bootloader" the phone restart correctly in fastboot.
I'm not able to unblock the connection between fastboot tool and phone in fastboot mode, I suspect due to missing / wrong driver.
If you have any idea, it would be great!
Found the correct driver. I needed to force Google ADB Driver -> "Android Bootloader Interface" and it works!
They are available here: https://developer.android.com/studio/run/win-usb
Thanks for the help and sorry for confusion, newbie questions
Mod Edit: Quote removed since post deleted.
I received 'not enough space" error when flashed gsi, this is why i delete product partition.
I recall there are fastboot commands to list super.img size, but not sure for super sub-partiton size. there are tools to extract the sub-partitons and it will show individual size.
there must be commands for it in fastboot i think, But i do not know them.\
They deleted the previous post, so I'm copy paste the steps from the blog post.
Pre-requirements
Tested on Windows 11, it should work on any previous Windows versions
Install MTK Client to unlock bootloader: Inofficial MTK reverse engineering and flash tool – which requires Python 3.9 and Git – Downloading Package (git-scm.com) and UsbDk
Download phone image system-squeak-arm32_binder64-ab-vndklite-vanilla.img.gz from Release AOSP 12.1 v410 · phhusson/treble_experimentations
Download Android DevelopersSDK Platform Tools | Android Developers
Download Google USB Driver | Android Developers
Unlock phone bootloaderBootloader must be unlocked to install the new firmware.
MTK CLIENT will allow you to read stock firmware off from phone, except with this phone the manufacture has enabled security and authorization files to block sp flash tool.
Install Python 3.9 from Microsoft Store and Git – Downloading Package and daynix/UsbDk · GitHub, then open a CMD:
mkdir C:\test
cd C:\test
git clone https://github.com/bkerler/mtkclient
cd mtkclient
pip3 install -r requirements.txt
Once installation in complete, start MTK Client with
c:\Test\mtkclient
python mtk_gui
To activate BRUM mode for the phone and connect it to MKT Client
Turn off the phone if it’s on.
Press Volume UP + Volume DOWN and plug the USB cable.
Do not press power button and MKT Client will detect it.
Backup:
In the Read partition tab,
Select all of them and Save to C:\Test\Firmware\Original
It will take about 40min to complete all the operation
Unlock Bootloader
In Flash Tools tab,
Click on Unlock bootloader button
Debug log will show Bootloader: unlock and python windows list
sej - HACC init
sej - HACC run
sej - HACC terminate
sej - HACC init
sej - HACC run
sej - HACC terminate
Progress: |██████████████████████████████████████████████████| 100.0% Write (Sector 0x1 of 0x1, ) 0.03 MB/s
If you restart the phone, you will see a warning that bootloader is unlocked and it will ask you to factory reset the phone.
Install the new firmwareYou need to have Android DevelopersSDK Platform Tools | Android Developers installed to be able to flash the new firmware.
Enable USB Debugging in the phone and connect ADB
Start the phone
Perform a Factory Reset
Restart the phone and complete the initial wizard
Open Settings -> “About Phone” -> Tap the “Build Number” item seven times.
You should get a message saying you are now a developer.
Settings -> “System” -> “Advanced” -> “Developer Options.”
Open the menu and enable “USB Debugging.”
To verify that ADB in installed correctly and is able to connect to the device:
CD C:\Test\Tools
adb version
Android Debug Bridge version 1.0.41
Version 33.0.1-8253317
Installed as C:\Test\Tools\adb.exe
adb devices
List of devices attached
AYMB5PKZCUEUUOSC device
Boot into fastboot with the following command adb reboot bootloader
or reboot while holding the volume up button and select fastboot.
Install Google ADB FastBoot driver in Windows 11Download Google USB Driver | Android Developers as they will be needed to connect the device via fastboot. To install the driver, we need to force the installation in Device Manager with these steps:
Open Device Manager
Right click on Other Devices \ Android device
Select “Update Driver” -> “Browse my computer for drivers” -> “Let me pick from the list of available driver“
Select “Show All Devices” -> “Have Disk“
Navigate to “C:\Test\Tools\usb_driver_r13-windows” and let Windows load the drivers
Select “Android Bootloader Interface” as driver name
Test that Fastboot tool is able to interact with the phone
CD C:\Test\Tools
fastboot devices
AYMB5PKZCUEUUOSC fastboot
Next step is to disable vbmeta verification with the following steps:
Firmware update via Fastboot
While the phone is in the FastBoot mode, type the following:
CD C:\Test\Tools
fastboot devices
fastboot --disable-verity --disable-verification flash vbmeta "C:\Test\Firmware\Original\vbmeta.bin"
target reported max download size of 134217728 bytes
sending 'vbmeta' (8192 KB)... OKAY [ 0.204s]
writing 'vbmeta'... OKAY [ 0.189s]
finished. total time: 0.393s
After vbmeta image is flashed, perform:
fastboot reboot fastboot to restart the phone and enter fastbootd
Check the phone is connecting correctly with fastboot devices
and force the installation of Android Bootloader Interface in Device Manager if needed.
The following step delete product partition so system partition has enough space:
fastboot delete-logical-partition product
Deleting 'product' OKAY [ 0.016s]
Finished. Total time: 0.016s
This command flash the custom rom on system partition:
fastboot flash system "C:\Test\Firmware\system-squeak-arm32_binder64-ab-vndklite-vanilla.img"
Invalid sparse file format at header magic
Resizing 'system' OKAY [ 0.016s]
Sending sparse 'system' 1/5 (255489 KB) OKAY [ 14.939s]
Writing 'system' OKAY [ 7.651s]
Sending sparse 'system' 2/5 (262100 KB) OKAY [ 15.141s]
Writing 'system' OKAY [ 7.705s]
Sending sparse 'system' 3/5 (262104 KB) OKAY [ 15.001s]
Writing 'system' OKAY [ 7.595s]
Sending sparse 'system' 4/5 (261825 KB) OKAY [ 14.752s]
Writing 'system' OKAY [ 7.711s]
Sending sparse 'system' 5/5 (183741 KB) OKAY [ 10.421s]
Writing 'system' OKAY [ 5.832s]
Finished. Total time: 107.885s
Once flash of new rom is completed, you can restart the phone and it will boot using the new rom.
Original post suggested to perform a factory reset.
WARNING: In my case, a factory reset caused a reboot loop and was not able to
If you want to proceed, in the menu on the screen:
Select “Enter recovery” and
Select “Wipe data/factory reset“
Screen on the phone will show
-- Wiping data...
Formatting /data...
Formatting /cache...
Formatting /metadata...
Data wipe completed.
If you missed the previous screen, or clicked the wrong button/option:
restart the phone holding Volume UP,
Select fastboot on the phone
Type fastboot reboot fastboot to reenter fastbootd screen
And repeat the factory reset
Restart the phone and you are up and running.
Restore original firmwareIf you need to restore original rom, use MKT Client tool to write:
vbmeta.bin
super.bin
then close the tool and restart the phone. It will be like new
hi! hope i can get some help. this is my first time using mtkclient but i can't seem to get it to detect the phone. i'm making sure to follow the steps listed of having the phone off first, then press both volume buttons and plug in the usb. on the phone it eventually pulls up a "select boot mode" where i can use the volume buttons to select recovery mode fastboot mode or normal mode boot. i've tried recovery and fast boot modes as well as just leaving it on that select screen but nothing is detected in mtkclient
thanks!
New to the world of droid but am familiar with modding stuff so I'm a semi-noob I suppose. Found myself getting one of these things from the local dollar general and followed this guide to get rid of all the google crap and hopefully speed it up a bit. Bootloader is unlocked, .img posted above is flashed, and it boots up and seemingly works. Can't figure out how to sideload apps nor can I find any type of write up explaining what to do with the tree and dump file posted above. Any help and/or clarification, greatly appreciated. MTKClient, ADB, and Fastboot are all installed and functional. Using Linux Manjaro.
--chuckles b
ltk6260 said:
hi! hope i can get some help. this is my first time using mtkclient but i can't seem to get it to detect the phone. i'm making sure to follow the steps listed of having the phone off first, then press both volume buttons and plug in the usb. on the phone it eventually pulls up a "select boot mode" where i can use the volume buttons to select recovery mode fastboot mode or normal mode boot. i've tried recovery and fast boot modes as well as just leaving it on that select screen but nothing is detected in mtkclient
thanks!
Click to expand...
Click to collapse
Run mtkclient. With the phone already off, hold down both volume buttons and connect the phone to your computer. You should hear the "usb connected" notification sound on your computer and mtkclient will pick up it. As soon as you hear that chime, release the buttons, set the phone down, and don't touch it. The screen shouldn't come on during this step.
Make sure you're ONLY holding down the volume buttons and plugging it in. Don't touch the power button.
If you're still having issues with it not picking up your phone, go through the standard troubleshooting steps: Recheck you followed every step, restart your computer, try other USB ports, try other cables.
*********
FYI this isn't applicable to this process, but should be noted: This phone has a weird way to get into the recovery menu. You have to hold Vol+ and Power, then select Recovery from the menu, THEN immediately press and hold the Vol+ (or Vol- I don't recall at the moment) and Power buttons again until the recovery menu comes up
veryspecialagent said:
Run mtkclient. With the phone already off, hold down both volume buttons and connect the phone to your computer. You should hear the "usb connected" notification sound on your computer and mtkclient will pick up it. As soon as you hear that chime, release the buttons, set the phone down, and don't touch it. The screen shouldn't come on during this step.
Make sure you're ONLY holding down the volume buttons and plugging it in. Don't touch the power button.
If you're still having issues with it not picking up your phone, go through the standard troubleshooting steps: Recheck you followed every step, restart your computer, try other USB ports, try other cables.
*********
FYI this isn't applicable to this process, but should be noted: This phone has a weird way to get into the recovery menu. You have to hold Vol+ and Power, then select Recovery from the menu, THEN immediately press and hold the Vol+ (or Vol- I don't recall at the moment) and Power buttons again until the recovery menu comes up
Click to expand...
Click to collapse
Thanks! that did help.
i was able to get all the way through up to flashing the new rom. I'm getting this error:
fastboot flash system system-squeak-arm32_binder64-ab-vndklite-vanilla.img
Invalid sparse file format at header magic
Resizing 'system' OKAY [ 0.013s]
error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
Sending sparse 'system' 1/2 (262140 KB) error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 201668900 is not a multiple of the block size 4096
OKAY [ 12.568s]
Writing 'system' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
still can't get past this error. i've confirmed my filename, file extensions, and file location. even checked file permissions. the img file is in the same folder as the fastboot command itself.
i also tried the command using the full c:\ path to the img file but it fails the same.
i then restored the phone to the original super.bin and the phone worked like normal. so i went all the way back through the steps starting from the top but failed at the same final step flashing the system.
ltk6260 said:
still can't get past this error. i've confirmed my filename, file extensions, and file location. even checked file permissions. the img file is in the same folder as the fastboot command itself.
i also tried the command using the full c:\ path to the img file but it fails the same.
i then restored the phone to the original super.bin and the phone worked like normal. so i went all the way back through the steps starting from the top but failed at the same final step flashing the system.
Click to expand...
Click to collapse
What are you trying to do? What is the purpose or end result you're hoping to achieve?
I ask because this thread is a bit convoluted and "noobs" looking to just root and tinker might come in thinking they have to do all the steps in this thread to get there.
Like someone wanting an oil change overhearing two mechanics rebuilding a transmission, taking notes, especially where they mentioned "oil," then walking away thinking that's what they need to do.
The tools linked above are great. The mtk one, once I was able to get it running, was how I got past the FRP. For anyone wondering, there's an FRP partition that you can just delete with the tool.
If you're just wanting root, see above for unlocking the bootloader, then stop. I'm 90% certain I achieved root by just following the process outlined the official Magisk page on GitHub.
Can I get some OP/MOD thoughts on breaking this thread up into specific guides with the purpose clearly written in the title?
veryspecialagent said:
What are you trying to do? What is the purpose or end result you're hoping to achieve?
I ask because this thread is a bit convoluted and "noobs" looking to just root and tinker might come in thinking they have to do all the steps in this thread to get there.
Like someone wanting an oil change overhearing two mechanics rebuilding a transmission, taking notes, especially where they mentioned "oil," then walking away thinking that's what they need to do.
The tools linked above are great. The mtk one, once I was able to get it running, was how I got past the FRP. For anyone wondering, there's an FRP partition that you can just delete with the tool.
If you're just wanting root, see above for unlocking the bootloader, then stop. I'm 90% certain I achieved root by just following the process outlined the official Magisk page on GitHub.
Can I get some OP/MOD thoughts on breaking this thread up into specific guides with the purpose clearly written in the title?
Click to expand...
Click to collapse
I understand your questioning. I'm trying to unlock and load aosp firmware, or frankly, anything other than what this device is loaded with since it's horribly bloated, slow and periodically unstable. this is a play phone, i have two of these phones actually.
ltk6260 said:
I understand your questioning. I'm trying to unlock and load aosp firmware, or frankly, anything other than what this device is loaded with since it's horribly bloated, slow and periodically unstable. this is a play phone, i have two of these phones actually.
Click to expand...
Click to collapse
So is mine. I agree with the bloat, which I thought was weird considering the Android 10 version it comes with (Go) is supposed to be a more streamlined version for lower end phones that lack the processing power.
I tend to not do new ROMs unless it's something with a track record and support like Lineage, but after playing around with it and testing some of the functions with things like WIGL, Termux, LSposed, etc, I'm thinking it might be a good Nethunter phone.
After some extensive Googling, and since I doubt this falls under the "you're flashing the wrong build/version" because there's only one variant of this phone, I'd say it might be possible you're not running the right SDK platform package.
Start Android Studio, go to Settings > Appearance & Behavior > System Settings > Android SDK and make sure you have the right platform packages installed (i.e. Android 10, API 29) and updated.