Database Info

Got a OTA for my ADP1!

Just received update notification (running jf's adp)
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.

Its adp's update. No its not cupcake lol

Uh oh, if it's a new bootloader, could this mean trouble for us in the future?
doesn't sound good to me

Just installed the bootloader without the "complete system update" and... surprise. The original T-Mobile G1 bootloader (RGB). After seeing that i downloaded hard spl, then installed it and that's all. I'm not going to complete the full update, because there is a chance after the update to be stuck to normal bootloader, and I don't want to prove it

Good morning!
I was just checking out the market when I got a popup message on my ADP1 (v1.1) telling me a baseband update was available.
I cant remember which version I had before, but it my Baseband version is now:
62.33.20.08H_1.22.12.29
Anyone have the same thing?

Untouchab1e, what was the use of reporting this post? it's only to report Spams, advertisments and other abusing stuff to the Mods and Admins, please use it wisely the next time or you'll get a ban!

yes you called
we came running....please use the report button as it should
thank you

My apologies? I either clicked the wrong button or I dont know, as I cant remember clicking any report button (havent noticed any report button at all really)..
Anyhow, sorry for the trouble
EDIT: A second update is being installed now, described as a "Full system update".. will be interesting to see what it is!
EDIT2: Its apparantly the ADP1 equivalent of the RC33. Latitude, Voice Search.. its all there!
Thank you Google

{
"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"
}
This is the Report Post Button its right besides the post number

ADP OTA update = no more Wifi Tethering??
I go ahead and did the update.
I checked the bootloader and it's still the modded one.
although, there's other problem. I can't do wifi tethering from the terminal emulator. I don't know if the OTA update take out Root access or not. is there a way to check root status without using Terminal emulator? (I know on the terminal emulator you just type su for superuser to get root, and # on the prompt means you have root access)
So, When I typed "tether start" after running the .tar file from the terminal emulator, I got this message
Code:
insmod: init_module '/system/lib/modules/wlan.ko' failed (file exists)
then when I typed tether stop, I get this message:
Code:
rmmod: delete_module 'wlan' failed (errno 11)
any info on this probleM? I need the tether function because it is the only internet access for my laptop at home because my cheap ass aunt disconnected the DSL for the house.
please be nice to me as I am a linux noob and has fairly little understanding using the terminal command line.
Edit: Nevermind. I found the problem. I had the Wifi radio on before I run the terminal code for tethering. Sorry for freaking out guys.

mony87 said:
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.
Click to expand...
Click to collapse
I just got this exact same update notification (im in the netherlands), im also running JF's ADP1 1.41 but im doing so on a devphone......... I really dont want to install anything on my phone unless i know specifically what it does or changes.....

mony87 said:
I'm running T-mobile G1 with JF's ADP1 1.41 + dev bootloader and before maybe 15 minutes received update notification. The full text is "Holiday phone update 1 of 2: This is bootloader update (0.95.0000). After this update installs, your device will start downloading a full system update." Anyone know what that is? I'm rejecting the update for now but i'm curious.
Click to expand...
Click to collapse
I got it too, and I'm not even running a TMobile data plan. It came in over wifi on JF ADP1.1. I did not install it. It's very annoying to say no to the update every time my phone wakes up from screen lock, however.
EDIT: JF's got a new release to fix this problem: http://forum.xda-developers.com/showthread.php?t=475381 (or check out the top sticky post).

Did it...
... i also got this message and i did the update.
Nothing changend after update. Everthing is the same.

Does this mean, we are all getting ota-updates in the future, even if we are on JF (RC33 or RC8)?
I thought JF deactivated this in his versions...???

kanisdragon said:
I got it too, and I'm not even running a TMobile data plan. It came in over wifi on JF ADP1.1. I did not install it. It's very annoying to say no to the update every time my phone wakes up from screen lock, however.
Click to expand...
Click to collapse
Here's the news....
First part of the update was no problem, all still worked..
Second part installed, phone rebooted, got the nice little blinking android and nothing happened for 15 min :S SO i got bored and tried to turn if off but this didnt work, pulled the battery and the same thing happened; phone hangs on bootup..... So its fooked haha, ill update to JF 1.42ADP1.1h, see what happens. I do need to find a way to disable this update stuff 'cuz its annoying!
So BEWARE when using these 'ota' updates on modded firmwares!!
[edit] And no, i do not have anything Tmobile on my phone because Tmobile sux! [/edit]

...same..
after the second update (part 2) my phone got stucked too.
What can I do now?

Hanneskitz said:
after the second update (part 2) my phone got stucked too.
What can I do now?
Click to expand...
Click to collapse
You can pray my friend, pray!
No, seriously i do have a solution but its not a pretty one...... I wiped my phone completely and had to reinstall the whole lot. Seems to work fine now but i just hope i dont get the freakin annoying update window again because that would seriously piss me off!
I dont know how easy this will be on non-dev phones tho....

maarten82 said:
You can pray my friend, pray!
No, seriously i do have a solution but its not a pretty one...... I wiped my phone completely and had to reinstall the whole lot. Seems to work fine now but i just hope i dont get the freakin annoying update window again because that would seriously piss me off!
I dont know how easy this will be on non-dev phones tho....
Click to expand...
Click to collapse
It sounds to me like this update was sent by Google only to dev phones. Couldn't you also do a nandroid restore if you made a backup?

kanisdragon said:
It sounds to me like this update was sent by Google only to dev phones. Couldn't you also do a nandroid restore if you made a backup?
Click to expand...
Click to collapse
Probably..... but setting back the complete backup(s) would not fix anything because you would still get the annoying update window telling you to install the stuff that will in turn crash you phone back to where you started
But then from your old backup you could try to install JF1.42 without wiping, that might work!

maarten82 said:
But then from your old backup you could try to install JF1.42 without wiping, that might work!
Click to expand...
Click to collapse
The JF1.42 update worked for me without wiping. I haven't been offered the Google update in the last hour.

EVO OTA is here

take a look guys
http://androidforums.com/htc-evo-4g/90893-ota-update-1-32-651-6-a.html

Interesting...
I am running Flips "stock" rom, and no prompt for this...
Did a "firmware" update... none found.
Did a HTC Software Update... found it.

post the zip so flipz and toast can have a look at it

extrafuzzyllama said:
post the zip so flipz and toast can have a look at it
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I used the search function in Root Explorer, but found neither "OTA_Supersonic" or "update.zip"
It must be in one of those folders that need root to view (right now I'm stock no root) like /data or something

DO NOT ACCEPT THE UPDATE FOR NOW ...MORE LATER FROM Matt, Ozzeh,Joshua and zule...

https://twitter.com/unrevoked
There's an OTA update we just got on the #EVO that breaks the root. Don't install it if you want to root.
Click to expand...
Click to collapse

Well that sucks...

upload it so the devs can see whazzz up!

Here's a copy of the sprint hero ota that I got at the same time and it supposedly (not gonna test it) breaks root. I'm pretty sure it's really a super cool update to make are phones ten times better

Just got back home. Super glad I saw this thread. I had the guy at radioshack cancel the update when it came up (he had to turn phone on to complete activation, he said).
He mentioned that for the other 6 phones he did that morning, he let the update install

GumboChief said:
Just got back home. Super glad I saw this thread. I had the guy at radioshack cancel the update when it came up (he had to turn phone on to complete activation, he said).
He mentioned that for the other 6 phones he did that morning, he let the update install
Click to expand...
Click to collapse
99% of the population is better off with the update due to the storage fix. Rooters are a tiny group of people, relatively speaking.

The guy at Sprint almost ran the update since they do have to turn the phone on to activate it, however since I didn't need anything else he just told me to make sure to update and told me how and even offered. I told him I'd get right on it as I go outside. But yea the OTA is probably best for most consumers buying this device (especially after the conversations that took place this morning) as just about everyone else there this morning just wanted to get the phone switching from various carriers from T-Mobile and ATT and just wanted it to work. There was like one other guy there who was pretty knowledgeable buying the phone outright like I was, but he claimed again he just wants the phone to work no jumping through hoops and knows about rooting but has no intentions to. The guy in charge was emphasizing to his staff to make sure to push the update. I just happened to luck out.

anyone got pre and post ota version numbers so I can confirm my unit hadn't been updated before handing it over? Thanks

FuManChuu said:
anyone got pre and post ota version numbers so I can confirm my unit hadn't been updated before handing it over? Thanks
Click to expand...
Click to collapse
1.32.651.1 ->Shipping
1.32.651.6 ->OTA

I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.

princem131 said:
I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.
Click to expand...
Click to collapse
That sounds promising. Look at the rom version in the about section of settings. Does it end with a 1 or a 6?

princem131 said:
I was running flipz stock got the notification last night at like 3am and updated. Not sure if it closed root access because I could still go into the recovery screen and navigate the menus to flash, wipe etc.
Click to expand...
Click to collapse
are you able to type su thru adb shell or connectbot on the localhost after applying the OTA while stil using flipz stock with root ROM?

um i tested... OTA applied... Rooted, recovery, NAND backup... it all worked...USB debugging Enabled on plugin. Installed 64bit ADB drivers and boom!
no problem to fear the root loss
um crap... nvm apparently i didnt update...
i swear I downloaded, installed, restarted the phone to allow install... but it shows software number 1.32.651.1.
maybe because I did a factory reset? then that would mean that this update is rather a patch (ie like a cab fix)??
or did the update not apply?

Tilde88 said:
um i tested... OTA applied... Rooted, recovery, NAND backup... it all worked...USB debugging Enabled on plugin. Installed 64bit ADB drivers and boom!
no problem to fear the root loss
Click to expand...
Click to collapse
But does that retain the update fix for the sdcard?

damn i updated what am i supposed to do now ?

Dead Moto G XT1032 after Lollipop downgrade

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

Dead Devices After using DRM fixes!!

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

Please help, Samsung A11 - TRWP problem

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.