yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] shabbypenguin:
Consider it impossible to brute force their signature, it would take decades.

you dont need access to the bootloader mode, you can use DD to write to the partition, however if the bootloader is locked then it is going to be a very fast bootup time to a screen alerting you your device will no longer work. in the past devices like this have been locked so it wouldnt surprise me if you guys were SOL but stranger things have happened where they made a change. please do note that if teh bootloader is indeed locked, its not just something people will "take a whack at", the last guy i knew personally who would break bootloader protections had a masters degree and was a security researcher as a day job.

presumably you guys have tried out these commands to get into fastboot mode/unlock? they are taken from the alcatel idol 3 guide.
[Android Q&A, Help & Troubleshooting] nyttliv7:
Tried it all ?

But thanks...

My softbricked 5054n is not secured for adb, so can't use adb, just sideload which is useless on this phone.

And my new 5054n is just too good to risk a new brick. The thing most people miss, is that this phone seam to be unbelievably sensitive to any changes in the system = soft brick ?

We've tried everything regarding bootloader / fastboot, but it's probably hidden and secured ?

Hope we're lucky enough to find a way soon... My hopes for my dead phone goes to Qualcomm HS-USB Qdloader and tools, as soon as I find or learn how to produce MPRG8909.hex and 8909_msimage.mbn.

Or if nothing changes, I have parts for repair, hehe ?
[Android Q&A, Help & Troubleshooting] shabbypenguin:
so what happens when adb reboot bootloader is executed on a normal working device?
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
I tried it, I keep getting "unknown" or device not found.
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
Wth, just realized ADB interface drivers not installed. HTC site doesn't have drivers for this device.
[Android Q&A, Help & Troubleshooting] nyttliv7:
Htc?

---------- Post added at 06:20 AM ---------- Previous post was at 06:19 AM ----------

Reading through file after file in the system since a while back, and for sure there's a bootloader (even if it's locked and hidden). This is a line from "last_kmsg"

androidboot.bootloader=L8D6U0U0BR00
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
Sorry, I'm thinking about my wife's phone, I have also been working on her device well.
[Android Q&A, Help & Troubleshooting] nyttliv7:
Another line confirming our guess about Pixi355:

pixi355_board_id = 4
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
I simply can not acquire 5054n adb drivers. Even here

http://www.skyneel.com/2015/05/download-latest-alcatel-usb-drivers.html
[Android Q&A, Help & Troubleshooting] AesopRock127:
I've had some odd problems with this phone but different from yours. I had to shut off lte and use regular 4g (or just use wifi) to send or receive MMS messages but just recently I haven't been able to even receive any MMS with wifi on, I have to shut it off and use 4g or it just gets stuck on 'downloading' until I shut off wifi.

Obviously different problem then yours but thought it worth mentioning
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
I acquired adb drivers, I'll input commands again.
[Android Q&A, Help & Troubleshooting] Vexx421:
I ran into that problem too for a minute. I solved it although I cant remember how..
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
ADB drivers installed, opening cmd under Run as administrator, entering command adb reboot-bootloader the phone upon entering command rebooted the device back to the default desktop.
[Android Q&A, Help & Troubleshooting] Vexx421:
Device just reboots like normal as far as I can tell.
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
A double screen flash but very very quickly as if to say it was attempting to do something, but then defaulted to a typical boot up.
[Android Q&A, Help & Troubleshooting] kirito9:
Yeah, others have tried before when I ported TWRP recovery but as users have pointed out, the manufacturers removed fastboot mode. That is why you won't see a fast boot screen upon entering the commands "and reboot boot loader".

Flashing recovery is possible yes with apps such as Flashify or Rashr but I wouldn't risk it seeing that you do not know if the device is unlocked or locked.
[Android Q&A, Help & Troubleshooting] jay251:
Root alcatel one touch fierce xl

