Hey guys,
Got a no name phone with mtk6580 and kernel 3.10.72 running custom Chinese android 5.1, and as you probably guessed I got problem flashing custom recovery on it, the device is not on the list for neither TWRP nor CWP.
What to do?
Thank you
Vant2239 said:
Hey guys,
Got a no name phone with mtk6580 and kernel 3.10.72 running custom Chinese android 5.1, and as you probably guessed I got problem flashing custom recovery on it, the device is not on the list for neither TWRP nor CWP.
What to do?
Thank you
Click to expand...
Click to collapse
A good place for no name phones is here:
https://forum.hovatek.com/forum-76.html
Either have a search or put a request for someone to make a TWRP for your phone, I put a request in and the next day someone made one for me.
I did try to make my own from a guide on here, its apparently really easy but I just couldnt get it to work, here is the one someone made for me which may work or at least gives you a good starting base to try: http://www.needrom.com/download/uhappy-up580-twrp-recovery/
robneymcplum said:
A good place for no name phones is here:
https://forum.hovatek.com/forum-76.html
Either have a search or put a request for someone to make a TWRP for your phone, I put a request in and the next day someone made one for me.
I did try to make my own from a guide on here, its apparently really easy but I just couldnt get it to work, here is the one someone made for me which may work or at least gives you a good starting base to try: http://www.needrom.com/download/uhappy-up580-twrp-recovery/
Click to expand...
Click to collapse
Once again thanks a lot for reply!
I have successfully ported one of your builds, but with some mindless actions trying to flash recovery through fast boot got a boot loop of some sort, logo keeps appearing and phone doesn't boot.
What I did is in fastboot flashed recovery with help of 'fastboot oem unlock' and now I just stuck. I have stock recovery, tried to flash it back but unsuccessfuly. Any idea how can I fix it?
Sorry for being such a noob
recovery and/or firmware should be flashed with SPflash tool simply because I find its the easiest way,
Perfect way of doing things is:
SPflash tools=flash stock firmware til 'done' close SPflash
remove battery, put back in, boot, maybe stuck on boot image (happens to me 50% of the time)
remove battery, put back in, boot. Let it boot up and set up wifi/internet
turn off phone, battery out, back in DONT POWER ON
reopen SPflash, select correct scatter.txt file from stock firmware again
unselect all tick boxes, tick recovery box, click on 'address or location of recovery' and locate the TWRP image
click download, plug turned off phone in.
wait til done.
battery out, back in, boot to recovery with correct button presses (volume up+power?)
in recovery, set correct time
reboot recovery and allow install of superSU, reboot phone, select superSU from the notification and update.
Then put the new custom rom onto sdcard and reboot back to recovery, wipe system/data/cache/dalvik cache and install rom
install gapps
wipe caches
reboot
That is a perfect way of doing it, if the rom doesnt boot something is wrong with the rom/boot img/something
fix that, put back onto sdcard, just do the 4 wipes again and install rom again
and again
and again
until it is fixed and boots.
robneymcplum said:
recovery and/or firmware should be flashed with SPflash tool simply because I find its the easiest way,
Perfect way of doing things is:
SPflash tools=flash stock firmware til 'done' close SPflash
remove battery, put back in, boot, maybe stuck on boot image (happens to me 50% of the time)
remove battery, put back in, boot. Let it boot up and set up wifi/internet
turn off phone, battery out, back in DONT POWER ON
reopen SPflash, select correct scatter.txt file from stock firmware again
unselect all tick boxes, tick recovery box, click on 'address or location of recovery' and locate the TWRP image
click download, plug turned off phone in.
wait til done.
battery out, back in, boot to recovery with correct button presses (volume up+power?)
in recovery, set correct time
reboot recovery and allow install of superSU, reboot phone, select superSU from the notification and update.
Then put the new custom rom onto sdcard and reboot back to recovery, wipe system/data/cache/dalvik cache and install rom
install gapps
wipe caches
reboot
That is a perfect way of doing it, if the rom doesnt boot something is wrong with the rom/boot img/something
fix that, put back onto sdcard, just do the 4 wipes again and install rom again
and again
and again
until it is fixed and boots.
Click to expand...
Click to collapse
Im getting an error when try to flash it: ERROR: S_DL_GET_DRAM_SETTING_FAIL (5054)
trying to flash stock firmware?
I had numerous issues getting mine to flash the first time, I downloaded and tried different versions of SPflash tools, different USB leads/ports etc...
I have to use a USB lead from my moto x play as the stock lead wouldnt work, my galaxy tab lead wouldnt work either.
I have to use SPflash tool version SP_Flash_Tool_exe_Windows_v5.1552.00.000 as other versions kept bringing up that error and similar ones.
It really does seem to be trial and error unfortunately.
Related
I've spent my entire day trying to flash a recovery image on my streak to no avail. I've rooted it using the super one click, have superuser on my device, along with clockworkmod.
I've confirmed my device is rooted using z4root.
I've tried flashing the recovery via clockwork, it says it was successful, yet when I reboot to recovery, I always end up in the regular OS, like all it did was reboot. Furthermore, trying to manually get there, holding down the buttons, tells me that the stanard recovery wasn't actually overwritten. When I go through fastboot and flash it that way, both computer and streak tell me that everything was successful. Yet, the recovery was still not overwritten.
My end goal is to put Steve's ROM on the streak, but I can't even get the recovery overwritten with clockworkmod.
I have a Dell Streak OEM:340. Thats the locked ATT version, which I think might be a part of the problem.
How do I end up with Steve's rom?
Sounds like you are using ROM manager? That does not work well with the Streak. See this article. ROM manager may actually flash your recovery, but does not work to start the phone in that mode.
You can flash the recovery image to your phone in fastboot mode. Here is a tool to help.
You get to fastboot mode by starting the Streak while holding the camera and power buttons at the same time. Then select fastboot from the top right of the screen and plug your phone into your computer. You will need the Dell drivers for this.
Also be aware that you need to rename install-recovery-sh to something else to prevent the stock recovery from being installed when the phone restarts. It's in the folder /etc. You have to use root explorer or an alternate method to do this, but it requires root.
I am using a ROM manger, but if that doesn't work as well, I'll stop.
I've been fastbooting it the majority of the time, flashing the ROM, but it says I've done it correctly, even though I obviously haven't. So far, all I know is that it's been rooted, and the recovery flashed via fastboot.
kyrillos27 said:
I am using a ROM manger, but if that doesn't work as well, I'll stop.
I've been fastbooting it the majority of the time, flashing the ROM, but it says I've done it correctly, even though I obviously haven't. So far, all I know is that it's been rooted, and the recovery flashed via fastboot.
Click to expand...
Click to collapse
Have you renamed the install-recovery.sh file so that the custom recovery won't be replaced by the stock recovery when you reboot? If not - do so.
Make sure that the Streakdroid rom you want is in the root of the SD Card along with the install.txt file.
If you can get into fastboot mode and connect to your computer I suggest using MultiRecoveryFlasher Streakmod recovery. You can reboot the phone from there also.
When you reboot you want to get to recovery mode. Turn your phone off then press the power button tile the leds light up and as soon as they do hold down BOTH volume buttons. See this gallery for what Streammod recovery should look like. Selecting the #2 option will take you to the streakmod recovery options. You use the "apply sdcard:update.zip" to install the ROM.
See the release thread for the ROM you are installing for more info and post any problems or questions you have with the ROM in that thread.
I have not renamed the install-recovery.sh file. in fact, haven't seen one through the process. To be honest, I'm not sure this part has been done at all by me. How do I go about doing that?
Furthermore, choosing the second option in recovery doesn't give methe streakmod options, it just tells me everything will be erased (stock Dell recovery). How do I make sure that this gets corrected?
For the record, marvin02, thank you thus far for the amount of help you've been giving me.
kyrillos27 said:
I have not renamed the install-recovery.sh file. in fact, haven't seen one through the process. To be honest, I'm not sure this part has been done at all by me. How do I go about doing that?
Furthermore, choosing the second option in recovery doesn't give methe streakmod options, it just tells me everything will be erased (stock Dell recovery). How do I make sure that this gets corrected?
For the record, marvin02, thank you thus far for the amount of help you've been giving me.
Click to expand...
Click to collapse
The file install-recovery.sh is a script that runs each time your phone is started. It will replace a custom recovery (streakmod) with the stock recovery when your phone starts, so the next time you enter recovery mode you are back at the stock recovery.
If you are going to dstay with a stock ROM, but want a custom recovery you have to rename the file. The easiest way (IMO) is to use Root Explorer which is an app you have to buy. You just open root explorer and the open the folder named etc and find install-recovery.sh long pres on it to get a menu to pop up and then select rename.
You don't have to do that to get a streakdroid rom installed if you enter recovery without letting the phone restart first.
Put the streakdroid rom file and the install.tx on the root of your SD card
Turn your phone off
Turn phone on in fastboot mode (camera and power buttons at the same time)
Use this tool to to flash the recovery you want
Using the same tool you can reboot the phone
As the phone reboots (wait for the leds to turn on just like they do when you restart the phone) hold down BOTH volume buttons to enter recovery. If you let the phone boot normally and you have not renamed install-recovery.sh the custom recovery will be over written.
Select option 2 and you should be taken to the streakmod options (images here)
Select apply sdcard:update.zip from the recovery menu
There will be two options on the next screen, select the one that lets you navigate to/select a file and then select the ROM file you put on your SD Card.
The ROM should install, be patient when it reboots it can take a few minutes.
Okay my Atrix 4g has unlocked bootloader, Android 2.3.6, and I flashed CWM recovery the other day, and it worked fine except whenever I plugged in my phone to wall charger, it would boot AUTOMATCALLY into that recovery. Followed this guide: LINK
I then installed CWM recovery 5.0.2.3 from here: LINK
Now again when I plug usb into wall to charge, it boots into the first recovery I installed. I can't see the battery charge symbol.
Now I downloaded this ROM - http://forum.xda-developers.com/showthread.php?t=1836674 and tried to boot into recovery from using the volume down button until "Android recovery" but that takes me to the stock 4 option crap.
So I tried to flash the MROM from ROM manager in the os, and it says restarting into recovery, AGAIN that takes me to the triangle exclamation point crap.
SO MY QUESTION is if I do a disk clear, format from the recovery, would my phone still work with T-mobile afterwards, and I can install the CWM again, and flash the new ROM?? I don't care about losing data, I have only few apps.
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
ravilov said:
Here's a crazy idea - did you by any chance install the recovery image on the BOOT partition instead of the RECOVERY partition?
If you can't do it manually, there is no point in trying with ROM manager, since it can't do anything you can't do yourself.
Click to expand...
Click to collapse
Here's a crazier idea - do you mind explaining things in more detail, since I am a noob and this is a help forum.
--
When I install the the recovery, it just says hit yes to continue. Please help, rather than telling me that I am an idiot.
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
ravilov said:
Apologies, didn't mean to imply you're stupid or anything. I said "crazy" because it is very unlikely but your symptoms kinda point to exactly that. This can easily happen actually - both the boot image and the recovery image are of the exact same structure (kernel + ramdisk) and the partitions that hold them are both exactly the same size (8 MB). The only difference is, with recovery the ramdisk launches an user interface and never leaves it, while with boot the ramdisk chains to booting your normaly system. Never tried it, but I believe if one flashes recovery on the boot partition, the end result would be that the phone boots into recovery every time you'd expect it to boot normally.
How exactly did you flash recovery? Don't link me to a thread or a procedure but rather describe what you did, what commands you issued and what was the response.
Click to expand...
Click to collapse
No problem mate.
Well I guess I could tell you what I did, but I did exactly what the guides said:
downloaded the .zip archive, placed contents anyplace, and started cmd from that folder and entered:
adb install MOTOA4_Bootstrap_0408_1720-signed.apk
Then I opened up that app "System Recovery" and hit Install recovery, then I hit recovery mode from the app, and was told to connect the usb to the wall charger, not pc. And that was it for the first recovery. I then noticed that this specific recovery was missing some functions in the actual recovery so I installed 5.0.2.3 later.
I downloaded the .zip from the site and placed inside phone internal SD, the second link from OP here, turned on phone and went into Android recovery and it opened up the one I installed just a minute ago, and hit install zip from sdcard, I hit internal, and selected the .zip I downloaded from that site. I hit reboot recovery and it booted into that recovery, 5.0.2.3, the real one.
To go to this new one, I insert wall usb to phone and it boots in the first recovery, and I hit, reboot recovery, and it takes me to the new one.
NOW whenever I plug in usb to wall to charge, it boots in the old recovery, and I don't see charge symbol. I have calibrated my battery 3 times, and it is still CRAP (brand new 1800mah battery for mb860).
Anyways, I thought to ask here if I did a wipe data from the new recovery, or old, would it get rid of this whole mess?
Hmm ok.
I told you this before but here goes again. I'd give up on random guides from random sites. Everything you need is right here on this forum.
Not to mention, the recovery in that ZIP is slightly older, there is a newer one available.
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
The ZIP you downloaded seems fine, but it's somewhat likely your boot is also messed up too. If all this goes well, you can try finding the T-Mobile fruitcake (go over to the Atrix Reboot Project thread) and flashing it from the recovery. Be aware though that you might lose all data in doing this.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
ravilov said:
Here's what I'd do if I were you.
Do you have fastboot installed? If not, search for it on the forum for moto-fastboot, it's just one .exe file (no installation). Also make sure you have Motorola USB drivers installed.
Download RomRacer's recovery from here (I linked you this before btw). Make sure to select the IMG version, not the ZIP. Choose whatever color you want.
Place the downloaded IMG into the same folder where moto-fastboot is, and rename it into something simple, say recovery.img.
Power off your phone and power it back on while holding Vol(-), make sure it says Fastboot on the screen, then confirm with Vol(+).
Start the command prompt and go into the folder with moto-fastboot, then connect the phone with the computer and enter this command:
Code:
moto-fastboot flash recovery recovery.img
Done. Reboot with Power+Vol(-) but this time select Android recovery (use Vol(-) to move the selection). You should enter the newly installed recovery.
Once again, I told you all this before (not in as much detail though), hopefully this time you'll actually listen.
Click to expand...
Click to collapse
ALRIGHT thanks for this actual guide.
It installed fine, works fine, AND AGAIN whenever I plug the wall charger in when the phone is off, it boots into the OLD OLD recovery, from the first link.
I still can't see the battery.
Please stop throwing sass at me. :crying:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
ravilov said:
Sorry, sorry.
Anyway, I'm thinking your recovery is fine, but I think somewhere down the line your boot partition got messed up. That's why I said you should try installing the T-Mobile fruitcake. (Fruitcakes are ROMs just like any other but contain the pure untouched stock firmware.)
When my phone is off and I plug it in, I get the boot logo and then the full-screen battery appears, just like it should be. However I'm not sure what this depends on. I always thought this graphics is contained within the bootloader (and thus no amount of messing around with flashing can interfere), but I could be wrong...
Click to expand...
Click to collapse
I can only find this: http://forum.xda-developers.com/showthread.php?t=1163009
I downloaded the 2.3.6 ROM from the backup thread. Says nothing about T-mobile.So do I just install this from the new CWM?
Is there just no way of getting rid of CWM recovery so I can install it just once, rather than you keep telling me to install this and that?
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
ravilov said:
Wait, I'm confused. You want to get rid of CWM?
The point of my previous post was to make sure you have the latest RomRacer's CWM installed fully and properly. Now that you have it installed there is no need to install it again.
Not sure what's your final goal though...?
This is the thread for the Atrix Reboot Project: http://cleanimport.xda/index.php?threads/1805666/
I think the AT&T 2.3.6 ROM should work on T-Mobile too, but in all honesty, I'm not sure. I think it'd be best if someone else answers this part.
Click to expand...
Click to collapse
YES!!! Because everytime I connect the damn charger it boots cwm. AND EVERYTIME I hit ANDROID RECOVERY I boot into the OLD OLD OLD OLD Recovery.
why is that hard to understand? I want to uninstall ALL the cwms, and install the one you sent me just to have that one, rather having 3 different cwms I have right now.
Also that thread is just a bunch of people talking about nothing really. HAS ABSOLUTELY nothing to do with T-mobile whatsoever.
I just want to make sure that this AT&T phone will still work with my t mobile sim card after I install ROMs!!!!
---
And for the love of all that is holy, don't reply with: "why won't it?"
BECAUSE THAT IS WHY I AM ASKING. I have never done this, that is why I ASK!!!!!
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
ravilov said:
It is hard to understand because I don't know how is it even possible to have multiple recoveries installed.
At this point I would suggest you just go ahead and install the 2.3.6 fruitcake you downloaded. Make sure to boot into the CWM you just installed. (Man, even this last sentence feels weird... More than one recovery?!)
Click to expand...
Click to collapse
SO there is NO WAY to remove CWM recoveries?????
LOL THIS IS FUNNY! Now when I plug charger in, it just boots into OS, and when I hit android recovery with VOL buttons, it shows the white triangle.
Still don't get what that rom did. Installed it, and nothing, except for losing all my data.
This forum made things worse.
Thank you.
EDIT: OKAY NOW it shows the battery when plugged in but still the white triangle crap in the recovery.
You must have SOME recovery. You can install TWRP if you like that better, but you must have SOMETHING. By following the procedure I described you properly installed RomRacer's CWM so that part is fine. Now, why are you still sometimes getting the stock 4-option recovery - only heaven knows.
I don't think there's a way to install the stock Motorola recovery other than installing the full SBF, however SBFs are VERY dangerous and nobody is going to recommend that.
I really can't imagine what you've done with your phone. The mere fact you have multiple recoveries raises a big red flag right there. I tried to help the best way I can, but since obviously it's not doing much good, I'm going to refrain from further comments and let someone else take over. Good luck.
Ravilov has said it all but its pretty spread out trying to figure out what happened so I'm hoping I can tie it all together.
If you attempt to boot into recovery and get the old android recovery but booting normally puts you into CWM Recovery then somehow you have flashed the BOOT partition with CWM image. To fix this just download the correct fruitcake and flash the BOOT.IMG to the BOOT partition using the moto-fastboot tool and reboot. I would recommend erasing the BOOT partition first just in case.
Sent from my Nexus 7 using xda app-developers app
Thanks for your patience and help Ravilov
Sent from my MB860 using xda app-developers app
Hi,
I have a samsung S3 and I want to update it to lollipop or above as my nexus 5 has started randomly rebooting and I need a phone to use whilst I sort a replacement.
I have been following this guide: wccftech.com/install-aosp-android-5-1-1-lollipop-on-galaxy-s3/ as I'm a bit of a noob when it comes to this custom rom business.
I have rooted the device and installed clockworkmod recovery v6.0.1.2. and copied over the rom and the gapps file to my phone.
I then booted into recovery mode and made a backup of the current setup.
I then did the factory reset and the cache wipe(s) and installed the new zip for lollipop and then the gapps.
This is where I received an error "E: Error in /sdcard/0/0/0/Download/gapps-lp-20150314.zip (status 7) installation aborted".
I figured that I should restore to my backup now but when I press it, the app says that files can't be found.
I can see that the files that I backed up do exist but they appear to have been dumped inside a new directory called /0/0/0 (I think this has got three levels because I've tried this a few times).
Now I can't boot into an OS to get any other roms on the phone and I can't edit the files on there (I googled and saw a possible fix for the gapp status 7) and I can't get clockworkmod to recognise an external SD card so I can copy over a new rom or file to try (I have googled and it's suggested the FAT32 is the format for this phone and my size of SD card (16GB)).
Can anyone offer me some advice on how to get out of this situation?
Thanks
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Don't use cwm as it is an outdated recovery. Use twrp instead.
Sgt.Mindfudge said:
Sounds like you're at a place where you should start exploring using your computer instead of a recovery in order to fix your system.
I recommend using the PC software Odin and installing a stock ROM of your device. (Or perhaps using fastboot)
There's plenty of guides on how to use Odin both here on XDA and on the rest of the internet if you just look around a bit
EDIT: This link contains a (possible) fix for your problem.
http://forum.xda-developers.com/showthread.php?t=2522762
Click to expand...
Click to collapse
I had a look at the link you suggested and it's one of the suggestions that had come up whilst I was googling for a fix. Unfortunately, I don't have any way to get the updated script onto the phone as the phone isn't picked up by my pc whilst it's in this state, and I can't get the recovery tool to recognise the sd card so I can't put it on there either.
I'll take a look at the stock rom or fastboot option and see if I can get back into the phone. Maybe then I can apply the fix in the suggested post.
Thanks
audit13 said:
Don't use cwm as it is an outdated recovery. Use twrp instead.
Click to expand...
Click to collapse
I'll see if I can install twrp through odin.
Thanks for your help
If the phone works in download mode, try to flash a stock rom too.
Update - fixed
Hi all, just wanted to let you know that I fixed the device with the combined advice from here:
I installed TWRP after holding the volume down + power + home buttons and then pressing volume up when the message appears (I can't remember what this mode is called). I then flashed the device with the TWRP image.
After this I rebooted into the TWRP recovery mode (Volume up + home + power and then release power button when the samsung logo appears).
At this point, the device appeared on my windows machine so I could upload a new image to the internal memory.
I decided to copy on CM13 and GApps.
I then wiped the cache, system, data, and davik cache using TWRP, then I installed CM13 and GApps.
After a reboot the device came back up as a new install.
Hopefully that information may be useful to somebody.
Thanks for all your help
Phone: LG Aristo MS210 (Metro PCS)
Bootloader: TWRP 3.0.3.0
So let me explain. I was just figuring out how to root the LG Aristo since I had never done it with a custom ROM. Yes, true story. Anyway, I was happy I got it working perfectly until I rebooted my phone. When I rebooted it, SuperSU was gone. I tried going to the play store and redownloading it, but I got an error code -504, and the thing is, I couldn't download any apps. ANY. I decided to look the error code up and I can't find anything on it. I tried multiple times doing multiple different things. From factory resetting, reflashing SuperSU, to factory resetting and then flashing SuperSU, wiping dalvik-cache along with everything except for system. It didn't work and I thought I could get it working.. Well... this next part I really messed up on. I decided to wipe everything. I selected all options and slid the cursor and it failed. The wipe failed. It said "E: /sdcard1 unable to partition" or something like that. I noticed that when I was wiping earlier the internal storage was also called that, and the funny thing is I have no microSD card in my phone. So. :/
Now when I boot I'm stuck on the LG splash screen and nothing else happens. I tried recovery mode (without ADB) with the power button + vol down key as I read here: (I'd post link but I'm a new member) that's how you get into recovery/factory reset. I'd use ADB to get into recovery, but since I just wiped the system, I don't have USB debugging enabled. I tried anyway and I gotta say this is my worst nightmare as I'm too young to get a job, (15 yrs. old) so I can't get a phone. :/ Oh, and if this can be useful: I know it connects to my PC over USB because I hear the sound it makes when a new device is connected. Is there any way I can use that to unbrick it?
EDIT 9/10/2017 9:31 PM (Eastern Time): I managed to get into twrp. I'm currently looking online for how to flash android 7.0 nougat (OS it originally had)
RyokoOnXDA said:
Phone: LG Aristo MS210 (Metro PCS)
Bootloader: TWRP 3.0.3.0
So let me explain. I was just figuring out how to root the LG Aristo since I had never done it with a custom ROM. Yes, true story. Anyway, I was happy I got it working perfectly until I rebooted my phone. When I rebooted it, SuperSU was gone. I tried going to the play store and redownloading it, but I got an error code -504, and the thing is, I couldn't download any apps. ANY. I decided to look the error code up and I can't find anything on it. I tried multiple times doing multiple different things. From factory resetting, reflashing SuperSU, to factory resetting and then flashing SuperSU, wiping dalvik-cache along with everything except for system. It didn't work and I thought I could get it working.. Well... this next part I really messed up on. I decided to wipe everything. I selected all options and slid the cursor and it failed. The wipe failed. It said "E: /sdcard1 unable to partition" or something like that. I noticed that when I was wiping earlier the internal storage was also called that, and the funny thing is I have no microSD card in my phone. So. :/
Now when I boot I'm stuck on the LG splash screen and nothing else happens. I tried recovery mode (without ADB) with the power button + vol down key as I read here: (I'd post link but I'm a new member) that's how you get into recovery/factory reset. I'd use ADB to get into recovery, but since I just wiped the system, I don't have USB debugging enabled. I tried anyway and I gotta say this is my worst nightmare as I'm too young to get a job, (15 yrs. old) so I can't get a phone. :/ Oh, and if this can be useful: I know it connects to my PC over USB because I hear the sound it makes when a new device is connected. Is there any way I can use that to unbrick it?
EDIT 9/10/2017 9:31 PM: I managed to get into twrp. I'm currently looking online for how to flash android 7.0 nougat (OS it originally had)
Click to expand...
Click to collapse
Hi,
Well the only way to fix this is that u need to be able to boot into recovery.
If u tried booting into recovery by holding the power and vol+/- and u end up booting to the boot logo, then recovery is also wiped.
In this case, u will need to check if u have access to fastboot. If so then obtain the twrp recovery for ur device and flash it then tried booting into recovery using the appropriate keys.
When I get time, I will research ur device for any recovery tool and stuff.
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Hi,
Well the only way to fix this is that u need to be able to boot into recovery.
If u tried booting into recovery by holding the power and vol+/- and u end up booting to the boot logo, then recovery is also wiped.
In this case, u will need to check if u have access to fastboot. If so then obtain the twrp recovery for ur device and flash it then tried booting into recovery using the appropriate keys.
When I get time, I will research ur device for any recovery tool and stuff.
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
I managed to get into recovery. I don't know how to flash Android 7.0 for my Aristo, though.. so I'm researching it.
EDIT: Got a ROM flashed. Everything working now.
please help me this is between live and death. I bought a coolpad 8715 but the android version doesn't work with Playstore and everything about it is in Chinese, I try to change the language to English but the apps are still written in China. please how can I install another OS on it that support Playstore. I downloaded the firmware ( 8715_4.4.016.P1.8715.CPB ) which is in CPB format and i try to extract it to change application and some settings, after extraction I found some files but I don't know which one to edit or how to. The help I needed is that, how to edit my firmware .....CPB file after extraction and pack it back as .......CPB file so that I can use it to flash my coolpad 8715. Or is their any OS or ROM I can use like KitKat, lollipop, marshmallow miui etc. I try to update the phone with wireless hotspot, not working. I also try to install KitKat 4.4.2 Custom ROM through the phone recovery mode which is in China, but showing verification failed and signature error. please help me what can I do, am ready to take any ricks.
King smus said:
please help me this is between live and death. I bought a coolpad 8715 but the android version doesn't work with Playstore and everything about it is in Chinese, I try to change the language to English but the apps are still written in China. please how can I install another OS on it that support Playstore. I downloaded the firmware ( 8715_4.4.016.P1.8715.CPB ) which is in CPB format and i try to extract it to change application and some settings, after extraction I found some files but I don't know which one to edit or how to. The help I needed is that, how to edit my firmware .....CPB file after extraction and pack it back as .......CPB file so that I can use it to flash my coolpad 8715. Or is their any OS or ROM I can use like KitKat, lollipop, marshmallow miui etc. I try to update the phone with wireless hotspot, not working. I also try to install KitKat 4.4.2 Custom ROM through the phone recovery mode which is in China, but showing verification failed and signature error. please help me what can I do, am ready to take any ricks.
Click to expand...
Click to collapse
Sent from my LGE LM-X220 using XDA Labs
hello guys my device is a lg v30 tmobile and i had lineage os installed i wanted to flashed it again with different gapps but now when trying to flash rom again it says that my device is not a v30 and if i try to boot or turn off my phone it just boots back into twrp any solution for that im pretty much stock in twrp
el.quechon said:
hello guys my device is a lg v30 tmobile and i had lineage os installed i wanted to flashed it again with different gapps but now when trying to flash rom again it says that my device is not a v30 and if i try to boot or turn off my phone it just boots back into twrp any solution for that im pretty much stock in twrp
Click to expand...
Click to collapse
You may have to LG UP and start over, also you can try one of the stock based roms.
Ainz_Ooal_Gown said:
You may have to LG UP and start over, also you can try one of the stock based roms.
Click to expand...
Click to collapse
how can i get in download mode everytime i try to power off it just reboots to twrp
el.quechon said:
how can i get in download mode everytime i try to power off it just reboots to twrp
Click to expand...
Click to collapse
There should be a option under reboot to just shut off does it try to reboot if you click that?
Ainz_Ooal_Gown said:
There should be a option under reboot to just shut off does it try to reboot if you click that?
Click to expand...
Click to collapse
yes and every options of twrp asks me if i want to install twrp app which is weird
So connecting usb cable, force resetting it, press combo for download mode (volume up + usb cable ?)
doesn't work ?
Or at least fastboot mode ?
connecting usb cable, force resetting it (vol down + power), press combo for fastboot mode (volume down + usb cable)
zacharias.maladroit said:
So connecting usb cable, force resetting it, press combo for download mode (volume up + usb cable ?)
doesn't work ?
Or at least fastboot mode ?
connecting usb cable, force resetting it (vol down + power), press combo for fastboot mode (volume down + usb cable)
Click to expand...
Click to collapse
ill try letting it reboot with the usb cable and see what happens
when twrp reboots it doenst even show the lg v30 screen it just shows a black screen for half a second then it goet straight to twrp
edit: i restored a stock backup and nothing is there a solution that can be done from twrp terminal
el.quechon said:
hello guys my device is a lg v30 tmobile and i had lineage os installed i wanted to flashed it again with different gapps but now when trying to flash rom again it says that my device is not a v30 and if i try to boot or turn off my phone it just boots back into twrp any solution for that im pretty much stock in twrp
Click to expand...
Click to collapse
that's the important part, I don't really know how much the t-mobile models differ from the H930 ones
but there should be fastboot ? download mode ? "factory reset" functionality (via button dance botting into TWRP) ?
el.quechon said:
hello guys my device is a lg v30 tmobile and i had lineage os installed i wanted to flashed it again with different gapps but now when trying to flash rom again it says that my device is not a v30 and if i try to boot or turn off my phone it just boots back into twrp any solution for that im pretty much stock in twrp
Click to expand...
Click to collapse
You might have done what I did which is flash twrp.img in recovery.. it won't go back to initial password screen. I did that and had the same issues.. I recently did it.. now it only restores backups which is how I got lineage or other rooms back.. after wiping the system partition, it also only flashes stock debloated room, but anything else I flash crash system partition.. I'm going to start over but with treble recovery in root process and just avoid messing with it..
lowkeyst4tus said:
You might have done what I did which is flash twrp.img in recovery.. it won't go back to initial password screen. I did that and had the same issues.. I recently did it.. now it only restores backups which is how I got lineage or other rooms back.. after wiping the system partition, it also only flashes stock debloated room, but anything else I flash crash system partition.. I'm going to start over but with treble recovery in root process and just avoid messing with it..
Click to expand...
Click to collapse
i didnt flash recovery i was flashing the custom rom but if i restore a stock rom back up it doesnt work either
el.quechon said:
i didnt flash recovery i was flashing the custom rom but if i restore a stock rom back up it doesnt work either
Click to expand...
Click to collapse
Did you restores the recovery as well? I did that which is suspect source of the problem number 2.. even flashing magisk crash my system partition.. but not the magisk in the stock room, probably cause it's built in.. or any restores.. either way I'm going to start over.. not touching recovery after root & not backing up recovery partition to confirm a few things.. can you flash debloated rom after formatting system partition? Aroma gapps don't work for me but other gapps does.. I found out the hard way cause I didn't see any information on it in the threads.. I read it's a common issue with TWRP recovery on multiple devices..
lowkeyst4tus said:
Did you restores the recovery as well? I did that which is suspect source of the problem number 2.. even flashing magisk crash my system partition.. but not the magisk in the stock room, probably cause it's built in.. or any restores.. either way I'm going to start over.. not touching recovery after root & not backing up recovery partition to confirm a few things.. can you flash debloated rom after formatting system partition? Aroma gapps don't work for me but other gapps does.. I found out the hard way cause I didn't see any information on it in the threads.. I read it's a common issue with TWRP recovery on multiple devices..
Click to expand...
Click to collapse
Got it working luckily my phone was almost dead so once it died tarp started working fine so now everything is normal
el.quechon said:
when twrp reboots it doenst even show the lg v30 screen it just shows a black screen for half a second then it goet straight to twrp
edit: i restored a stock backup and nothing is there a solution that can be done from twrp terminal
Click to expand...
Click to collapse
I had that once when i tried to flash the aroma gapps for pie ?
that kinda ****ed up TWRP, a force reset (vol- + power) did the job for me, as all the reboot/shutdown options in TWRP didnt wanna work.
SGCMarkus said:
I had that once when i tried to flash the aroma gapps for pie ?
that kinda ****ed up TWRP, a force reset (vol- + power) did the job for me, as all the reboot/shutdown options in TWRP didnt wanna work.
Click to expand...
Click to collapse
Exactly what happens to me try the aroma installer from gapps project and everything went down hill now I flashed the stock one they have.
How can I delete Google apps installed by gapps without making other Google apps crash
Did you not have a backup of your rom using twrp before you made the change? Isn't that the whole point of having twrp and a phone with SD card? Always backup your whole phone before making a change. It has saved my phone many times.
Alibaba0101 said:
Did you not have a backup of your rom using twrp before you made the change? Isn't that the whole point of having twrp and a phone with SD card? Always backup your whole phone before making a change. It has saved my phone many times.
Click to expand...
Click to collapse
Yes I had a back up but it was twrp acting up by not being able to boot.
My phone was just booting back to twrp even when pressing power off some how by finally powering off the device (letting it discharge all the way) that was the only thing that fix it me twrp started working fine after that
My twrp has been acting funny/unpredictable. Or I am not doing something right. Mostly has to do with the restore function. I generally have two separate roms backed up in restore. But, lately, I will see only one listed. When I get back to the phone and check in my root manager, I will see them both listed. And then later, it (Rom) "might or might not" return to the restore function area.
But, lately it seems that when I restore the system, I can not open it up in the lock screen (does not recognize the pin). I have to turn the phone off, then use the vol down and power button to get back into twrp. Luckily, I have a couple of roms downloaded in the install section which then does let me flash and reboot, but I have to start new/over.
I don't know if reflashing twrp in recovery will help or not (have never done it).
I'm afraid one of these times I will some how get locked out or not be able to flash a good rom.
gimpy1 said:
My twrp has been acting funny/unpredictable. Or I am not doing something right. Mostly has to do with the restore function. I generally have two separate roms backed up in restore. But, lately, I will see only one listed. When I get back to the phone and check in my root manager, I will see them both listed. And then later, it (Rom) "might or might not" return to the restore function area.
But, lately it seems that when I restore the system, I can not open it up in the lock screen (does not recognize the pin). I have to turn the phone off, then use the vol down and power button to get back into twrp. Luckily, I have a couple of roms downloaded in the install section which then does let me flash and reboot, but I have to start new/over.
I don't know if reflashing twrp in recovery will help or not (have never done it).
I'm afraid one of these times I will some how get locked out or not be able to flash a good rom.
Click to expand...
Click to collapse
when it doesnt recognize your pin, go (in twrp file manager) to /data/system/ and delete the locksettings.db(-sh/-wal) files...
I think that was the path, you can google that too ^^
Thx, SGCMarkus, I did delete just the one db only file. It did away with the pin unlock code on reboot (but I did not do a restore, just a reboot back into my system), so I assume it will work. I will try it when I have time. I think that deletion has to be done everytime in twrp, because the line does reappear the next time I booted back into twrp?
Thx.