Hello I am trying to do OTA update of a Sonim xp7 from 4.4.4 but apparently some root app has tampered with /system/bin/debuggered.
Could anyone on 4.4.4 be so kind to share their original file?
Here is a ported twrp recovery I made, it will work on un-rooted devices.
You just need adb/fastboot on your computer and developer options on your phone.
http s://www .mediafire .com/file/rqyxpppc7gc1n2u/twrp.img/file
$ adb reboot bootloader
$ sudo fastboot boot twrp.img
This gets into twrp from a standard system without modifying the original recovery at all.
From there you can mount /system and copy /system/bin/debuggered to your /storage
I would greatly appreciate any help!
Thank you.
EDIT:
I managed to download the OTA .zip on my comupter, so maybe there is a way to tamper with the file verification?
Edit2:
So I have removed the file check from /META-INF/com/google/android/updater-script for both debuggered and build.prop.
Update runs smootly with twrp, as sideloading from stock recovery gives a verification error.
Now the problem is that when the phone is booted up the build info hasn't changed a bit.
I imagine it's the build.prop is at fault..
So anyone can tell how can I view the build.prop.p from the update?
bumps
Xp7
Were you able to get the firmware?
Anyone have firmware?
I have flashed verixon cdma xp7 with lte 4.4 and lost modem. Maybe someone have link for QFIL loaded verizon fw or 5.x lte version?
I'm looking for some insight on flashing the Xp7. I'm using the QFIL flasher and I have the latest drivers. It looks like the flash starts but tawords the end I get a Firhouse loader failed. I'm trying to flash to get around the google frp. Any insight would be appreciated!
Related
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
mochamoo said:
I have an MDK S4. I have been running beanstown's rom for months with TWRP 2.5.0.2 with no issues. Today I decided to flash clockworkmod touch recovery in terminal emulator using the following command:
su
dd if=/sdcard/ recovery-clockwork-touch-6.0.4.4-jfltevzw.img of=/dev/block/mmcblk0p21
So now my phone won't boot at all. All I get is a screen that says:
Secure fail: kernel
System software not authorized by Verizon Wireless has been found on your phone...
UGH!!!! So now what? Do I need to do the following or is there another way around it?
http://forum.xda-developers.com/showthread.php?t=2301259
Please advise asap. Thanks.
Click to expand...
Click to collapse
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Thank you. My s4 is rooted. I *think* that I have solved my issue. I was able to get it to go into Odin mode power+vol down. I didn't connect to a computer (am at work and all of my android tools are at home). I just cancelled out of Odin mode and it booted up just fine. Now I tried to go into recovery again and got the same error as above and was able to get out of it the same way. I was able to go into ROM manager and flash regular non-touch CWM recovery and was able to boot to it without issue.
I suspect that my flash of the touch via terminal emulator didn't work right. Can anyone who has done it this way let me know how long the flash should take? I was at the su prompt and entered the dd line above (copy and pasted to avoid typos). It appeared to do something...there were some numbers maybe 5 or 6 per line and then it went back to the prompt so thought it was done. This didn't take it more than about 15 seconds to do. What should I see here?
I know that I can just flash it via ROM manager but wanted to be able to do it myself without rom manager and also be able to flash the latest twrp img if I want to (goo.im seems broken at the moment). Maybe I will try to do it via Odin later.
TIA.
you rock
I just got this same error and your steps worked perfect
Same problem except on i545vrufnk1
k1mu said:
I think you need to go here: http://forum.xda-developers.com/showthread.php?t=2290798
Click to expand...
Click to collapse
Hello, I went to flash a recovery package with flashify and got the black screen with kernel fail. I was on the latest nk1 kernel.
please help
Hi! I'm really sorry to revive such an ancient thread but I've a similar problem.
I tried to use the dd command to update TWRP and wound up at this spot, but I was running a custom 5.1.1 system (jflte dev something or other from oct 2014 - recovery needed to be updated in order to install 7.1.1). So I tried to ODIN back to the old bootloader because I read it may have just become locked again, and now the system seems broken or missing, I'm not sure which. Phone no longer boots into the system and I get this error at recovery, so I'm hoping that if I flash an older factory image onto the phone, it'll restore it.
My question is, if I flash a stock image onto the phone, will it overwrite the bootloader and make my custom recovery dreams impossible? I went as far as to transplant the insides of this phone into a replacement when it first broke to maintain my MDK bootloader, so I'm really hoping I didn't **** myself here.
----
Edit:
So I've fixed my phone! The whole ordeal wasn't too too bad, but it was somewhat time consuming and difficult to divine on my own.
Now, I realize now I may have actually flashed the wrong .img file, which may have caused this whole issue. I'm actually not certain, because through the method that I fixed this problem with, I was able to flash what I would later find out was an incorrect .img for the recovery (jfltexx instead of jfltevzw ) but it did work properly, and I only found out when I got an error on trying to install the LineageOS zip.
I tried a bunch of things, but the one that worked was converting a twrp .img file to a .lok (loki) file. At the time of this writing, it happens that there's a bug in the latest twrp version that also prevents you from installing the system, but downgrading back to an older version will work, and I assume after 3.1.2 the bug will be fixed.
In order to do this, I wiped the system back to an MDK 4.2.2 system image I found here: https://forum.xda-developers.com/showthread.php?t=2301259
(dead link? Here's an archive: https://archive.is/LDnaY - I hit a bunch of dead links when I was figuring this process out and it was frustrating)
which preserved the mdk bootloader (because flashing anything newer than this will lock the bootloader, I've been told. I didn't dare try.)
I rooted that image by downgrading to the prerelease kernel and using motochopper to root, then upgraded back to the mdk kernel.
Then I grabbed the loki_tool from this thread:
https://forum.xda-developers.com/lg-g2/general/guide-how-to-flash-cwm-6-0-4-4-lokitool-t2813514
(Dead link? Here's an archive: https://archive.is/F7k29 )
and used a twrp .img file to create the recovery.lok file
Flashing through this method restored my custom recovery, and also made the samsung unlocked padlock bootscreen go away (I miss it already!). Having Android 7.1.2 on this phone is quite a treat though!
Hope that anyone else who winds up here in the future finds this useful! And I hope those links
Before moving forward, you must understand that if anything happens with your device, I'm not to be blamed on, you choose to flash this
Hey guys, so a friend of mine bricked his OnePlus2 to a state that his recovery wasn't working (wiped) and also his ROM was bootlooping. So I thought of this little trick to convert the latest full OTA zip file into fastboot flashable stock ROM files by converting the system.new.dat into system sparse image. Though my friend recovered his phone by flashing recovery and sideloading zip. I still think it would be a good idea to share here
Download: OOS 3.5.8
Requirements: must have fastboot
Must have fastboot drivers
Must have knowledge on how to use these commands
Note: this is not rooted or tampered with, with this system firmware you should be able to get OTAs
Happy unbricking!
Nice, might become useful
Thanks
MZO said:
Before moving forward, you must understand that if anything happens with your device, I'm not to be blamed on, you choose to flash this
Hey guys, so a friend of mine bricked his OnePlus2 to a state that his recovery wasn't working (wiped) and also his ROM was bootlooping. So I thought of this little trick to convert the latest full OTA zip file into fastboot flashable stock ROM files by converting the system.new.dat into system sparse image. Though my friend recovered his phone by flashing recovery and sideloading zip. I still think it would be a good idea to share here
Download: OOS 3.5.8
Requirements: must have fastboot
Must have fastboot drivers
Must have knowledge on how to use these commands
Note: this is not rooted or tampered with, with this system firmware you should be able to get OTAs
Happy unbricking!
Click to expand...
Click to collapse
Got a
no file in this folder
Click to expand...
Click to collapse
when clicking the link.
casual_kikoo said:
Got a
when clicking the link.
Click to expand...
Click to collapse
Try again, the file seemed to be removed because something happened to the backend servers of AFH
Hey man. Can I still do this if my device is locked. Whenever I try to flash twrp recovery it will display unable to patch image device is locked.
Hope you can help me Bro. Thank you! ?
conqueror_25 said:
Hey man. Can I still do this if my device is locked. Whenever I try to flash twrp recovery it will display unable to patch image device is locked.
Hope you can help me Bro. Thank you! [emoji4]
Click to expand...
Click to collapse
No you can't flash images while you're locked, use fastboot oem unlock to unlock your bootloader
Thank you for your prompt response mate.
Please allow me to post my problem here with my phone.
* Hi everyone. Hope somebody can help me restore my phone again. I have successfully unlocked the bootloader of my phone but I cannot boot to Rom. Every time I power on the phone it will boot to CM stock recovery. Tried to flash TWRP recovery but unable to write image. Device is locked. Did some research and found out the reason behind this is I did not unable update to CM Recovery in Developer Options.
What is the best way to resolve this issue? I still have access to Fastboot and can do ADB commands but device is locked.
Will sideloading a stock CM OP2 Rom will fix the issue? I'm also concerned with the draining of the battery, if I cannot turn on because no more charge already.
I'm using Mac computer but I can borrow a windows laptop to fix this.
Any help will be highly appreciated..
Thank you very much in advance guys!
God bless!
conqueror_25 said:
Thank you for your prompt response mate.
Please allow me to post my problem here with my phone.
* Hi everyone. Hope somebody can help me restore my phone again. I have successfully unlocked the bootloader of my phone but I cannot boot to Rom. Every time I power on the phone it will boot to CM stock recovery. Tried to flash TWRP recovery but unable to write image. Device is locked. Did some research and found out the reason behind this is I did not unable update to CM Recovery in Developer Options.
What is the best way to resolve this issue? I still have access to Fastboot and can do ADB commands but device is locked.
Will sideloading a stock CM OP2 Rom will fix the issue? I'm also concerned with the draining of the battery, if I cannot turn on because no more charge already.
I'm using Mac computer but I can borrow a windows laptop to fix this.
Any help will be highly appreciated..
Thank you very much in advance guys!
God bless!
Click to expand...
Click to collapse
This is weird. You should start a new thread about ut
I already did. Thanks man. Appreciate your reply. ?
Where is the fastboot command it is not visible
niteshnandi said:
Where is the fastboot command it is not visible
Click to expand...
Click to collapse
You have to install fastboot and adb from
https://forum.xda-developers.com/showthread.php?t=2588979
[TOOL] [WINDOWS] ADB, Fastboot and Drivers -… | Android ...
Hi @MZO,
After downloading https://androidfilehost.com/?w=files&flid=169179, the file seemed corrupted, since it seems that the file could not be fully extracted.
Please kindly verify it.
Thanks.
Hey developers. I am currently using Moto X Force XT1580 bought in India with Android 7.0 July 1 2017 Security Patch. I extracted the build.prop file using adb but the problem is I can't push it back. I edited the build.prop to enable Camera2 Api. The issue is I don't want to unlock boot loader and root because it always shows ugly message showing unlocked bootloader in Motorola. Next to use Android Pay we need locked bootloader and to lock bootloader again I need to flash stock firmware again. This makes the editing buil.prop and pushing thing moot. . So I thought only method is via fastboot or using Zip. So help me experts because I have no idea on how to push that new build.prop. If there is way to do this without unlocking bootloader then amazing. Also if anyone can provide me Stock ROM of Android 7.0 for XT1580 Indian model.
Thanks in advance
You are stuck then. As you need root to push a file to the system partition where that file goes.
zelendel said:
You are stuck then. As you need root to push a file to the system partition where that file goes.
Click to expand...
Click to collapse
But fastboot flashing doesn't need root, or does it? Isn't there any way of flashing via fastboot or creating any zip like those OTA update zip files
hey! i accidentally deleted a backup for my device and now i have no system to boot off of
are there any roms available for mya-l11? all the ones i see on this sub are for the 2015 models. thanks
lbxda said:
hey! i accidentally deleted a backup for my device and now i have no system to boot off of
are there any roms available for mya-l11? all the ones i see on this sub are for the 2015 models. thanks
Click to expand...
Click to collapse
I could not find any custom Roms for your device.
I could find an stock Rom for the Mya-l41 trough.
Here is an link: https://mega.nz/#!wKpT1ZaS!CV-2E4sNnUwIurskAdqCDpDawWlZD2UeABtSELk_ffc
That should be an update.app or an flashable zip.
You may get Huawei Update Extractor and extract the system.img and boot.img of the update.app
After that flash system.img and boot.img from fastboot.
Warning. This may soft brick your device.
Good luck.
If i helped press the Thanks button
Thespartann said:
I could not find any custom Roms for your device.
I could find an stock Rom for the Mya-l41 trough.
That should be an update.app or an flashable zip.
You may get Huawei Update Extractor and extract the system.img and boot.img of the update.app
After that flash system.img and boot.img from fastboot.
Warning. This may soft brick your device.
Good luck.
If i helped press the Thanks button
Click to expand...
Click to collapse
i was able to flash the boot and recovery image, but i couldnt flash the system image
lbxda said:
i was able to flash the boot and recovery image, but i couldnt flash the system image
Click to expand...
Click to collapse
Does it show an error or anything?
Fastboot flash system system.img
ok, so i found what i thought was a stock rom for my device on some spanish forum and used sp flash tool to install it
problem is, sp flash tool formatted my phone, but encountered an error trying to install the firmware and now my phone wont boot and windows says its not recognised
is there any fix to this? or is my phone bricked?
hey again! i know this post has been a wild ride of me doing stupid stuff and bricking my phone, but i got the firmware back!
only catch is that i'm receiving some nvram error (which i got on my previous phone too. i swear this is the last time im going mediatek), so if anybody has a method that can fix this it'd be highly appreciated
thanks
Hi, Ibxda.
Can you please share with us where you found the stock rom, what went wrong with flashing, and how you managed to get the firmware back?
I have a running system, but I rooted it and cannot apply official upgrades. I'd like to go back, upgrade and root again. I would appreciate the info on your progress.
ifrag_svk said:
Hi, Ibxda.
Can you please share with us where you found the stock rom, what went wrong with flashing, and how you managed to get the firmware back?
I have a running system, but I rooted it and cannot apply official upgrades. I'd like to go back, upgrade and root again. I would appreciate the info on your progress.
Click to expand...
Click to collapse
You should root with Magisk, it's systemless and it should not affect updates. If you want to update you should flash stock recovery. After you updated you are free to flash Twrp again if you want. If you are rooted with SuperSU you should uninstall SuperSU and install Magisk
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Why not compile a matching TWRP by yourself?
Look inside here.
@ jwoegerbauer i can give a try but have no experiences when it comes to makin a custom recovery.
ᐯerified Developer said:
I have this device rooted with magisk BUT cant find way to properly port a qualcomm twrp from similar devices i just need help to get started with custom recovery if i can get one to boot i might be able to fiqure out the rest if any "Bugs" are found thru out the custom recovery. any help would be appericated.
below is a stock image of recovery and boot if needed
both images were from a " .Tar " file. I then extracted the file and got the recovery and boot in " .img.lz4 " format and then i converted them to " .img " only for easy access to edit ETC.
Android Version : 10
Current Firmware Version : A115MUBU1ATC2
Chipset : msm8953
Encryption State : encrypted
#System as Root
Uses an A/B operating System
https://drive.google.com/drive/folders/1mYYqvNgAXAxmiBH8ZDmbnoKMma4CUR12?usp=sharing
Click to expand...
Click to collapse
Yea, im also looking for a way to get some sort of custom recovery on the exact same device. My advice is (if you cant build your own version of twrp) to just wait for some devs to release something for it. The galaxy a11 is a very new device so we'll just have to wait it out.
Edit: So I followed a tutorial here (https://www.youtube.com/watch?time_continue=40&v=MyxGZbCuxDQ&feature=emb_logo) and i created this (https://filebin.net/u3yww2cyajktm043). IT MAY OR MAY NOT WORK!!! USE IT AT YOUR OWN RISK!!!!
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
ninjakira said:
what model number is yours? i have the one from boost its the sm-a115u and it seems the toggle for oem unlock is not in my dev settings on my phone
Click to expand...
Click to collapse
You can put the device into download mode and unlock the bootloader from there...
I'm currently stuck on this device trying to get it to unlock the boot loader. I've ticked OEM unlock but when I get into download mode (adb reboot download) I'm not getting any option to unlock the boot loader there. I'm also not able to get into download mode with any key commands. Any ideas here?
I've heard you power off, then hold volume up and down when you plug in a data cable. Haven't tried it yet, I'm on the a115u t-mobile variant. I can get to what it calls download mode, which looks to be fastboot and NOT the standard samsung blue screen download mode. Just boot to recovery and select reboot to bootloader. I do not have oem unlock in my dev settings, but I'll see if I can fastboot oem unlock when I get back to my laptop.
flash sm-a115u1 version firmware first. gives you oem unlock option. obviously toggle on and adb debugging. power off the phone. hold both volume buttons and insert usb cable. it will look like the normal blue download warning screen but read it carefully. it says long press volume up to unlock bootloader. it works. it will go black. release volume up and next it will ask you to confirm. choose yes. it will reboot and erase. after skipping thru set up enable dev options again and you will see oem toggle greyed out with a caption "bootloader already unlocked". thats as far as ive gotten. because now im like "what now?" i need a custom recovery file to flash to the device. any help with that out there? so now that the bootloader is unlocked can i install magisk to root and if so after that how can i network unlock? any help would be greatly appreciated. also looking for any custom roms that are available for this a11(2020). seems like a decent phone.thanks.
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Is there any updates that can be flashed with stock recovery
griha41 said:
Situation:
You can build your TWRP it's very easy. Or get compiled version from A10 and patch your system.
As result you'll get a bootloop.
Why?
Samsung had f****d you up and give you a SECURE BOOT that's not possible to remove by bootloader unlock. If you're install wrong signed recovery loader will said to you:
1st something is going wrong and signatures are mismatched, lete wipe your phone!
Ok. You jad solved that and not wiped your phone.
2nd hmm, signatures still mismatched I'll not boot and go in ***!
Result:
Untill someone will not break this Qualcomm Secure Boot you'll not able to install custom OS or TWRP or any other good stuff.
Click to expand...
Click to collapse
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
sdell said:
my a115u is stuck on load screen ,,after flash root trying to get bit un stuck ?????
ugg frustrating
Click to expand...
Click to collapse
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
griha41 said:
What's a point? Unpack firmware's AP_ file, extract boot.img, patch it through magisk, and flash through odin. But where in that thread header did you found the install root?
I want to remind you that recovery is bot a root part. That's why root thread and TWRP threads are separated.
Click to expand...
Click to collapse
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
sdell said:
cause i was new ..lol didnt know ..and still trying to understand it all but thqnk you for reply
Click to expand...
Click to collapse
Ahh I see. Sorry then.
You shall do that way. Find current fiware for your device, download it through fine software.
A result you will get 5 files with .zip extension.
You need to unpack file with AP_ prefix, i suggest you to use 7zip for that stuff. From file you need took off the boot.img.
Then boot.img you shall pack into archive.tar,
When you've done, down load the Magisk apk from github and install on your phone. Move your jew archive to phone memory/diwnload folder and start the Magisk, make patching of kenel, as result you'll receive the magisk_patched.tar, copy that file to your pc and start the Odin, place that archive in AP slot and flash it.
PROFIT!
But I want to warn you in android 10 and up there root and kernel system are different, now system is booting from super.img, and partition /,/system and etc are RO, so through the root you'll not able to change anything in system it would be wiped on next system restart.