Related
I just want to verify before I actually try this because I have already bricked one phone and i don't want to brick another.
How do I go about flashing CWM for my recovery instead of TWRP?
Can I just download CWM, rename it to recovery.img and run
Code:
fastboot flash recovery recovery.img
Or is there some other method??
Thanks.
BigRed35m said:
I just want to verify before I actually try this because I have already bricked one phone and i don't want to brick another.
How do I go about flashing CWM for my recovery instead of TWRP?
Can I just download CWM, rename it to recovery.img and run
Code:
fastboot flash recovery recovery.img
Or is there some other method??
Thanks.
Click to expand...
Click to collapse
you;ve got it exactly right! allthough remember that you've renamed it to recovey.img because if in the future you do the same again for twrp or a different version you may forget which you have renamed. In addition if you already ahve either recovery and root you can download rommanager/goo.manager and within the app flash cwm/twrp respectively without ever having to use fastboot. Allthough the CWM in the forums has larger text but its the same thing.
jonesin said:
you;ve got it exactly right! allthough remember that you've renamed it to recovey.img because if in the future you do the same again for twrp or a different version you may forget which you have renamed. In addition if you already ahve either recovery and root you can download rommanager/goo.manager and within the app flash cwm/twrp respectively without ever having to use fastboot. Allthough the CWM in the forums has larger text but its the same thing.
Click to expand...
Click to collapse
Thanks! I saw a couple forums that related to goo manager, but wasn't sure if I'd be able to use it without S-OFF or not. Running the command through CMD Prompt seems easiest for me right now so I'll give that a try. Thanks again.
BigRed35m said:
Thanks! I saw a couple forums that related to goo manager, but wasn't sure if I'd be able to use it without S-OFF or not. Running the command through CMD Prompt seems easiest for me right now so I'll give that a try. Thanks again.
Click to expand...
Click to collapse
One more thing TWRP has been exhibiting problems for many users and at this time and until further notice i would recomend against it. It can be made to work but is buggy
jonesin said:
One more thing TWRP has been exhibiting problems for many users and at this time and until further notice i would recomend against it. It can be made to work but is buggy
Click to expand...
Click to collapse
TWRP Has shown problems when trying to switch to CWM? Or just in general?
BigRed35m said:
TWRP Has shown problems when trying to switch to CWM? Or just in general?
Click to expand...
Click to collapse
not it has nothing to do with switching between the two
TWRP has exhibitied problems when attempting to create a backup or when attempting to restore a backup. Just avoid it for now CWM is more stable
jonesin said:
not it has nothing to do with switching between the two
TWRP has exhibitied problems when attempting to create a backup or when attempting to restore a backup. Just avoid it for now CWM is more stable
Click to expand...
Click to collapse
were the problems with the md5 sum part ? i had problems with CWM it wouldent backup so I had to to switch to twrp
syler2012 said:
were the problems with the md5 sum part ? i had problems with CWM it wouldent backup so I had to to switch to twrp
Click to expand...
Click to collapse
I have had problems backing up with both. Try switching backup type to .tar in CWM. TWRP has had problems backing up as well. Right now we dont have a rock solid stable recovery just have to work around it. CWM has had more fixes applied though I know this for a fact.
BigRed35m said:
I just want to verify before I actually try this because I have already bricked one phone and i don't want to brick another.
How do I go about flashing CWM for my recovery instead of TWRP?
Can I just download CWM, rename it to recovery.img and run
Code:
fastboot flash recovery recovery.img
Or is there some other method??
Thanks.
Click to expand...
Click to collapse
If you don't do a lot of backups/restores I actually recommend TWRP. The built in file manager makes file management without S-OFF a lot more hassle free. Another upside I've found with TWRP is "adb remount" actually works. It's just the little things. The downsides of TWRP that I've found are, add I've stated backup/restore and the size (which actually bugs me so much that I'm using CWM). Overall, as of now for this device, I recommend TWRP for the everyday rooted user.
Sent from my HTC6435LVW using xda app-developers app
hello to all...i am new to this developing. i have a rom file in .zip format....inside it there is system folder. i want to convert this .zip into a system img file. is it possible?? actually i hav a phone on which sdcard is not getting detected. so cwm recovery wont work, niether adb is detecting that device, so i want to make a system img file from this rom so that i can flash it using fastboot. Plz help me
niranjand147 said:
hello to all...i am new to this developing. i have a rom file in .zip format....inside it there is system folder. i want to convert this .zip into a system img file. is it possible?? actually i hav a phone on which sdcard is not getting detected. so cwm recovery wont work, niether adb is detecting that device, so i want to make a system img file from this rom so that i can flash it using fastboot. Plz help me
Click to expand...
Click to collapse
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
bill.weckel said:
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
Click to expand...
Click to collapse
i am trying it for huawei u8180
shinobisoft said:
For future reference, at the very least, state the device you have and or are having problems with. Makes things easier for people like me
What your asking for doesn't exist to my knowledge. However, you can extract the contents of the zip to your hard disk and use fastboot to flash the file "boot.img' which should be in the root of the zip you have. Everything else needs to be pushed via ADB to the /system partition. If your CWM is built correctly, ADB should detect your device when connected. That's assuming that you have your drivers installed already.
In reality, I don't think that what you are wanting to do can be done, however I don't know everything either. :silly: Best of luck
Click to expand...
Click to collapse
I tried this using Livesuit 1.11 for a softwinerEvb a13 tablet (no other known device specs) and it said the image file was invalid. Situation is I soft bricked my tablet by flashing the wrong cwm zip. Finally found out how to connect via Livesuit (kinda like fastboot or bootloader mode or something? like Odin?) to flash stuff to it. I decided to use an erase img .img because where I found how to connect it suggested that to the OP (on techknow). So now instead of the tablet just being stuck on the first screen when trying to boot (normal or recovery), it doesn't do anything at all since there's no boot.img. Which I'm not worried about since It connects to my laptop just fine via livesuit still so I can get a boot on it (ADB won't detect it - pretty positive it's not ADB user error [I run cmd "adb root" when the tablet is connect in whatever mode its in - the way livesuit detects it - and adb says no device found]. BUT I can't find a stock firmware/rom/boot.img for it anywhere (mainly since there's a bunch of clones of this tablet). I'm downloading a few roms (in boot.img format? - .7z files) that I found for "this" tablet (meaning the devs don't know which clones which roms work on lol).
ANYWAY haha, my question is, is there a way to do what you said in the above quote that will work in my situation? I'm not advanced enough to know why livesuit says the image is invalid. I tried it with a cm10.1 zip made for this tablet and a cwm zip made for this tablet (for both I extracted the files and then tried flashing the boot.img I found in the directory(extracted folder right?) via livesuit. livesuit said image file invalid for both .img's.
Please help me and THANK YOU in advance.
I'm open to anyone's help and any help is much appreciated! Thanks buttons will be pressed!!!
Same situation
Same Situation but I know the Specs,, It is allwinner A10 .and Stuck in the soft brick
could you solved this problem? i need a help too, the same problem
---------- Post added at 09:21 PM ---------- Previous post was at 09:13 PM ----------
vennkis said:
Same Situation but I know the Specs,, It is allwinner A10 .and Stuck in the soft brick
Click to expand...
Click to collapse
Hi, could you solved that?
i have a Chinese tablet a10, i have repaired different tablets and android phone trough ADB, but this devices is not detected, i have download some software to help me download the tablet drivers, but hasn't possible that.
finally the only source i have, is charge the firmware again, i use phoenix , and i have some rooms in zip format, what can i do for convert to IMG format?
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
how to convert?
m.morcielago said:
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
Click to expand...
Click to collapse
m.morcielago said:
Hello everyone
Finally what can we do?
How to convert .ZIP to .IMG ?
Click to expand...
Click to collapse
hahaha...no answer....i am still waiting for this software
doelwit.sunny said:
hahaha...no answer....i am still waiting for this software
Click to expand...
Click to collapse
You know just converting is not enough
I can convert it
But you need "partition table" for making .IMG
So we don't have it
check sdat2img and imgpatchtools
Is it specific for each device? Or does it depend only on finding the correct partition/block to be extracted?
Could you point me to further readings about that?
Thanks.
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
DopeyTheOne said:
It is at least device specific, for extracting the bootimage, check this http://forum.xda-developers.com/showthread.php?t=1951426
Sent from my Acer Cloudmobile S500
IF YOU THINK I MADE SOME SENSE, PLEASE HIT THE THANK BUTTON !!!
What if everything is an illusion, and nothing exists?
In that case, I definitely overpaid my carpet....!
Click to expand...
Click to collapse
Well, that link is to proceed AFTER you have boot.img at hand. I want to find a way to extract it from my phone (assuming default.prop can be changed in there).
Thanks.
When you make a back up with CWM, you have a copy of your bootimage in the clockworkmod map, not?
That's the thing ... I am trying to figure out how to get that backup in hand at first.
Currently, following the method in http://droidcore.blogspot.com.br/2012/12/how-to-edit-initrc-in-android.html
It seems to use the same scripts as cited in your link.
Will post results afterwards.
Don't make things more complicated as they are. If you just install CMW recovery (or TWRP for that matter) for your device, you have your full backup in minutes, including one of your bootimage, then use the script from my first post.
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
MrCabana said:
I managed to find boot.img, made the necessary changes, sent it back to device (used MPK Rom Studio and SP Flash Tool).
The problem is, the reason I want to change boot.img is to root my device. I thought that disabling ro.secure, I would be able to do so. But I couldn't.
I believe cmw recovery, or twrp, both need my phone to be rooted, no?
Click to expand...
Click to collapse
I used a CWM image to root my device. Booted up with that image, and flashed SU....after that you can use su, and apparantly, with the changes you made with your bootimage...you'll be like God on your phone
Sent from my S500 using xda app-developers app
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Click to expand...
Click to collapse
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
bromeara said:
Do you mean the stock firmware on the device, where is this located? or do you mean from the vendors web page?
Click to expand...
Click to collapse
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Alright thank you. I'm fairly new to the android ecosystem and to boot I'm working on a Fire tablet so its running fireos and amazon doesn't really make it easy to touch their code
think he is facing the same situation as mine, for hk version of htc u12+, its hard to find the proper RUU or firmware from internet. Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
Vita.T said:
Just wanna know the method of ...pulling the boot.img directly from device. Thanks in advance for any assistance.
Click to expand...
Click to collapse
Hey simply extract the boot.img from the stock firmware if your device is not rooted......
I think this only possible when you have root..
It is also not possible with adb without root...so
If your device is rooted with magisk then untouched boot.img is placed in /data folder as stock.xxxx.gz format and simply extract it....
If your device is rooted with one click root apps then download kernel auditor app and select backup option and the boot.img will be available in android/data/ kernel auditor specific folder....
Hope this help
Edit:- If your device is Mediatek, using SP Flash Tool you can readback. If you have Snapdragon, then bkerler's edl tool can readback. (No need of root)
HemanthJabalpuri said:
Bro it mean download the firmware from internet for your mobile and simply extract it...
Then you can find the boot.img
Click to expand...
Click to collapse
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
dano.556 said:
It's not that simple though, firmware comes in KDZ extension..have to extract using Extraction tool & even then extracted files are in .BIN extension..Boot.img is not available immediately after DZ extraction
Click to expand...
Click to collapse
Ok....
I am assuming that the op has a samsung device....
Same Problem
Loku_kika said:
I have the same problem, I need the boot image of my device to root it using magisk manager, but I can't find it.
Help!!!!!
Click to expand...
Click to collapse
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Lloydster said:
The Boot Image for oppo ax7 isn't available so i am trying to find aswell, OR i need help: taking the boot.img off my unrooted, non bootloader unlocked phone. Or extracting it from the stock ROM, unfortunately i'm not ble to open oppo's OFP file.
Click to expand...
Click to collapse
just google "Latest Software Version for OPPO OPPO AX7" and go to the Software Updates page on oppo-uk.custhelp.com. Download 2.4GB ozip file (like CPH1903EX_11_OTA_0210_all_oStq7F7jxqfF.ozip) and unpackit with 7zip program. You'll find boot.img inside .ozip file.
I do not have root, there is no recovery or rom for my phone, Can I extract the boot.img from my phone storage, to patch it with Magisk?
Is there a possibility to go into the recovery mode without using hardware keys or apps in a ROM?
Situation:
Download mode with odin works.
Power button destroyed.
Volume up + Home button brings no effect.
If it starts, it boots to ROM-Splash and seems to stuck in a bootloop.
Flashed Custom ROMs and Stock ROM, 1 and 3 parted - no success.
Is there a way to force the I9100 to boot into the recovery without Apps, Android or hardware keys?
In best, out of download mode with odin, like "odin force reboot"-tar file.
You can use adb. I think there is command like fastboot reboot recovery or something like thah
Sent from my iPad using Tapatalk
MatNEWBIE said:
You can use adb. I think there is command like fastboot reboot recovery or something like thah
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Thanks für your replay.
adb oder fastboot reboot recovery does not work - impossible to get a connection to device.
Isn't it possible to write a tar file and flash it via Odin that lets the device start into recovery next time?
I was never doing so. I don't use Odin too often, to get learn more I'm trying to do staff using adb... Hmmmm..... Were you trying to just flash stock kernel? Or kernel with philz? (Btw have you seen somewhere unsecured kernel with twrp same as stock? Share link if you had plx)
For this tar file... I think it's quite possible so search further.
P.S. I'm quite sure that I read that you can get out of such brick with adb but I forget how...
Sent from my iPad using Tapatalk
MatNEWBIE said:
Were you trying to just flash stock kernel?
Click to expand...
Click to collapse
No, always flashed 1 or 3 parted stuck ROM.
You think about formatting internal SD with pit-file and flash stock kernel from 3-parted stock ROM?
I don't remember where I could find it.
Would be a try, I think, whether it boots only into recovery after flashing.
I remember once, I flashed a kernel with CWM and that happend.
But never again.
Or kernel with philz?
Click to expand...
Click to collapse
Yes, no chance.
Only boots Stock ROM and bootloops.
I can't get into recovery, thats the problem.
(Btw have you seen somewhere unsecured kernel with twrp same as stock? Share link if you had plx)
Click to expand...
Click to collapse
not yet. If so, I'll link (try this first: http://www.cyanogenmod-forum.de/Thread-DOWNLOAD-TWRP-Downloadlinks)
For this tar file... I think it's quite possible so search further.
P.S. I'm quite sure that I read that you can get out of such brick with adb but I forget how...
Click to expand...
Click to collapse
I hope so.
ADB: I can't a a connection to the device, that's the problem. Else I could use adb reboot recovery to get into recovery and flash a new ROM, wiping, etc.
But I can't geht into recovery.
I really need such a script.
It is possible to create odin-friendly tar-files, but I don't know what to put in so it boots into recovery afterwards.
Man every phone I get, I brick!! Im stuck in a BLU boot loop. Can't find any files out there for this model. Well did see one here
http://clangsm.com/ftpdemo/index.php?dir=Flashes/BLU/Studio%20XL%202/
They want $$ for the download :crying:
Anyone a member there that could get me this file?
Thanks for the help
Try this
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
what version is this?
dougunder said:
Hey
https://www.ineedrom.tk/2017/04/09/blu-studio-xl-2-s0270uu-rom-stock-firmware/
I'm working on twrp. I haven't tried flashing it
edit: I've bricked and re-flashed. It's a good image
Click to expand...
Click to collapse
is this firmware v08? it rendered my phone inoperable. no cell, no camera and several other issues. the phone came installed with v09
Anyone ever find V09??
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
crmcc said:
I am also in need of BLU_S0270UU_V09_GENERIC firmware for a Studio XL2 , 6.0. Anybody have a source for this???
Thanks ahead!
Click to expand...
Click to collapse
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
mrmazak said:
I have a phone arriving tmw. First thing I will be doing is pulling the stock images. So if it has v09 I will link it for you.
I uploaded stock system and boot images to Androd File Host. If you still need them let me know.
Click to expand...
Click to collapse
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
killer13666 said:
Could you send me the links to the stock image? I recently rooted this phone using superSU and now I can't install Magisk due to the fact that superSU modified the boot image
Click to expand...
Click to collapse
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
mrmazak said:
here is link to my folder for the studio_XL_2
the stock images are in the zip labled
Blu-Studio_XL-2-__BLU_S0270UU_V09_GENERIC-01-03-2017.zip
the modifoed boot.img file will give root adb shell with ability to set selinux to permissive and then mount /system as rw all without needing superSU or magic installed.
The port zips are current w.i.p. of Cm/LM13 for the studio
Click to expand...
Click to collapse
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
killer13666 said:
Okay, I downloaded the files, but I'm not quite sure how to flash the images onto my phone.... Please forgive my ignorance as I've never had to do this before
Click to expand...
Click to collapse
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
mrmazak said:
I assume you already know how to get into twrp, because you were previously attempting to flash magic., So no need to cover that.
Put the boot.img to your phone (same way you put the superSu or magic zips)
To flash the boot.img, select install button in twrp. At lower corner or screen in twrp will appear button "Install Image", select that.
then browse folders same as usual but now will show you the img files available .
select the stock boot.img
next screen is "select Partiton to Flash Image"
select Boot, then "swipe"
this will return you to stock boot.img, as long as you were on V9 before.
You should also be able to flash the system.img the same way, if neede, but I have no way to know If is ok to use as upgrade from V8
must have images unzipped from main archive before putting to phone.
Click to expand...
Click to collapse
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
Click to expand...
Click to collapse
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
killer13666 said:
Okay, so flashing the boot image in the way you suggested worked for me, but there isn't an option to flash an image to system. Do I also just do that for boot or maybe uboot...?
---------- Post added at 11:16 AM ---------- Previous post was at 11:05 AM ----------
There isn't an option to flash it to system fyi, that's the only reason I am asking where I should flash it to.
Click to expand...
Click to collapse
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
mrmazak said:
No, don't put the system image anywhere except in system.
I will need to look at the twrp on the device again tonight.
I know the same recovery before being ported to the studio( on my life Max ) allows flashing system image. That's how I usually do my full reset.
On the studio I assumed it was same. Will update when I get back to PC. ( Tethered recovery is a pain ).
But do you actually need to reflash system though?
Click to expand...
Click to collapse
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
killer13666 said:
In trying to get the google assistant to work on my phone, I tried flashing something and I think it messed up the build.prop file along with some other things. I forgot to take a backup before flashing the zip and now my phone doesn't boot. It just has a black screen.
************************EDIT************************
/system won't mount either..............
Click to expand...
Click to collapse
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
mrmazak said:
system not mounting may be a bigger problem.
I ported different TWRP that has the flash system image option.
same as old one you must use "fastboot boot" to get into it, do not flash it to phone.
https://forum.xda-developers.com/devdb/project/dl/?id=27144
Click to expand...
Click to collapse
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
killer13666 said:
Okay, so I figured out why /system wasn't mounting. I accidentally set the rm -rf option instead of formatting the partitions, so I fixed the system partition not mounting. And this port of TWRP fixed my phone, so thank you so much for your help!
And as a side note, why exactly can I not flash TWRP onto the phone? What will happen if I do?
Click to expand...
Click to collapse
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
mrmazak said:
When the recovery is flashed inside, the touchscreen in recovery does not work. Making using recovery impossible, unless maybe a USB mouse would work
Click to expand...
Click to collapse
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
killer13666 said:
Is there like a port of CWM that I can flash to this? I remember an old phone of mine (I think it was a Samsung Fascinate), I had CWM on it and it didn't use the touchscreen at all, but rather it used the volume keys to move the selection and used the power button to actually select a menu item.
Click to expand...
Click to collapse
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
mrmazak said:
there is a "carliv" one . Its a CMW with touch also. But will work without.But it does not see the /data partiton on phone. so only good for install from micro sdcard
Click to expand...
Click to collapse
So in other words, it won't let you flash anything that'll modify the data partition as well?
killer13666 said:
So in other words, it won't let you flash anything that'll modify the data partition as well?
Click to expand...
Click to collapse
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
mrmazak said:
If all goes well, I may have a custom kernel in a few days that will enable the touchscreen
Click to expand...
Click to collapse
Please do let me know how that goes.