EDIT: I fixed it, I tried to install again with MODEM and success .
I had CM13 and wanted to upgrade version. Removed this version and tried to install newest version. It gave me an error ("It appears you are running an unsupported baseband") and i found this solution and did it:
Now, the "Unsupported Baseband" issue when flashing, at least CM based ROMs, is a known error recently. (In the past year I'd say) So the very common way to get around this, without having any issues, is to:
1. Go into your downloaded ROM zip, the zip you wish to flash, in your case it's crdroid-6.0.1-20160118-vs985.zip.
2. Extract the files into a folder (I'd recommend naming the folder the name of the .zip file, for ease in the end)
3. Open the extracted files folder
4. Open "META-INF" ==> "com" ==> "google" ==> "android"
5. Within that "android" folder, open "updater-script" file with Notepad, or a similar text editor.
6. Delete this line of code:
assert(getprop("ro.product.device") == "g3" || getprop("ro.build.product") == "g3" || getprop("ro.product.device") == "vs985" || getprop("ro.build.product") == "vs985" || abort("This package is for device: g3,vs985; this device is " + getprop("ro.product.device") + ".");
assert(g3.verify_baseband("35B:MPSS.DI.2.0.1.C1.13 .4-00005") == "1");
7. You should be left with "ui_print("Target: lge/g3_vzw....." in your case.
8. Overwrite the edited "updater-script" back to it's directory (the android folder)
9. (Make sure you don't save it as a .txt file, it should still be a "File" (no extension))
10. Now go back to the "crdroid-6.0.1-20160118-vs985" folder after editing and saving "updater-script"
11. Select all the files/folders within, and add them to a .zip archive (Recommended by using WinRar)
12. You should end up with a .zip file visually identical to the original crdroid-6.0.1-20160118-vs985.zip, except this one has the edited "updater-script"
13. The edited one^ is the only one you need now, and is the one you will be flashing
14. Also, if you're curious I have done this many times with CyanogenMod, on vs985, and can assure you nothing bad will come of this... I assume the same is with CrDroid as it is deeply based on CM. (As long as you're "Unknown Baseband" problem has been fixed.
Click to expand...
Click to collapse
After that i installed and opened it. It started to give me ''Google Play services stopped'' error. I tried to install again and after that it didn't boot. I learned that there is a problem with this version. After this i tried to install 03.23 (3 days later -they said that it's best stable version at now-) version but it didn't boot again (i saw LG logo and after that black screen). Tried to install CM12.1 but same happend again.
I'm waiting your helps!
Related
If you're trying to flash Task & Ktoonsez excellent 10/11 AOKPJellybean 4.1.2 ROM for the SGS3 AT&T/Rogers using TWRP 2.3.0.0 and it bombs with Error 7, you can:
Copy the zip to a Linux box (this is important!)
If you're using something modern, like Ubuntu 12.04, open the zip and replace the update-binary file as described on the TWRP 2.3.0.0 page h t t p : / /teamw.in/project/twrp2. Sorry, I'm a n00b and can't post links yet. The info is listed under the "What's new in 2.3.0.0" section, about a page length's down.
Try to flash again
I'm betting that you could also extract the zip, replace the file and rezip without a problem, but I didn't try it. I was successful doing this using Ubuntu 12.04 x64 but I'm also very sure you could do this in about any distro.
Good luck!
m3741 said:
If you're trying to flash Task & Ktoonsez excellent 10/11 AOKPJellybean 4.1.2 ROM for the SGS3 AT&T/Rogers using TWRP 2.3.0.0 and it bombs with Error 7, you can:
Copy the zip to a Linux box (this is important!)
If you're using something modern, like Ubuntu 12.04, open the zip and replace the update-binary file as described on the TWRP 2.3.0.0 page h t t p : / /teamw.in/project/twrp2. Sorry, I'm a n00b and can't post links yet. The info is listed under the "What's new in 2.3.0.0" section, about a page length's down.
Try to flash again
I'm betting that you could also extract the zip, replace the file and rezip without a problem, but I didn't try it. I was successful doing this using Ubuntu 12.04 x64 but I'm also very sure you could do this in about any distro.
Good luck!
Click to expand...
Click to collapse
This actually works for cwm as well and any rom that throws that error when flashing and doesn't need to be done on a linux box. The way I do it, is open the zip using winrar, don't extract it, navigate to the updater-script and open it with Notepad++, notepad or wordpad messes it up, but Notepad++ preserves the linux stuff so you can still flash it. Edit the file and remove the first line that says "assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");" without the quotes. Save and Close the file and it will ask if you want to update it in the archive, say yes. That's it, just transfer it to your phone and voila!
Hope this help some others out there!
majorassface said:
This actually works for cwm as well and any rom that throws that error when flashing and doesn't need to be done on a linux box. The way I do it, is open the zip using winrar, don't extract it, navigate to the updater-script and open it with Notepad++, notepad or wordpad messes it up, but Notepad++ preserves the linux stuff so you can still flash it. Edit the file and remove the first line that says "assert(getprop("ro.product.device") == "d2att" || getprop("ro.build.product") == "d2att");" without the quotes. Save and Close the file and it will ask if you want to update it in the archive, say yes. That's it, just transfer it to your phone and voila!
Hope this help some others out there!
Click to expand...
Click to collapse
Nice! I'll give this a shot when I get home. I always love knowing little tidbits like this as I'm sure it'll save me in the future sometime too.
TeamWin Recovery Project
Restore in the old 2.4.1 version doesnt work for me. I build from source, now it works, I share.
Download
http://dualhoki.vim.hu/bubor/dev/twrp-i927/
http://rpi.bubor.hu/bubor/dev/twrp-i927/
Current Issues:
display timeout blank screen disabled
Issue report:
Give everything I need to reproduce the problem (logs, guide, dumps etc), I wont reply useless reports.
Changelog:
Changelog can be found : http://www.teamw.in/project/twrp2
2.6.1 wipe data make smaller data partition, that need for encyption. Encypt mount support.
2.6.3 removed superuser, compiled with cm-10.2
2.6.3-2 add fuse, it should support extfat
2.6.3-3 remove encypt, puth superuser (Rooting)
2.6.3-4 put security fs, selinux, it will need for flash cm-11.0
2.6.3.1 update twrp from git (actually its 2.7.0, but you will see 2.6.3 in the corner)
2.7..1: update twrp, compiled with cm-10.2
2.8.4: compild with cm-11.0, fix MTP
Credit:
Terinfire(Source)
Dman(Source)
thegreatergood
TWRP TEAM
Install
Install zip from TWRP or ClockworkModRecovery
Put device to download mode ( power on, while hold volume up, hit volume up again when asked to do ), and use odin (included in the zip, browse to pda, dont flash other)
Changelog: http://www.teamw.in/project/twrp2
You may want to install older rom, you must change assert tag in rom zip file META-INF/com/google/android/updater-script:
Code:
assert(getprop("ro.product.device") == "i927" || getprop("ro.build.product") == "i927" ||
getprop("ro.product.device") == "SGH-I927" || getprop("ro.build.product") == "SGH-I927" ||
getprop("ro.product.device") == "SGH-I927R" || getprop("ro.build.product") == "SGH-I927R" ||
getprop("ro.product.device") == "SGHI927" || getprop("ro.build.product") == "SGHI927" ||
getprop("ro.product.device") == "SGHI927R" || getprop("ro.build.product") == "SGHI927R" ||
getprop("ro.product.device") == "n1" || getprop("ro.build.product") == "n1" || abort("This package is for \"i927,SGH-I927,SGH-I927R,SGHI927,SGHI927R,n1\" devices; this is a \"" + getprop("ro.product.device") + "\"."););
Awesome! Thanks so much for fixing this for Team Glide!
Sent from my Rooted Samsung SGH-i927 Captivate Glide
Running @ndroid JB4.2.2 CM10.1 & TWRP 2.4.4.0 using xda-dev app.
They just released a newer version 2.5.0.0
Sent from my Rooted Samsung SGH-i927 Captivate Glide
Running @ndroid JB4.2.2 & TWRP 2.4.4.0 using xda-dev app.
*thanks bubor for keeping twrp up to date.
*please keep twrp up to date since it can then use rom manager to do all the wipes, flash and install roms and gapps package an dother patches along he way.
*can the img extension just be use through adb to get that to the phone or not?
*how is this done and steps pleas?
dd if=recovery.img of=/dev/block/mmcblk0p8
You can find recovery.img inside the zip.
update to 2.6.1
Oh my...
I think this is one of the best finds for the Cappy Glide since CM10.1...
Thank you! Thanks SOOOOO MUCH!
I was about fed-up with CWMR, having to spam the volume buttons, but now with touch controls, I mean, COME ON! How much better could it get to flash and recover and restore and backup stuff! Thank you! BIG THUMBS UP!
:good::good::good::good::good:
great thanks, its time to udate it. i see we have a version from odin and one to flash via CWMR.
Initially got some strange "assert getprop" errors when flashing stock Samsung flashable packs (CWM does the job), but flashing CM and PAC looks alright. Just why does the stock flashables all require ro.product.device=SGHI927... (normally it would be SGH-I927)
Sent from Samsung Captivate Glide @ CM10.1.2
AndyYan said:
Initially got some strange "assert getprop" errors when flashing stock Samsung flashable packs (CWM does the job), but flashing CM and PAC looks alright. Just why does the stock flashables all require ro.product.device=SGHI927... (normally it would be SGH-I927)
Sent from Samsung Captivate Glide @ CM10.1.2
Click to expand...
Click to collapse
assert tag changed a year ago, old custom 4.0/4.1 doesnt work with newer recoveries.
New roms test both assert tags. You can change test in rom's zip file.
Well after upgrading to 2.6.3 I get fail to create directory & failed to backup? This is to either internal or external. On 2.6.1 I was getting fails to restore? Anyone else having these issues?
Sent from my Rooted Samsung SGH-i927 Captivate Glide Running Android ICS 4.0.4 LiteRom 0.9.0 & TWRP 2.6.3 using xda-dev app.
amppcguru said:
Well after upgrading to 2.6.3 I get fail to create directory & failed to backup? This is to either internal or external. On 2.6.1 I was getting fails to restore? Anyone else having these issues?
Sent from my Rooted Samsung SGH-i927 Captivate Glide Running Android ICS 4.0.4 LiteRom 0.9.0 & TWRP 2.6.3 using xda-dev app.
Click to expand...
Click to collapse
could you write detail? uploading /tmp/recovery.log helps lot.
I just made a backup and restore, and it works.
TWRP 2.6.3 bu failure
bubor said:
could you write detail? uploading /tmp/recovery.log helps lot.
I just made a backup and restore, and it works.
Click to expand...
Click to collapse
Hm I don't see a tmp folder in root or twrp. I did a search for all recovery.log files & only found the ones from 2.6.1 backups
I had to go back to 2.6.1 & got it to backup & restore.
I've attached one of those.
When trying using 2.6.3 it says it "Unable to create Folder: /external_sd/TWRP/..."
"Failed to make backup folder"
I am running TGG Literom 0.9.0
amppcguru said:
Hm I don't see a tmp folder in root or twrp. I did a search for all recovery.log files & only found the ones from 2.6.1 backups
I had to go back to 2.6.1 & got it to backup & restore.
I've attached one of those.
When trying using 2.6.3 it says it "Unable to create Folder: /external_sd/TWRP/..."
"Failed to make backup folder"
I am running TGG Literom 0.9.0
Click to expand...
Click to collapse
try to rename TWRP to TWRP2,and lets it creates new one.
2.6.3 backup unable to create folder
bubor said:
try to rename TWRP to TWRP2,and lets it creates new one.
Click to expand...
Click to collapse
I tried renaming them & reflashed 2.6.3 but still get the same error messages of it not being able to create backup folders? Very strange.... I could have sworn it was working the first time I flashed it? But now these repeated errors have me mystified?
Edit: I also tried redownloading 2.6.3 & reflashing but still getting the same error messages?
Ive had to reflash 2.6.1 & it works perfectly!
2.6.3
Doesn't seem capable of mounting 64gb exfat formatted SDXC card.
Just says failed to mount or something along those lines, mounted a 8gb FAT32 card, wouldn't mount an old FAT 512mb card.
I know for a fact the 2.6.1 is capable of mounting the 64gb exfat card. Flashed back to it and no issues.
amppcguru said:
I tried renaming them & reflashed 2.6.3 but still get the same error messages of it not being able to create backup folders? Very strange.... I could have sworn it was working the first time I flashed it? But now these repeated errors have me mystified?
Edit: I also tried redownloading 2.6.3 & reflashing but still getting the same error messages?
Ive had to reflash 2.6.1 & it works perfectly!
Click to expand...
Click to collapse
I had the same error, so i just downloaded nandroid backup from the play store, and it works wonders if you choose TWRP as your recovery.
Sent from my SGH-I927 using XDA Premium 4 mobile app
I also had the same problem, but with d2att - changed the auto generated backup name and it worked (also fixed permissions but not sure if it was necessary to or not).
bubor said:
assert tag changed a year ago, old custom 4.0/4.1 doesnt work with newer recoveries.
New roms test both assert tags. You can change test in rom's zip file.
Click to expand...
Click to collapse
Went to older recovery, still not able to flash.
WTF?
Sent from my SGHI927 using Tapatalk
Changing the auto-generated name fixed for me too.
Hi, I have been flashing nightlies since CM11 came out with no issues (maybe once a week, so quite a few times).. The version I currently have installed is 11-20140204. I have been just dirty flashing manually in CWM, installing from SD card / install ZIP.
For some reason I cannot update anymore ? Any of the new Nightly versions give me a STATUS 7 and to my knowledge nothing on my phone has changed ?
I have updated to the latest CWM - 6.0.4.7. and still wont work.
Here is the error I am getting :
Installing Update:
Assert failed:
getprop (“re.bootloader”) == “I747UCDMG2”
getprop (“re.bootloader”) == “I747UCUEMJ2”
getprop (“re.bootloader”) == “I747UCUEMJB”
getprop (“re.bootloader”) == “I747MVLDMF1”
getprop (“re.bootloader”) == “I747MVLUEMK5”
getprop (“re.bootloader”) == “I747MUMUEMK3”
E: Error in /data/media/0/cm-11-20140216-NIGHTLY-d2att.zip (STATUS 7)
Installation aborted.
Please help, Thanks
I was having the same problem and if you look around a little you can try editing the updater script.... There is a whole step by step tutorial somewhere in this forum. You have to unzip the ROM and edit the updater-script file but here is the link just copy and paste it, its a couple comments down and it has worked for a ton of people, I'm still having issues but its helped a ton of people to flash successfully.
http://forum.xda-developers.com/showthread.php?p=38880428
Is your bootloader included in the list of supported loaders?
Use TWRP instead.
Flash this, http://invisiblek.org/d2firmware.html
Format /cache, dalvik, /system, /data, and your internal SD card, then try again.
Sent from my SGH-I747 using Tapatalk
RJantu said:
Use TWRP instead.
Flash this, http://invisiblek.org/d2firmware.html
Format /cache, dalvik, /system, /data, and your internal SD card, then try again.
Sent from my SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Won't formatting your internal SD card delete your nandroid backups if that's where your cwm stuff is? I'd like to find a solution for my issue to I have the new bootloader from 4.3 UCUEMJB and I successfully rooted it and installed philz cwm and removed Knox with the Knox remover zip and then I successfully flashed beanstalk 4.4.1 which I'm still running and with no issues......but I haven't been able to flash anything else.... So I was considering trying twrp because at first I was getting those errors then edited the updater scripts in the ROMs I was trying to flag just for it to abort installation again and not because of a status 7 error I think it said something about data/0 / volume or something crazy like that which is all foreign to me.
Hello, I recognize a strange thing in my S4 mini. If I turn on my device the screen shows me the main logo and the GT-I9195 sign. So it is an LTE version. Now the problem. I wanted to install an serranoltexx zip and cwm says " This package is for serranoltexx devices, this is a serrano3gxx device. serrano3gxx.zips will installed ironical.
Whats that. That happens during many trys to install a serranoltexx.zip. Every time the same massage. But if I try to install a zip that comes with the aroma installer I can choose the right version with no error massage and a clean and workable installation.
can anybody help me
AlexandreVegetaroux said:
Hello, I recognize a strange thing in my S4 mini. If I turn on my device the screen shows me the main logo and the GT-I9195 sign. So it is an LTE version. Now the problem. I wanted to install an serranoltexx zip and cwm says " This package is for serranoltexx devices, this is a serrano3gxx device. serrano3gxx.zips will installed ironical.
Whats that. That happens during many trys to install a serranoltexx.zip. Every time the same massage. But if I try to install a zip that comes with the aroma installer I can choose the right version with no error massage and a clean and workable installation.
can anybody help me
Click to expand...
Click to collapse
the error comes from the zip you flashing ... open the zip of serranoltexx go to META-INF>com>android>updater script ... open it with notepad++ and replace every i9190 with i9195
Ok, Thank you. I looked in that pathfile and everything is ready for serranoltexxx
for example:
assert(getprop("ro.product.device") == "serranolte" || getprop("ro.build.product") == "serranolte" ||
getprop("ro.product.device") == "serranoltebmc" || getprop("ro.build.product") == "serranoltebmc" ||
getprop("ro.product.device") == "serranoltektt" || getprop("ro.build.product") == "serranoltektt" ||
getprop("ro.product.device") == "serranoltexx" || getprop("ro.build.product") == "serranoltexx" || abort("This package is for \"serranolte,serranoltebmc,serranoltektt,serranoltexx\" devices; this is a \"" + getprop("ro.product.device") + "\".");
and the last...this is a. "" + getprop("ro.product.device") + "\"."); the updater extract the actually device name...in my case it reads out serrano3gxx.
very strage
PS.: I have to say that my phone works not perfect. It does not charge. only if I charge the battery in an separate static charger it does. Than I can switch the phone on and than it works. But with this strange behavior during the cwm install process. The phone does not charge(with this strange grey battery symbol) since it was totally flat or dead(i do not know how I could say in english). I do not know if those two strange behaviors are related to each other. No charge animation except if I connect the phone with the laptop, nevertheless it does not charge according the battery menu.
Thanks so far
Hello all. A friend of mine has LeEco Le1 Pro US version and his usb port was not working when connected to pc or adb, but only working in fastboot mode. the phone has twrp but we cant flash any roms through twrp because the pc wont recognize it(yes we have proper drivers installed). the phone has no os and the only way is to flash roms manually through fastboot mode but I cannot find any roms that are flashable through fastboot. Are there any solutions? Thanks in advance.
jimakos98 said:
Hello all. A friend of mine has LeEco Le1 Pro US version and his usb port was not working when connected to pc or adb, but only working in fastboot mode. the phone has twrp but we cant flash any roms through twrp because the pc wont recognize it(yes we have proper drivers installed). the phone has no os and the only way is to flash roms manually through fastboot mode but I cannot find any roms that are flashable through fastboot. Are there any solutions? Thanks in advance.
Click to expand...
Click to collapse
Hi, I give you an easy method to make update.zip flashable through TWRP.
On your PC open update.zip with (Zip, Winrar or 7z..), go to folder META-INF > com > google > android In this folder, select the updater-script file and extract it anywhere in your computer, then open it in a text-editor, put # in the beginning of the first line, save it, drag and drop the newly edited updater-script file back to the ZIP file to update the package with it (Check that the path where the file is copied back is the same !). it may take some time to repack it
You're done !!! Now you can flash the package as usual from TWRP without any issue.
Good Luck.
Code:
#getprop("ro.product.device") == "msm8994" || getprop("ro.product.device") == "x1_na" || abort("This package is for \"x1_na\" devices; this is a \"" + getprop("ro.product.device") + "\".");
package_extract_file("splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("bootvideo.img", "/dev/block/bootdevice/by-name/bootvideo");
set_progress(0.500000);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
set_progress(0.950000);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
set_progress(1.000000);
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/pmic.mbn", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1bak");
package_extract_file("firmware-update/pmic.mbn", "/dev/block/bootdevice/by-name/pmicbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
Here you can find a Fastboot Rom. many thanks to @Aurel
nsmsdz said:
Hi, I give you an easy method to make update.zip flashable through TWRP.
On your PC open update.zip with (Zip, Winrar or 7z..), go to folder META-INF > com > google > android In this folder, select the updater-script file and extract it anywhere in your computer, then open it in a text-editor, put # in the beginning of the first line, save it, drag and drop the newly edited updater-script file back to the ZIP file to update the package with it (Check that the path where the file is copied back is the same !). it may take some time to repack it
You're done !!! Now you can flash the package as usual from TWRP without any issue.
Good Luck.
Code:
#getprop("ro.product.device") == "msm8994" || getprop("ro.product.device") == "x1_na" || abort("This package is for \"x1_na\" devices; this is a \"" + getprop("ro.product.device") + "\".");
package_extract_file("splash.img", "/dev/block/bootdevice/by-name/splash");
package_extract_file("bootvideo.img", "/dev/block/bootdevice/by-name/bootvideo");
set_progress(0.500000);
block_image_update("/dev/block/bootdevice/by-name/system", package_extract_file("system.transfer.list"), "system.new.dat", "system.patch.dat");
set_progress(0.950000);
package_extract_file("boot.img", "/dev/block/bootdevice/by-name/boot");
set_progress(1.000000);
# ---- radio update tasks ----
ui_print("Patching firmware images...");
ifelse(msm.boot_update("main"), (
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpm");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tz");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/aboot");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1");
package_extract_file("firmware-update/pmic.mbn", "/dev/block/bootdevice/by-name/pmic");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hyp");
), "");
ifelse(msm.boot_update("backup"), (
package_extract_file("firmware-update/rpm.mbn", "/dev/block/bootdevice/by-name/rpmbak");
package_extract_file("firmware-update/tz.mbn", "/dev/block/bootdevice/by-name/tzbak");
package_extract_file("firmware-update/emmc_appsboot.mbn", "/dev/block/bootdevice/by-name/abootbak");
package_extract_file("firmware-update/sbl1.mbn", "/dev/block/bootdevice/by-name/sbl1bak");
package_extract_file("firmware-update/pmic.mbn", "/dev/block/bootdevice/by-name/pmicbak");
package_extract_file("firmware-update/hyp.mbn", "/dev/block/bootdevice/by-name/hypbak");
), "");
msm.boot_update("finalize");
package_extract_file("firmware-update/NON-HLOS.bin", "/dev/block/bootdevice/by-name/modem");
package_extract_file("firmware-update/BTFM.bin", "/dev/block/bootdevice/by-name/bluetooth");
Here you can find a Fastboot Rom. many thanks to @Aurel
Click to expand...
Click to collapse
Thanks for the help, but I actually found a china "prototype" fastboot rom, flashed it and then transfered the stable rom I wanted to flash with an app that connects the phone and the pc with wifi since PCs wouldn't recognize the phone when connected with a usb cable. However I'm saving this answer for future usage in case I run into trouble again.
jimakos98 said:
Thanks for the help, but I actually found a china "prototype" fastboot rom, flashed it and then transfered the stable rom I wanted to flash with an app that connects the phone and the pc with wifi since PCs wouldn't recognize the phone when connected with a usb cable. However I'm saving this answer for future usage in case I run into trouble again.
Click to expand...
Click to collapse
Hi, jimakos98. Please, can you tell us which app did you find it "that connects the phone and the pc with wifi since PCs wouldn't recognize the phone when connected with a usb cable"? and explain in detail how to proceed to get the phone visible from the pc?
Thanks in advance.
mipatriaeslaurss said:
Hi, jimakos98. Please, can you tell us which app did you find it "that connects the phone and the pc with wifi since PCs wouldn't recognize the phone when connected with a usb cable"? and explain in detail how to proceed to get the phone visible from the pc?
Thanks in advance.
Click to expand...
Click to collapse
First of all, the phone was recognizable by PC but only in fastboot mode. The way I got to flash the TWRP flashable only ROM I wanted for my smarthpone, was this: I found a fastboot flashable ROM which was labeled as "chinese prototype developer ROM" and flashed it. After that, I booted the device and went to play store and downloaded the app called "AirDroid" which lets you "control" the phone from your PC through Wi-Fi. After that, I transfered the desired ROM (which was TWRP flashable only and not fastboot) to the device through the PC with AirDroid and then rebooted to TWRP and finally flashed the ROM. Keep in mind that the device is still not recognized by PC in normal/adb mode and only in fastboot so this is probably a hardware issue since we tried lots of different roms and usb cables with no result.