Hello;) THIS IS EXACTLY WHAT YOU HAVE TO DO... GET ROOT ON ALCATEL ONE TOUCH FIERCE XL... FIRST GO TO kingroot.net DOWNLOAD v4.80.. THEN ON YOUR DEVICE GO TO SETTINGS THEN ENABLE UNKNOWN SOURCES.. THEN INSTALL KINGROOT V4.80. THEN GO TO DEVELOPER MENU AND TURN ON DEBUGGING AND OEM UNLOCKING.. THEN GO TO YOUR DOWNLOADS OR FILE MANAGER AND LOCATE THE KINGROOT APK YOU DOWNLOADED AND INSTALL IT.. THEN YOU HAVE TO GO TO THE PLAYSTORE AND GET SUPERSU ME PRO(FREE VERSIONS DO NOT WORK) DOWNLOAD IT AND GO BACK TO KINGROOT OPEN IT RUN ROOTING EXPLOIT..ONCE KINGROOT HAS ACHIEVED ROOT ON YOUR DEVICE.. RUN PURIFY.. ONCE PURIFY HAS COMPLETELY FINISHED USING YOUR TASKER GO TO HOME SCREEN AND THEN MENU (APPS) AND OPEN SUPERSU ME PRO PRESS FOLLOW THE INSTRUCTIONS AND PRESS THE BLUE BUTTON WAIT UNTIL STAGE 1 HAS COMPLETED.. USING YOUR TASKER AGAIN GO BACK TO KINGROOT AND RUN EXPLOIT ONCE AGAIN GAINING ROOT AND THEN PURIFY AGAIN.. ONCE COMPLETED USING YOUR TASKER GO BACK TO SUPERSU ME AND RUN STAGE 2.. ONCE COMPLETED KINGROOT AND PURIFY WILL BE REMOVED AND SUPERSU INSTALLED.. REBOOT YOUR PHONE AND THEN OPEN SUPERSU IT NEED TO BE UPDATED FOLLOWING THE INSTRUCTIONS ONCE UPDATE COMPLETES REBOOT YOUR PHONE OR IT MAY REBOOT ITSELF YOUR ALCATEL ONE TOUCH FIERCE XL IS NOW ROOTED...;) YOU CAN TURN OFF DEVELOPER MODE AND UNCHECK UNKNOWN SOURCES IN THE SECURITY MENU IF YOU CHOOSE AND YOU CAN NOW DOWNLOAD BUSYBOX..ETC., ENJOY!!! YES IT WORKS MINE IS ROOTED PERMANENTLY UNTIL I REMOVE ROOT NO DATA CONNECTION IS REQUIRED TO ROOT USING KINGROOT V4.80 AS THE PREVIOUS VERSIONS DID REQUIRE IT.. YOU ARE ONLY USIN IT TO RUN SUPERSU ME EXPLOIT TO OBTAIN PERMANENT ROOT ON YOUR DEVICE.. AGAIN ENJOY!!!
[Android Q&A, Help & Troubleshooting] void513:
just a thought what if fastboot is there but it has a totaly dif set of oem commands and possibly dif usb drivers get to fastboot
[Android Q&A, Help & Troubleshooting] Vexx421:
Thats a lot of work when you can just install kingroot 4.80 and run the su zip through teminal and use the su app to install as system.

---------- Post added at 01:38 AM ---------- Previous post was at 01:33 AM ----------

There is no fastboot file in system root folder like there is an adb file to recognize commands
[Android Q&A, Help & Troubleshooting] AesopRock127:
Not to be mean but way to come in a thread yelling (caps lock?) about some simple Simon crap that not only everyone here knows how to do but knows how to do better... Where did you come from and how is this post relevant to the topic? Lol no offense or anything but geez I'm SMH here. Also SuperSU Me Pro is a good way to brick this phone which you would know if you read this thread and there's a better safer way to do this as Vexx pointed out, which you would also know if you read this thread. -____-
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
I was thinking the same thing
[Android Q&A, Help & Troubleshooting] void513:
heres a site with some intersting info on qualcome hsusb 9008 mode

http://www.androidbrick.com/unbrick...-you-have-the-right-kind-of-rom-qhsusb_dload/

and another with dif prog use on qualcome hsusb 9008 mode

http://www.androidbrick.com/ultimat...ide-snapdragons-are-unbrickable-qhsusb_dload/
[Android Q&A, Help & Troubleshooting] TwentyFoursWorld:
Yes void, we've looked through both of these sights when we first figured out our Hs_USB mode.

But the only thing stopping us, is we never found our own source code.

Again. We could only get so far(actually really far) if we had source code (￣(ｴ)￣)ﾉ
[Android Q&A, Help & Troubleshooting] void513:
Sorry

keep reading about bootloader being lock so was looking for other was to unlock it
[Android Q&A, Help & Troubleshooting] nyttliv7:
Isn't it "funny" how so many late posts just prove they really didn't read through the thread??

Welcome to "repeat repeat repeat"...

---------- Post added at 04:12 AM ---------- Previous post was at 04:08 AM ----------

Just a reminder:

FORUM RULES

1. Search before posting.

Use one of our search functionsf before posting or creating a new thread. Whether you have a question or just something new to share, it'sr very likely that someone has already asked that question or shared that news.

