My Moto G survived the elements for a year now, with abuse, drops, water and a llot of flashing.
Yesterday, i decided to use Lollipop Brazil rom from here. It all went well but after some testing and just checking out new features i downgraded to 4.4.2 rom. Lollipop is imho not very fast compared to latest 4.4.x...
The device worked without problems, until i got the OTA update for 4.4.4. When it was installing in the stock recovery, the screen went dark. Since that moment no life at all! The LED works a few minutes when i charge it, but other than that. I have a nice black -not working- device.
Then I tried this & this without any luck.
I'm booted with driver verification disabled, installed "qhsusb_bulk" driver from Riffbox Jtag. It can see the device but can't flash a new bootloader.
Fastboot don't work, because I can't even power on the device....
I'm fed up, this is my main device and I didn't expect this. After all, I flashed CM12 5.0 builds in the past and reversed to 4.4.x without any hassle!!
Can I do something? I have the right torx screwdrivers.... something... *sigh* It can't be that just a few lines of code f*ck up this device....
{
"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"
}
You should have just installed one of the custom roms instead. As far as I can tell, there's no difference between those and the official rom other than a few extra features. The brazillian rom you installed came with the new bootloader and that makes it likely to hard brick your phone if you try to downgrade back to kitkat.
jman1234 said:
You should have just installed one of the custom roms instead. As far as I can tell, there's no difference between those and the official rom other than a few extra features. The brazillian rom you installed came with the new bootloader and that makes it likely to hard brick your phone if you try to downgrade back to kitkat.
Click to expand...
Click to collapse
I tought the official rom was the most stable one...
So what is plan B?
dwensch said:
I tought the official rom was the most stable one...
So what is plan B?
Click to expand...
Click to collapse
I believe there is a guide to "un" hard brick your phone somewhere around this forum. Try searching [guide] moto g hardbrick or something similar... But since you upgraded the bootloader this most likely will not work. Sorry for the bad news... Wait for new methods or jtag your phone. Or send it in to motorola... Try running the qboot.exe in windows xp sp3 compatibility mode.
skyguy126 said:
I believe there is a guide to "un" hard brick your phone somewhere around this forum. Try searching [guide] moto g hardbrick or something similar... But since you upgraded the bootloader this most likely will not work. Sorry for the bad news... Wait for new methods or jtag your phone. Or send it in to motorola... Try running the qboot.exe in windows xp sp3 compatibility mode.
Click to expand...
Click to collapse
XP SP3 mode didn't work... and I don't think Motorola will fix it for free, since i replaced the screen 2 times already...
Gonna need to save money for new phone now, damnit
Is there a way to extract 5.0 bootloader and force "install" to my device?
dwensch said:
XP SP3 mode didn't work... and I don't think Motorola will fix it for free, since i replaced the screen 2 times already...
Gonna need to save money for new phone now, damnit
Is there a way to extract 5.0 bootloader and force "install" to my device?
Click to expand...
Click to collapse
The bootloader should be in the zip file you got the rom from. It should be called motoboot.img
But you need to be able to blank flash your phone to flash a new bootloader if its hard bricked. Your best bet at this point in time would a jtag. Just be patient and wait a few weeks, theres bound to be a solution soon...
OKay, i will have patience. Still, very anoying.. But i understand it, because the new ART software changes everything... I hope somebody will take the time and make some solution...
dwensch said:
OKay, i will have patience. Still, very anoying.. But i understand it, because the new ART software changes everything... I hope somebody will take the time and make some solution...
Click to expand...
Click to collapse
No it is not because of ART. That doesn't have anything to do with your problem. When you flashed firmware to upgrade to Lollipop you must have also flashed the new bootloader. You might have used a command called "fastboot flash motoboot motoboot.img" When you do this, the updated bootloader will not boot to kernels below android 5.0. So when you tried reflashing 4.4.4 or lower on your device, you must have used a command like "fastboot flash boot boot.img" Since you flashed a kernel that the bootloader does not support your phone became "hard bricked" more or less.
I did the exact same procedures and having the same problem.Someone please help
sauravbiswas said:
I did the exact same procedures and having the same problem.Someone please help
Click to expand...
Click to collapse
The bootloader should be in the zip file you got the rom from. It should be called motoboot.img
But you need to be able to blank flash your phone to flash a new bootloader if its hard bricked. Your best bet at this point in time would a jtag. Just be patient and wait a few weeks, theres bound to be a solution soon...
I'll help you: PM me I'm Dutch also!
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
harshhemnani said:
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
Click to expand...
Click to collapse
My bootloader is'nt working so can't load a custom recovery
He can't do that if the phone does not even turn on...
I just hope to get a working solution fast....coz this is my daily driver and I m screwed
harshhemnani said:
Boot into some custom recovery and wipe system.
Then install some custom ROM or stock 4.4.4
Click to expand...
Click to collapse
I wish it was that simple! Did you even read the topic?
I hope somebody can fix mine and others problem. Because i spent allot of money on this phone *sigh*, there is nothing wrong with the hardware.
In the past year i replaced the LCD 2 times, 1 cover and 1 backhousing. So the hardware is functioning perfect now. It makes me sick that just a few lines of code destroy the bootloader software!!!
Why was this not stated in OP from Brazil Lollipop? Yeah, it says it can "brick the phone', but that warning is so generic..... I wish he was more specific?
Im gonna buy a new phone in the coming weeks, because IMHO, this phone is RIP. But if somebody is able to get it working again, i would be very grateful.
Well to be fair, you should have known that flashing an OTA meant for xt1033 on xt1032 would have caused problems.
dwensch said:
I wish it was that simple! Did you even read the topic?
I hope somebody can fix mine and others problem. Because i spent allot of money on this phone *sigh*, there is nothing wrong with the hardware.
In the past year i replaced the LCD 2 times, 1 cover and 1 backhousing. So the hardware is functioning perfect now. It makes me sick that just a few lines of code destroy the bootloader software!!!
Why was this not stated in OP from Brazil Lollipop? Yeah, it says it can "brick the phone', but that warning is so generic..... I wish he was more specific?
Im gonna buy a new phone in the coming weeks, because IMHO, this phone is RIP. But if somebody is able to get it working again, i would be very grateful.
Click to expand...
Click to collapse
jman1234 said:
Well to be fair, you should have known that flashing an OTA meant for xt1033 on xt1032 would have caused problems.
Click to expand...
Click to collapse
No there is no problem with the ota stuff. Its the fact he flashed new boot loader and tried to downgrade. That is the root cause of the problem. As I said be patient and wait a few weeks, there's bound to be a new solution. If you want I can send some partitions from my phone if you want. Lollipop is very new so solutions are scarce.
Exactly, wait a while until the right files are out and you'll be able to revive your phone.
The same problem here, we have to wait for Mbm-ci 5.0 for bootloader 41.18 right?
i installed lollipop to my xt1034 GPE and try to be root, the phone stuck on boot animation and i tried go back to 4.42 and works, but when i update from ota to 4.4.4 some go wrong and my phone death, also i cant enter to bootloader
Related
Hi, i just bought a samsung infuse and i was looking for an ICS rom and i found the cm9 unofficial http://forum.xda-developers.com/showthread.php?t=1601844 this one
and i flashed like the thread says and everything went good, ics started like a charm but then i turned off my phone to get into the recovery but i found out to be in a huge problem
My phone wont boot, it goes directly to the recovery (cwm 5.5.0.4) and it looks like a broken screen (sort of, rainbows) its usable but it wont boot, i even tried to reflash it
Would somebody help please?
riikiiee said:
Hi, i just bought a samsung infuse and i was looking for an ICS rom and i found the cm9 unofficial http://forum.xda-developers.com/showthread.php?t=1601844 this one and i flashed like the thread says and everything went good, ics started like a charm but then i turned off my phone to get into the recovery but i found out to be in a huge problem My phone wont boot, it goes directly to the recovery (cwm 5.5.0.4) and it looks like a broken screen (sort of, rainbows) its usable but it wont boot, i even tried to reflash it Would somebody help please?
Click to expand...
Click to collapse
Well I guess you didn't read all the way til post 3 of the thread where you pulled the CM9 unofficial ROM...BTW your probable gonna get flamed since you also didn't make a run thru the the Q&A...since this has been address, well I ran out of fingers and toes to count how many times...but
Go back the op [Firmware][ICS]UNOFFICIAL CM9 for the Infuse 4G... go down to post 3, and do a little reading, maybe you should of did some more homework before jumping in, but hey good on you for just jumping and not looking where you might land...
If you require more reading (i suggest) see my links below...ok,
Good luck
yes i know i will get flamed, and i did read the 3rd post about the bootloaders
but i just wanted to know if there is another way to do it, and since English is not my native language, i don't understand everything very well, but thanks
riikiiee said:
yes i know i will get flamed, and i did read the 3rd post about the bootloaders but i just wanted to know if there is another way to do it, and since English is not my native language, i don't understand everything very well, but thanks
Click to expand...
Click to collapse
Ok understood, just relax and re read it again, and go thru the Q and A seciton.
What part are you having trouble understanding...?
---------- Post added at 11:17 PM ---------- Previous post was at 11:10 PM ----------
What I suggest is start over:
Use the one click back to stock and then use the one click to install CWM...which is what you need to get CM9 ics ok,
so first one click back using qkster method:
http://forum.xda-developers.com/showthread.php?t=1524081
1. Put your phone into Download Mode.
2. If you have not used Heimdall, you will need to set up the driver for device recognition.
3. Once your device is connected, the DEVICE STATUS should show: CONNECTED. The long FLASH bar will also turn on for flashing.
4. Click on the FLASH button. (In my opinion: I recommend that you do this in a safe environment. Do not disturb your phone will flashing this firmware. Turn off Antivirus. Do not run any other programs, upload/download/youtube/burning DVD etc)
5. Once it has completed, your phone will reboot. You will hopefully see the ATT logo and reboot into STOCK UCLB3.
6. If it did not work, you will have to put it back into DOWNLOAD mode and reflash a second time, with the FLASH BOOTLOADER box checked. This is more likely if you never had proper Gingerbread bootloaders on your phone, if you are coming from FROYO or if you never had Odin a Gingerbread leak to get your bootloaders.
Then use one click from same op, qkster method:
http://forum.xda-developers.com/showthread.php?t=1524081
post 2... After you have flashed the UCLB3, some of you may want to have Red ClockWorkMod (CWM) recovery to flash another ROM.
Put your phone back into DOWNLOAD mode after your phone has booted up.
Then reinstall the cm9 zip, once you reach this stage, you will have to flash it twice..ok this file...
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
timmetal6669 said:
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
Click to expand...
Click to collapse
Yes and No...
It is a step up for the infuse, well it will be...
The problem is people are not doing their homework, and have never flashed a ROM, much less know what the letter ICS or CM9 even are, and yes it has brought some challenges but for those of us that have installed and ran it on this phone and other phones, I don't mind assisting others, but they have to do the reading and homework for them self's...
Yes you have your opinion and I don't disagree or agree, but I do hope the ROM with be brought up fully functionally, and it will with the Developer we have working it and others who are "testing" it, the ones who are familiar with...
Alright thanks mate, right now im installing the driver for heimdall, I already read everything you said and the links you shared
Thanks again, you just saved another noob
When your up and running for good, let us know, and don't forget to thank the Dev that provided you with the tools you needed...not me...just pointed you there...
Yes I will
timmetal6669 said:
Cwm9 is the devil! Everyone who had tried to use it for anything except putting itself on the phone has had one problem after another. Call it experimental or call it in alpha.. Whatever call it as it is a bricking virus. Just cause it was all good through ginger bread doesn't mean it will be the best forever. Pull it off the site already. it affects all phones that use it. I have an epic 4g and it nearly bricked mine about 3 months ago. Check out some.of the other forums that this alpha virus had spread to. Nearly every brick had cwm9 mentioned in it.
Click to expand...
Click to collapse
No one who actually FOLLOWED THE INSTRUCTIONS has had an issue.
I challenge you to find ONE person who has bricked an Infuse with CM9. The only time in the CM9 flashing process one might brick is when flashing the bootloaders to get rid of rainbows - and I have PLENTY of warning that flashing bootloaders is a dangerous and risky process.
Similarly, no one has bricked an I9100 flashing CM9 either, unless the recovery they were flashing away FROM was defective (such as the initial I777 UCLD3 recovery repacks) - but that same defective recovery caused hardbricks for people flashing even rooted stock with no CM9 involvement.
Task650 was right when he replied to you in the I777 thread - he contributed more to XDA when he took a dump this morning then when you spread your bull****.
Thank You "E"....well put...:thumbup: :thumbup:
I hate it when jokers like that guy pipes in, when trying to help others...the op admits to not to be good at his English...
hey, i downloaded everything that i needed
and even a little bit more
but i haven't been able to start OneClick
put my phone into download mode, install drivers for heimdall
I tried with heimdall frontend in the flash tab, just like the tutorial
add every partition, and then when i click Flash
this is what it says
"Initialising connection...
Detecting device...
ERROR: Failed to access device. libusb error: -12"
any idea?
ok I am not trying to insult you just wanna ask a few question ok,
{
"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"
}
You sure your in Download mode...does it look like this your phone?
I go into download mode like this: I take out my battery, plug in the cable while holding both volume buttons i pop my battery in...bamm download mode...
you will see the pic above....
But once it does go into dl mode carefully place the phone down with still connected to the cable then...
if so then you click the one click to open it and you see the word "connects"..in green, click the button below it flash...
and then it should run thru you will see the blue line go across your phone will lots of remarks running thru on the screen in the one click window....ok
dont worry, but yes i know how to put it into download mode
but the thing is that i downloaded oneclick but i cant run it
riikiiee said:
dont worry, but yes i know how to put it into download mode but the thing is that i downloaded oneclick but i cant run it
Click to expand...
Click to collapse
1) ok, have you tried different usb port and or cable...
2)re-download the one click file again...here is a link
http://db.tt/Y2XEPwGv
3) And this the link to give you CWM, you run this after you have install above and you will have to put into download mode for this....and you will hear the lady voice talking that means it is installing cwm...ok but first do the above
http://db.tt/WEJyXywV
riikiiee.....status check my friend...
elostish venus.
Hey BigJoe
the problem was my computer, i used other one I have here, and now Im good and running GB I really appreciate your time and your help.
From now and on I will read everything I have to read
And thanks again mate, you really helped
riikiiee said:
Hey BigJoe
the problem was my computer, i used other one I have here, and now Im good and running GB I really appreciate your time and your help. From now and on I will read everything I have to read
And thanks again mate, you really helped
Click to expand...
Click to collapse
No problem....glad you found out what the real problem was...
Any time ...:thumbup:
goritat the
Yeah, now back to ICS again
the right way now
According to the Verizon Galaxy S5 Update Page:
This software update provides the latest Android™ security patches, fixes an email issue and updates the Amazon Shopping app.
Email update:
Fixes an issue that prevented Outlook® 2007 and 2003 users from accessing and downloading email attachments.
Click to expand...
Click to collapse
Please note that if you happen to play Pokemon GO or any game which "GPS Spoofers" take advantage of, the March Security Patch, and this update will prevent GPS Spoofing.
Also, I'm not entirely sure yet as to whether the Samsung Patch for Qualcomm Galaxy S5 bootloaders included in the March Security Patch will affect the ability to have a Developer bootloader anymore:
SVE-2016-7930: Multiple Buffer Overflow in Qualcomm Bootloader
Severity: Critical
Affected versions: Galaxy S5 with Qualcomm AP chipset
Reported on: December 20, 2016
Disclosure status: Privately disclosed.
A buffer overflow vulnerability exist in Qualcomm bootloader.
The patch prevents buffer overflow by removing the problematic source code.
Click to expand...
Click to collapse
I, personally, am not willing to test this, but if anyone does, please post your results. I'll upload an aboot free (Dev Friendly) firmware as soon as possible in case anyone wants to test it.
I'm currently in the process of downloading/uploading the Odin firmwares right now. I'll update this post when they are uploaded.
EDIT:
Stock No-Wipe FW. Will remove Developer Status Bootloader: G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME.tar.md5.zip
Developer Bootloader Friendly:
G900VVRU2DQC2_G900VVZW2DQC2_G900VVRU2DQC2_HOME_No_Aboot.tar.md5.zip
If it breaks something that I warned about, please reply.
If it breaks something that I didn't warn or know about, please share with everyone else.
I'm guessing no replies and no ROMs based on QC2 means noone has tested it yet.
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.
I'm gonna try it out when I get a chance this week. Thanks!
Has anybody tried this?
robbyoconnor said:
Has anybody tried this?
Click to expand...
Click to collapse
Not yet I'm gonna download this once I get to a pc definitely
Sent from my SM-G900V using Tapatalk
Kastro1784 said:
Not yet I'm gonna download this once I get to a pc definitely
Click to expand...
Click to collapse
You can use Flaahfire by the way.
Download /installed last night.Havent had time to dig around. Precursor look has only shown latest Android security updates.
Dudash said:
I'm going to flash the aboot free version to one of my CID 15 S5's later tonight so I'll reply with results.
Click to expand...
Click to collapse
How we looking, captain?
I recently was pushed the QC2 update with the March 2017 security package. I have noticed a significant decline in performance and battery life. Anyone in the same boat?
It seems like they have pushed a security updated every other month or so for the last 6 months. It is very irritating. I want to go back to root but it is too much of a hassle to figure it out at this point. I feel like they are deliberately doing these updates to make the S5 run worse and feel more outdated so you are more inclined to go buy a new one. Really sick of the whole game that is the telecom industry.
I am going to try doing a factory reset (very annoying) and see if that helps. Hopefully I can hold out long enough for the Pixel 2.
@Dudash QD1 is up, can you upload it to AFH. thanks in advance.
Noooooo! I flashed the Dev friendly QC2 modem and it seems to have killed my dev bootloader and wiped my phone!
I'll keep messing around and see if it can't be remedied. I could just punch myself for being so ambitious, though.
Edit 1: It was taking forever on the Verizon logo, so I pulled the battery and rebooted to recovery. It wiped TWRP and put in stock. I booted to Download Mode, and it still reads MODE: Developer (which I hope to God means my Dev bootloader is retained).
Edit 2: TWRP sucessfully re-flashed. The "Custom" with unlocked lock icon has reappeared on the boot screen, along with the yellow text at the top (so clearly, I was wrong about losing Dev status. Whew! I just freaked out when I saw a plain boot screen and the dreaded Verizon logo :silly. My installation of Lineage OS is clearly gone, but, peeking through TWRP's file manager appears to indicate my media data (photos, downloads, etc.) may yet have survived. I'll flash Lineage and GApps and see what happens.
Edit 3: Lineage OS booted successfully (made easier with the help of an SD card-- hooray for those things, amirite?), with QC2 baseband intact! Hooray! And my downloads and pictures and everything survived too.
Lesson: Always make a nandroid backup when doing this sort of thing! It takes a while, and it's morbidly annoying, but had I done it, I probably wouldn't've had to start from scratch. But hey, got the new baseband, and still running Lineage, so I call this a win. Cheers, everyone! And thanks to OP for posting updates!
Follow-up: Since it doesn't seem like we can flash only the new basebands by themselves, I've found a tactic that does the trick for those of us on not-stock ROMs. Boot into TWRP and make a backup of Boot, System, and Data (notice there's a Modem option-- leave it unchecked). I imagine it's best to put the backup image on an SD card. Then Odin the dev-friendly firmware update (I used the no-wipe option). Let the phone restart, then Odin the most recent TWRP back on there. Boot into TWRP, do a Factory Reset Wipe, and restore the backup you made. Takes a little while, but it does leave you with your phone as it was, but with the new baseband. :victory:
{
"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"
}
mohammad.afaneh said:
@Dudash QD1 is up, can you upload it to AFH. thanks in advance.
Click to expand...
Click to collapse
In the process of uploading right now.
Dudash said:
In the process of uploading right now.
Click to expand...
Click to collapse
??? thanks
J-Lindo said:
How we looking, captain?
Click to expand...
Click to collapse
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.
Dudash said:
I totally missed this reply. I flashed QC2 onto one of my S5's and it remained a Dev Edition. Then earlier today I flashed QD1 onto my other S5 and it remained a Dev Edition as well. Faking GPS doesnt work on either anymore but they keep Dev status.
Click to expand...
Click to collapse
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?
J-Lindo said:
No problem! I'm sure you've already seen the results of my first (embarrassingly n00bish) independent baseband flash :laugh:
I appreciate the response, though. Fortunately, I'm not into GPS spoofing, so this isn't an issue for me. When you say you flashed QC2 and QD1, do you mean strictly the basebands without the bootloaders, or did you flash the entire updates and still retain Dev status?
Click to expand...
Click to collapse
I flashed the entire firmware minus the aboot.
I've had an MT6577 phone sitting around for a few years now that's been stuck in a boot loop. My phone karked it today and this is the only device lying around, hoping it can be revived some how to save a few dollars.
It all happened one time when I tried to use an app to install a new font just to see what it looks like.
Seems to be the most obscure thing ever made as it has many names and models all with 0 firmware available. Typically SoSoon X8 Elite 3 shows up as the most common make but I recall the original box having Senq X8 Elite on it.
The bad?:
USB Debugging is almost certainly off because ADB can't find a device no matter if I just plug it in off, in bootloop (shows 2 drives on my PC that are not ready to be used in this stage), fastboot mode, recovery (install update from ADB)
Questionable root, one of those generic one click apps.
No stock or custom roms available any where that I have found from searches here and there over the last few years
I tried to follow a tutorial to port an MT6577 rom but I would need the kernel off the phone, which can't be done to my limited knowledge.
No custom recoveries available, running Android System Recovery 3e. Can't use TWRP MTK 1 click install on my PC because the device needs to be fully booted to work.
The good?:
Fastboot seems to work as it does show the device in the command prompt "fastboot devices"
I think the bootloader was unlocked at some point, no idea on the relevance of that.
Any information on if/how to sort it out is greatly appreciated.
Last ditch effort to try revive it because it was decently usable for what it is, hoping that someone on here has one lying around somewhere.
Will add more information as I remember and reply to any responses asap
Thanks for your time
Hello have you tried a hard reset so far ?
-Hope- said:
Hello have you tried a hard reset so far ?
Click to expand...
Click to collapse
I have, through the recovery "Wipe cache partition" and "Wipe data/factory reset" have been done a few times as I've tried different ways to try and fix it
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
-Hope- said:
can you get the model it would be easier to look up for the rom
try fastboot oem device-info that will input some useful informations
Click to expand...
Click to collapse
Good news: Tired it
Bad news: Nothing happened
{
"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"
}
Also tried "getvar all" which according to a post on a xiaomi forum, is an MTK specific command, returned nothing anyway.
Just showed the "..." until I pulled the USB cable out.
Thanks for the suggestion, guess that's a pretty significant strike against any kind of fix for it.
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
-Hope- said:
the battery is removable ? maybe you can find the model in the box if you have it , dont lose hope
Click to expand...
Click to collapse
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
weavernater said:
The battery is soldered in but the back panel pops off easily, no information at all besides "X8" written on the battery.
I've found what I'm sure is the exact same model phone on GearBest and I've asked the seller if there's a chance of them providing the stock firmware.
This is the only form of model number I've found, but it's generic and shows up more Sony Xperia posts than anything else through google.
Click to expand...
Click to collapse
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the whole system.img unless you have TWRP or can sideload apps in the recovery that you have.
Sent from my SM-S903VL using Tapatalk
-Hope- said:
https://url.gem-flash.com/gtKxY
Here this flash is not for your device exactly by might work, check if the spcs match too
Click to expand...
Click to collapse
Thank you for finding this, much closer than anything I've ever found. From what I can see on it, it's really close spec wise. I'll download it and have a look through the files before trying it.
Droidriven said:
You don't need a whole firmware, all you need is a good copy of system.img from a device like yours or from a similar device that uses the same kernel, trying to find a whole firmware that will flash without issues will be kinda difficult because there are things in a whole firmware that might not work on your device, a system.img on the other hand doesnt have all the extras in a firmware that could cause issues. Use fastboot to flash the .img with this command.
fasboot flash system system.img
From what you described causing the issue, technically, all you "need" is a copy of the stock font to replace the font that you tried and screwed it up with, but getting just the font back on without doing anything else isn't as easy as flashing the while system.img.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I did try that. I have all kinds of zips that could supposedly be flashed with the stock roboto font as well as the file itself ofcourse but I could never get fast boot to so anything with it. Based solely off the assumption that all android devices use it as the default, and assuming that the app was just renaming custom fonts to Roboto or something along those lines.
As said in the title... my insurance company has given me several different devices after they keep dying during charge.. I have had several different G1841's and they all seem to die during charge a few days after from applying the DRM fixes and do not turn back on again at all... Has anyone else experienced this issue yet??
I applied all the OTA updates through Sony's official software update then I unlocked the bootloader so I do not believe I am doing anything wrong.. It's just that the devices keep dying every time I obtain root access!! Not sure what to do as this is the 4th time it has happened (happened just today after receiving another device only a few days ago, my insurance company will start to think something is up now...)
Did you uninstall the Update Center? Installing OTA updates on an unlocked Bootloader is what bricks devices.
Also, did you try connecting the phone to a PC in flashmode?
saved-j said:
Did you uninstall the Update Center? Installing OTA updates on an unlocked Bootloader is what bricks devices.
Also, did you try connecting the phone to a PC in flashmode?
Click to expand...
Click to collapse
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
avi312singh said:
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
Click to expand...
Click to collapse
seems like the modded kernel is not for your device and there is conflict!
how did you obtain root? which kernel you used? who provided that kernel ?
avi312singh said:
Yeah didn't do any updating after DRM fix, flashmode fastboot nothing works... Happened on many different devices now - maybe problem with UK version?
Click to expand...
Click to collapse
I don't believe that there's loads of duff Sony devices out there that die as soon as you unlock them. What's more likely is that as mentioned above, you're flashing the wrong firmware/kernel/image for your model, bricking it in the process.
Not sure how you can keep blaming the phone after four attempts. Perhaps you need to review your method before the insurance company refuse to replace the next one?
YasuHamed said:
seems like the modded kernel is not for your device and there is conflict!
how did you obtain root? which kernel you used? who provided that kernel ?
Click to expand...
Click to collapse
I've had about 5 different XZP's... 4 of them were storm's and one of them were janjan, all of them went in the same way - complete power off whilst charging and dead after completely.
I am going to use the new stock kernel for the DRM fix by shoey - hopefully that is alright as I am getting a different XZP back this week
Didgesteve said:
I don't believe that there's loads of duff Sony devices out there that die as soon as you unlock them. What's more likely is that as mentioned above, you're flashing the wrong firmware/kernel/image for your model, bricking it in the process.
Not sure how you can keep blaming the phone after four attempts. Perhaps you need to review your method before the insurance company refuse to replace the next one?
Click to expand...
Click to collapse
Lol not really, I use xperifirm to download and flash the fw (customised UK- maple), all the kernels etc are taken from this forum - not sure how I can go wrong with flashing the wrong zips etc (I am a computer scientist myself )
However, I do believe there is something wrong with the modified kernels for UK devices, maybe wrong charge current rate etc. I don't know but these problems did not happen when I was on stock firmware
{
"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"
}
avi312singh said:
I've had about 5 different XZP's... 4 of them were storm's and one of them were janjan, all of them went in the same way - complete power off whilst charging and dead after completely.
I am going to use the new stock kernel for the DRM fix by shoey - hopefully that is alright as I am getting a different XZP back this week
Lol not really, I use xperifirm to download and flash the fw (customised UK- maple), all the kernels etc are taken from this forum - not sure how I can go wrong with flashing the wrong zips etc (I am a computer scientist myself )
However, I do believe there is something wrong with the modified kernels for UK devices, maybe wrong charge current rate etc. I don't know but these problems did not happen when I was on stock firmware
Click to expand...
Click to collapse
I can not imagine a connection between your problem and XperiFIX. At least if you have the software (as of version 2.0) it can not be the kernel. Because current versions of XperiFIX do not use prepared kernels (ramdisks) anymore. The stock ramdisk is modified during the process and this happens directly in the device. The kernel itself is not changed, but the required lines / files are added to the ramdisk. So... With XperiFIX you always have the stock kernel.
What I could imagine is that you used the old zips. However, I strongly advise against using them. Sony is constantly working on the firmware and it is quite possible that there are also changes to the relevant system files between the firmware versions. And since the modifications to the DRM issue are very sensitive, the device could be damaged if you put outdated hacks.
But to generally address your problem:
So you had several devices and all rooted. Did you try with a device and what happens if you do not (root / fix)? Maybe you use the same charger all the time and the cable has a defect or something in the direction. Maybe you also use a certain app that has a bug. Sounds crazy, but mostly it's little things that make life difficult.
sToRm// said:
I can not imagine a connection between your problem and XperiFIX. At least if you have the software (as of version 2.0) it can not be the kernel. Because current versions of XperiFIX do not use prepared kernels (ramdisks) anymore. The stock ramdisk is modified during the process and this happens directly in the device. The kernel itself is not changed, but the required lines / files are added to the ramdisk. So... With XperiFIX you always have the stock kernel.
What I could imagine is that you used the old zips. However, I strongly advise against using them. Sony is constantly working on the firmware and it is quite possible that there are also changes to the relevant system files between the firmware versions. And since the modifications to the DRM issue are very sensitive, the device could be damaged if you put outdated hacks.
But to generally address your problem:
So you had several devices and all rooted. Did you try with a device and what happens if you do not (root / fix)? Maybe you use the same charger all the time and the cable has a defect or something in the direction. Maybe you also use a certain app that has a bug. Sounds crazy, but mostly it's little things that make life difficult.
Click to expand...
Click to collapse
I believe I used the zips from your 2.0 software.. I sent you a donation through PayPal when you released this, do I get the software or some sort of discount? Student life has hit me hard this year
Well I am getting a completely different device tommorow and will hopefully be able to use your 3.0 fix on it... With regards to the charger, I will use a new wall charger - hopefully can order a new official one from amazon when it arrives and not charge it till then
Before unlocking the bootloader and applying the DRM fixes I experienced no problems such as dead devices.. Let's hope the sixth device is ok!
Update: the culprit of this was the battery charge limit application which requires root privileges and is found on the Google Play store.
I'm not going to link in here but there seems to be a conflict with either the device., rom I don't know - but yeah just making people aware of this
Hi everyone,
Recently I purchased and Samsung A11. I wanted to root it and unlocked the bootloader first. Than I used Odin to install TRWP recovery. Odin showed "PASS" and I was supposed to press certain buttons which didn't work. Phone kept coming back to "Download Mode" although I pressed those buttons. So I was stuck. The only option was to cancel the download mode, so I pressed volume down + power button for more than 7 seconds. That was the end Now the phone turns on until I see the Samsung logo, there's a small vibration but it can't go forward. It resets back and now stuck in a loop. None of the buttons work including Volume Down+Power combination. Don't know what I am supposed to do now. Can anybody help?
Thanks...
1. Add Samsung A11 to this thread's title thus mainly owners of such a phone get addressed
2. My recommendation: Re-flash STOCK ROM to get rid off of all mods you applied.
jwoegerbauer said:
Re-flash STOCK ROM to get rid off of all mods you applied.
Click to expand...
Click to collapse
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
gokund said:
Thanks but how can I do that? Phone doesn't turn on, so PC cannot recognise...
Click to expand...
Click to collapse
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
jwoegerbauer said:
As I can see you are proud owner of a softbricked phone.
Take it to authorized service center and let them fix it.
Click to expand...
Click to collapse
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
gokund said:
Yeah, veeeery proud
I plan to let it die on battery and will try to see if I can turn on "Download Mode" after recharging. Do you think it may work?
Click to expand...
Click to collapse
it wouldn't ... usually the cause of bootloop is certain corrupted partition and as long as that partition is corrupted it would keep bootlooping.
if you doesn't know what your doing your best bet is Take it to authorized service center and let them fix it. like what @jwoubeir said
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
sammiev said:
I don't have the A11 model but have used this on other A models that were in the same loop.
Press the volume up and down at the sametime and plug in the usb cable.
This has to be done within a second or two after it vibrates and before it reboots and will likely take a few tries. Good Luck
Click to expand...
Click to collapse
great tip work on ADB too anyway OP is provably using sp flashtool since his phone is samsung so this method would be rather tricky
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told and I tried flashing another TRWP file thinking that might have caused the problem but nothing has changed. Same loop again ! So I flashed the original ROM back using Odin and it's back live again Thanks for the help guys. But to be honest, I am still curious. What might be the problem in not getting TRWP flashing going right?
gokund said:
Yayy, I managed to get into the "Download mode" doing exactly how @sammiev told
Click to expand...
Click to collapse
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
sammiev said:
Used that method of a few peoples Samsung phones. Worked for me every time. It's just to get the timing right.
Sure you have the correct TWRP?
Click to expand...
Click to collapse
I tried again from scratch with a new TRWP file and the result is the same. Odin shows "PASS" but the "Download Mode" screen gives the error as in the photo:
{
"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"
}
My phone model is A115F and I downloaded the TRWP file from this link:
Downloads for : Samsung Galaxy A11 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
androidfilehost.com
The version I used is "twrp-3.5.0_10-3_afaneh92-a11q.tar"
I also tried rooting with Magisk without the need of TRWP installation. That was also unsuccesfull. Odin was PASS but I got bootloader screen saying Secure Check Fail : vbmeta
Here's the screenshot of Magisk fail in "Download Mode"
Can't figure out what's wrong ...
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Deleted
sammiev said:
Have you flashed the latest stock rom to this device?
Was there other TWRP files for this model?
Is other people having trouble with this model?
I never worked on A11 Samsung yet
I would hate to give you bad info and have you brick your phone.
Click to expand...
Click to collapse
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
gokund said:
Following your advice, I managed to get into the Download Mode and I flashed the original rom. So phone is up and running now but not rooted. So I've been trying to root again first with Magisk to bypass the need of TRWP installation and with others which need TRWP installation first. There seems to be something blocking the flashing of anything other than the original rom !! On the link I shared above, there are other (older version) TRWP files. Shall I try them?
Click to expand...
Click to collapse
Usually the latest TWRP with the latest firmware.
Check my profile, your KG stated is ****ed. There is nothing you can do about it, there is abosulutly no way to fix this without unsoldering the eMMC and resetting it entirely. Some people on 4PDA had the same problem and found no fix. I was hopping to develop a custom rom but I cant as my kg state is prenormal. This mexican dude on youtube fixes devices with KG and FRP issues, but yeah this aint something that you can do at home. At least I learned not to buy any samsung devices in the future https://www.youtube.com/c/TeamOcmineMMCBootRepair
edit: nvm your oem is unlocked, you can just flash the vbmeta reset script via odia and everything should flash fine.