Yeah right?

---------- Post added at 04:19 AM ---------- Previous post was at 04:12 AM ----------

Dreaming about dual boot, replacing boot partition or overwrite any possible partition with alternative bootloader (boot) or recovery ???

I know, just dreams, hehe ?
[Android Q&A, Help & Troubleshooting] Nyzai22:
Metro

Lol I went there and didn't tell them that I rooted and wasn't turning on but do you have to pay a $15 fee for replacement if not then your one lucky camper :):cool:
[Android Q&A, Help & Troubleshooting] mrnmcII:
Has anyone gone to a windows 10 version owner to see if there is a way to rescue that device if bricked
[Android Q&A, Help & Troubleshooting] liljefflito:
how did you get sense 7

Please help me install sense 7
[Android Q&A, Help & Troubleshooting] shabbypenguin:
oh you already tried twrp? is your device tree up somewhere?
[Android Q&A, Help & Troubleshooting] kirito9:
Lol, well I had it before and deleted after a user tried and it bricked their device. That was before knowing that MetroPCS removed fastboot mode. They flashed with the TWRP with flashify and then the phone bricked (probably locked bootloader which can't be unlocked).

I can make it again. I used two devices to compare the recovery partitions. I unpacked the stock recovery.img and stock boot.img and compared the mount points with the TWRP for the Idol 3 since it's Alcatel and would (although not same SoC) have similar partitions like modemst1, modemst2 and so on.
[Android Q&A, Help & Troubleshooting] shabbypenguin:
ok so you did a repack then? what tool did you use to unpack em? once you compared the mounts what all did you do then?
[Android Q&A, Help & Troubleshooting] kirito9:
Yeah I repacked it and it was the ported TWRP. I do not have the device so it was just the first test. Some mount points I wasn't sure about so I repacked that ported TWRP to test but since it bricks the device. I decided to discontinue working on it until there is a backup and restore guide for this device.

I used this tool to unpack and repack Carliv Image Kitchen.
[Android Q&A, Help & Troubleshooting] shabbypenguin:
just so im clear, what exactly do you mean ported twrp? what files did you copy over to the fierce's recovery?

https://onedrive.live.com/redir?res...4516&authkey=!AInZDjwaVMPcZYA&ithint=file,img

this is the stock recovery unpacked and repacked. nothing was done to it other than breaking the signature. this file could break your phone so dont touch it unless you want to risk it. if this flashes and yoru device is fine afterwards then it lets us know your device is capable of running unsigned images. at this time however i do believe that we need to find a way to access fastboot to issue a command, lg tmobile/metro devices used a partition that once zero's out allowed access to fastboot this may be a similar thing.
[Android Q&A, Help & Troubleshooting] kirito9:
Can you upload that recovery to another hosting site, I can't seem to download it. Yeah when I say ported I copied not to the fierce's recovery but over to the already working TWRP. The kernel for the fierce stock recovery was copied over along with a few edited files already in TWRP recovery like the default.prop file, init.rc file etc. What do you mean breaking the signature? Is the signature broken after unpacking and repacking a stock recovery and flashing to device? Do you have a link to the lg tmobile/metro device that had that partitioned removed?

EDIT: I got it downloaded.
[Android Q&A, Help & Troubleshooting] shabbypenguin:
all the other kernel files like t he DT.img and other stuff should have been as well. its easier taking the ramdisk of the twrp recovery and moving it over to the fierce's as then you dont mess anything else up within the image. with a locked bootloader it only boots images that pass a signature check, if i take it apart and put the image back together there is no way for me to match that same signature meaning it will trip the bootloader flags if they are there. with devices like this its best to do a repack of the stock recovery because if something goes wrong then you know its either the bootloader, or you packed the image incorrectly, vs with adding in twrp that could just not be booting and then you have no idea what the issue is.

lg l3, stylo and many more, if it came out on t mobile/metro in teh last 2 years then root and zeroing out the LAF partition gave you access to the fastboot mode.
[Android Q&A, Help & Troubleshooting] kirito9:
Ahh, thanks for that knowledge. Like I said before, this is my first time working with Qualcomm devices so I too am a noob :). I wouldn't give the TWRP another try until there is a unbrick method or we can at least get to fastboot mode. I will check those devices and see how they did it. Hopefully we can find a way to get to that fastboot mode :highfive:.
[Android Q&A, Help & Troubleshooting] nyttliv7:
[MENTION=5515628]kirito9[/MENTION] or anyone, can you recommend somewhere I can learn the details about all specific partitions, what they are/do and specifically about the boot partition, maybe an extracted one so I can see what's really there ? Any boot, but possibly a similar one to the one we have, based on a qualcomm/lollipop one? Really want to learn more ?
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
[MENTION=631273]Chainfire[/MENTION] have you had a chance to play with this device yet?
[Android Q&A, Help & Troubleshooting] Nickalick:
Guys i have flashed just about every twrp alcatel has to my phone not one bricked it use flashify worked for me about 10 diff recovery flashes i did and all was good if it did not work i flashed stock and wala worked and if u do the bpotloader unlock in diag then it seems to run unsighned fine well atleast for me it did

---------- Post added at 11:53 AM ---------- Previous post was at 11:48 AM ----------

If u want to no all there is to no about mem locations and partishun structure/size use emmc raw tool and load the raw partition that is in the dump on this thread i will shoot a screen shot the 4gig file is actuly only 2 and its holds the gpt for this device and has corect partition layout and sizes
[Android Q&A, Help & Troubleshooting] kirito9:
Here are a few good explanations. Look here, here and here

Find my extracted boot.img for Alcatel 5054N here.
[Android Q&A, Help & Troubleshooting] Vexx421:
Aren't Signature files are broken anytime you change something. Even if so much as a period gets changed I thought keys, sigs and certs dont match up anymore. Eg. A pgp key or any encrypted file.
[Android Q&A, Help & Troubleshooting] Nyzai22:
Safe mode

So am I the only one that screens turns on and shows the Alcatel logo then turns off?

And if I'm bricked can I still do that spamming thing?
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
Just hold volume down while booting up. If you are bricked I wouldn't think you can do anything at all.
[Android Q&A, Help & Troubleshooting] TwentyFoursWorld:
Yes, the on and off screen is normal. It should stay black as your led (if on) will stay lit. It is known as hs_USB mode

If you are bricked. Then sadly idk if safe mode will work.

Since bricking means not getting past the boot screen.
[Android Q&A, Help & Troubleshooting] nyttliv7:
Yes, it didn't work on my one that freeze on boot...

---------- Post added at 11:30 PM ---------- Previous post was at 11:25 PM ----------

Thanks :)

So, viewing the "inside" of our boot.img, where is the bootloader? What is locked, all or just specific parts? Just curious! Is it impossible to clone it without the lock/encryption? Is it possible to see the hardware code?
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
The bootloader signature would get broken or modified if you added anything to the .img, we would have to be able to unlock the bootloader to let us run unsigned sigs.
[Android Q&A, Help & Troubleshooting] kirito9:
What he said, and I don't think there is a specific file in the boot.img that is the bootloader, I think. Not sure. I'm new to qualcomm SoC and can only really understand if I get a qualcomm device. Hardware code, mmm don't think so but lol again, I'm just as noob as you with qualcomm.
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
I'm about ready to seek a dev for hire and pay them if they can do this. I could just as easily go buy a different phone that's already been unlocked and a custom twrp is already out there for it. But now it's gotten personal with this particular device. I'm the type that has an extremely hard time letting go of a project until I see it to the end.
[Android Q&A, Help & Troubleshooting] void513:
here a question if you turned unlock off in developer mode dose it stay off even after reset.or is it automatic switch back on when you reset phone.another question also since some able flash recovery are able boot into it. reason i ask is a custon recovey that might give adb and fastboot in recovery.to unlock bootloader
[Android Q&A, Help & Troubleshooting] nyttliv7:
Thanks for clarifying :)

I wish it was possible :(

[MENTION=5515628]kirito9[/MENTION], shipping of my device cost the same as a new phone :(

---------- Post added at 12:43 AM ---------- Previous post was at 12:42 AM ----------

Thanks for clarifying :)

I wish it was possible :(

[MENTION=5515628]kirito9[/MENTION], shipping of my device cost the same as a new phone :(
[Android Q&A, Help & Troubleshooting] kirito9:
Lol no, do not bother with shipping your device. I'm not a developer in anyway or at least not yet. I still have a long way to go. It may take a couple months to actually acquire all the knowledge about Qualcomm as I did with Mediatek, so until I get my hands on a Qualcomm device, try to learn as much as you can. These things take quite some time and in the end, the information you read will be worth it. Good luck :fingers-crossed:
[Android Q&A, Help & Troubleshooting] nyttliv7:
I'm not sure what phone I had (LG or htc), but once when I couldn't reach fastboot, I had the cmd window open with command "fastboot devices" written, cmd showing "waiting for phone", during the boot on a phone that was stuck in a boot loop. Weird, yes, but it worked after a few attempts :)

Haven't tried yet with this phone, but I just wonder if it sounds totally stupid? I mean, even if the bootloader is hidden, it has to be part of the boot time, somewhere? I don't know, maybe worth a try?

---------- Post added at 03:05 AM ---------- Previous post was at 02:07 AM ----------

Interesting!

"Q2) How do I disable 'fastboot' for my commercial device?

A2) Personally, I would like to see commercial devices leave 'fastboot' enabled.* It goes in the spirit of Android Open Source Project where end users and developers have access to the source code to allow them to modify it and upgrade their device over usb using 'fastboot'.* However, if OEMs or network providers want to lock down 'fastboot' it can be done by disabling the keypad and usb driver in bootloader.* This can be customized in the following files:

lk/app/aboot/fastboot.c

lk/app/aboot/aboot.c"

https://www.codeaurora.org/blogs/little-kernel-based-android-bootloader
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
Our chipset being MSM8909 I don't see it on the list YET. I would imagine if we got into contact with Travis, Brian, or Dima we might get a more specifically aimed set of answers.
[Android Q&A, Help & Troubleshooting] nyttliv7:
I wouldn't mind if they joined our thread, hehe :)
[Android Q&A, Help & Troubleshooting] void513:
anyone know what aboot partion for

---------- Post added at 01:00 PM ---------- Previous post was at 12:50 PM ----------

will researching aboot i cam across this program that might help

http://xdaforums.com/galaxy-s2/orig-development/tool-updated-09-06-14-efs-professional-t1308546
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
The*Application Bootliader, (aboot) boots the Android kernel/Recovery kernel. It is the mechanism to download images onto the device from a host machine (like Windows/Linux PC). On Samsung devices it runs the ODIN protocol on the device.
[Android Q&A, Help & Troubleshooting] TwentyFoursWorld:
So i recently just tried this, but when i tried to read phone info it said (SPC was denied by phone)

whats SPC? also the tool seems great, but i wasn't sure why it couldn't connect....

any ideas??? :rolleyes::eek::good:

UPDATE: so i got it connected. i had the ADB run and then re opened the tool, and it reads my phone. I also unchecked Send SPC.

now what? im scared to do further tinkering with it :p
[Android Q&A, Help & Troubleshooting] void513:
from what i gathered spc is a programers code here a link that expains it a little more

https://forums.wirelessadvisor.com/threads/spc-service-programming-code-faqs.14337/

i notice alot of app used to flash phone from pc req the spc code.and not sure if we be able to get it from a bricked phone
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
I've been digging into this device pretty hard the past two days, I've found my SPC code, I've found that the toggle switch to OEM unlock mode in dev options isnt actually functional. I had to access the google.android.partnership.rlz receiver within the phone to actually turn it on. Our android SDK is 22, and from what I'm seeing if I can unlock this damn thing, I should be able to sdk adb using "fastboot oem unlock" theoretically with my SPC and the adb call I should at least get some kind of a reaction from this device. I'll keep messing around and see what happens.
[Android Q&A, Help & Troubleshooting] void513:
couple of places says the spc is unique and dif for each phone but if you think about it how would support flash a phones that bricked or unbootable,there has be a specific spc that support uses to fix the phone.but i have no idea what it could be.also heres a list of sercret menus and how to get them for alcatel device http://greentooth.xtgem.com/alcatel have no way of try right now since my phones brick but some else could try them.
[Android Q&A, Help & Troubleshooting] Psych0Smil3s:
Pop off the back of your phone, get your imei, use a imei to spc converter. You MIGHT be able to boot into download mode and access the phone that way. I've accessed all the secret menus. There are a few functions that were switched off that I manually turned back on.
[Android Q&A, Help & Troubleshooting] void513:
ok got a some what working code be sure not to check send spc when you try to connect or will reject spc and dissconnect you also here a online working imei converter to get your spc http://imei.org/meid-esn-imei-converter/ and also not sure if because the way my phones bricked but when i connect with efs pro qualcomm nv tool i get a msg unable to read beyond the end of stream
[Android Q&A, Help & Troubleshooting] void513:
might want look into this app also since we got spc code now for our phones

http://www.androidbrick.com/download/latest-qpst-2-7-build-422-qfil/

and yea i know this might be a reapeat of a post without having to go through 50 some page of this thread

---------- Post added at 05:11 PM ---------- Previous post was at 04:30 PM ----------

the last app i post above one of it components the software download say it has be in diagnostics mode to backup or flash the phone