Related
I took a bunch of backups before hand, but I put them on my laptop, so they're not on my phone. I've tried connecting my phone to my laptop, but I can't access the filesystem of my phone through my laptop. I can, however, boot my phone into TWRP recovery through a .bat file on my computer. The only thing I've managed to be able to do from there is wipe the phone and flash stuff. The only thing I've got on my phone that's useful is two .zips, the PA 4.4 zip and the Gapps that follow. As far as I can tell, the only thing I need to do to get my phone working again is to get my backup files back onto my phone somehow, but I cannot seem to get that working.
I've tried the ADB push command, but it can't detect my phone, so that's not working.
I'm wondering why the .bat works, as I can tell by the log that it is sending files to my phone! Somehow it manages to do it, but I cannot send my own files. Why is that? Also, looking at the log from previous times, It sent the files with speeds of several MB/s, but now it's only sending them at like 100-200KB/s. Is my SD card damaged?
I've read through a bunch of guides, and several of them states that the stuck boot animation is caused by the cache, so I tried wiping that. However, for some reason, it's begun to say "Error: Operation failed" when trying to wipe it again.
Help please
## Fixed it.
Could you post the .bat file that you used? Sorry if its a bit off topic but you are the only person that I can find with a similar problem as me and I have my phone stuck in the boot animation. I can't get my phone into recovery mode and was hoping that your .bat file could help me. I have a back up in twrp that I could use.
Okay, so I have a Samsung Galaxy S 5, specifically the SM-G900H.
I rooted it some months ago and yesterday wanted to use the Screen Mirroring, so I found that you could get that function back by adding a line to the build.prop file.
Did that using this build.prop editor in F-droid.
It worked, but it also gave me a 2048 resolution and tablet layout (odd, I just added the key "wlan.wfd.hdcp" with the value "disable"), since I saw it stated that it had made a backup I chose to use the "restore" option and then boot. I'm not sure if it restored the wrong file or what but now after the first splash screen I get a black screen.
I went into Recovery Mode (Home+Power+VolumeUp) and tried to do adb from there but I only see the phone as "Host" and adb gives me an "error: closed" message whenever I try to do anything else than adb devices. If I try this without going into recovery mode I see the device as "offline".
So giving up hope to do this smartly by fixing the build.prop I tried a data wipe from recovery mode, the error persists but now I get stuck hearing the second splash screen's sound over and over again.
If I start ODIN mode I can see the device and flash (?) the auto-root found here without problem.
So, what do you recommend I do at this point? is there any way to edit the build.prop file with either ODIN or recovery mode's adb sideload?.
Or should I just flash a new ROM? I downloaded Cyanogenmod but I'd rather keep using stock for now. Where can I find the latest stock rom?.
Sorry if this has been solved elsewhere, I've looked and tried a bunch of them... there's a lot of noise out there.
update (making progress)
In case anybody wants to chime in (or this helps anyone else in the future)
I think I made some progress but the phone is not functional yet.
I flashed the TWRP found here:
http://forum.xda-developers.com/galaxy-s5/development/rom-kian-rom-bog6-t3187812
and went into recovery mode with that.
I did a backup, although I'm not certain what it backed up and where because neither the free space it needed nor the used space I had match up very much with that... a bit worried.
Then I mounted the /system and saw that there was no build.prop but only the build.prop.bak so I renamed that to build.prop and now I can see the second splash screen and don't hear it (I think this is because I might have had the volume down before) and it gets stuck there.
But hey, now I can edit the build.prop and maybe backup my files (mostly the chat logs and pictures) into the SD card. Will see what happens... I'll try to remember to come back and update.
build.prop.bak is the original it backed up when you edited it, it saves a new copy
Just rename to build.prop and reboot
*Detection* said:
build.prop.bak is the original it backed up when you edited it, it saves a new copy
Just rename to build.prop and reboot
Click to expand...
Click to collapse
hmmm Detection I did that at some point and it didn't seem to work, but it could have been that I didn't wait long enough.
After several more changes it worked (although my phone is still in tablet mode and I lost all my personal data).
CAUTION TO NOT LOOSE TWRP
I read two posts that say v21, now again on V8.5, put the stock recovery back instead of twrp. This is probably a side effect of a fresh stock /system and wipe of /data.
As a preventive step, when done flashing and wiping reboot to recovery FIRST, before booting the system It will allow recovery to handle removing the recovery-from-boot.p that flashes stock recovery.
I just patched the modified V7.4.2 up to the newly released 8.3 now 8.4. 8.5, 8.7,9.0 -V9.2 Patch
New update has been made from V17 to V21 of the non prime version of R1-HD, Non prime is behind on security patch (2017-05-05)
Copied ROM from phone and made twrp install ROM from it.
* No preloader change (official updates change the preloader to block your ability to use sp flash tools for rom flashing)
* No lk.bin change __ this part is what allows you to choose boot options(boot menu when power and volume pressed together)
* No "FOTA" app Fota has now been left in to make it easier to get next update, if that ever happens.
* No opera browser
* No adds (removed in the modified 7.4.2)
* Custom boot logo (only done on v8.3, there was no interest in this so abandoned)
--Newer versions of rom left stock, Leaving mods up to user.
** while it is not necessary to do a wipe with this ROM, I still recommend it.
**Thanks:
** @vampirefo needed his patched v7.4.2 in order to apply this new 8.3 patch and again for 8.4
** @ColtonDRG OR @jasonmerc I do not remember which one made it: For the image used in the custom logo
and the modified zip is here .
Roms are rootable with SuperSU, flashed in twrp after install. Must be done in systemless mode. In order to patch system veridy in boot.img
Logo update did not work on original rom changing link to updated version
BLU rolled v8.3 back to v7.4.2 because of app compatability issues. V8.4 is there fixed release. Both 8.3 and 8.4 are modified prime roms with ads stripped
V21 is the non prime update.
Unmodified V6.1
==>NON-ROOTED-logo-not-replaced-modified-V8.3
==>Fixed Logo modified NON_ROOTED V8.3
==>>modified V8.4
==>>modified V8.5
==>>Full with Ads V8.7
==>>Full with Ads V9.0
==>>Patch For V9.2 must be flashed on top of fresh V9.0
****Run debloat ==>script to remove ads if you need/ want to, or remove from zip before flashing ****
alt. manual example: before reboot, while still in twrp. Select mount and put checkmark next to system. Then run these two commands in adb terminal
Code:
adb shell rm /system/priv-app/com.amazon.*/com.amazon.*.apk
adb shell rm /system/app/Adups*/*.apk
==>>Modified V21
** stand alone logo installs
I flashed this but I didn't get the custom boot logo.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
I had that happen to my second phone too.
I don't have an explanation yet.
I even made a separate update.zip , that one didn't make the logo change either. I did eventually change it with sp flash tool.
I tried with both recoveries.
and multiple /dev location formats. and for whatever reason my one phone did not accept the logo change from recovery.
And the other test phone it worked.
mendelgordon said:
I flashed this but I didn't get the custom boot logo.
Click to expand...
Click to collapse
Neither did I but it all seems to be working fine
Been using this for about a day now, likewise no custom boot logo, but that's fine. Otherwise, it's been running super well. A lot better than the previous mostly stock version did for me with the bloatware APKs removed after the install. A lot of the general idiosyncrasies of the previous version of the stock rom seem to have gone away for me. It seemed to have weird storage management issues, errors moving to SD, broken symlinks that prevent apps from moving or being reinstalled, and a lot of other little non-storage issues, but so far, none off that here.
Long story short, good work! I hope we eventually see proper 7.x roms through some of the efforts going on, but in the meanwhile, your work here has made life a little bit better on 6.
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
**logo-update is same as composite but with alt updater-binary
**composite-logo screenshot is in op
**stock logo will return to original BLU logo
mrmazak said:
It seems that I was able to get the logo.bin to update when I applied the original update patch, but not when I used the same line in the rom install.
It is no big deal that it did not work, I was just trying to make it look different at boot time.
edit:
I think i found the problem with the logo not updating.
i used the update-binary from the official patch update. (the one that allowed the logo to change the first time)
and it changes . so since the ROM seems to install the way it is , only the logo didn't flash I put it in a separate update.zip if anyone is interested in it.
EDIT 2:
clarification.
It was not so much the binary allowing the logo to change but the format of the partition location I had been using that needed that binary.
Further test had shown me that I could have used the binary I was using but just change the partition naming line
Code:
package_extract_file("logo.bin", "/dev/block/mmcblk0p9")
the above code works with the same update-binary as rom install
But I was using
Code:
package_extract_file("logo.bin", "/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/logo")
Taken straight from the official patch, and thats why it needed the update-binary also.
I dont know what is different in the binary other than , major size difference.
The powered by me logo was just a test file to see changes in the logo.
Click to expand...
Click to collapse
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Serenitybs said:
Hahaha the scribbled "ME" is hilarious. Your work is awesome, I don't think anyone using this rom will have an issue with the boot image but thanks for being so helpful and explaining.
P. S. Do you have any plans with the Nougat update?
Click to expand...
Click to collapse
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
Somebody already tried this out
linuxsociety said:
Nougat is going to take a full build from scratch. We don't have 100% identical hardware with any other nougat device to my knowledge. We might have the same MTK chipset, but there are several other differences. All we really need is an official device overlay and the vendor files released by BLU themselves. We can then apply those to the latest Lineage or AOSP (I prefer AOSP myself) and build. Then the only problem we'll run into is anything that has changed in 7.x that isn't compatible with our kernel we use in 6.0. It'd be a slight chance our current kernel would work without some patches on 7.x We can't even get our official sources for anything else, so I'm almost certain we'll not find any patches to for the kernel to work properly with Nougat, at least not from BLU or any similar devices. None The less Nougat has been well thought of, and we have been trying to debug issues with a broken Port. But a broken port from a different device is just that - Broken. We need a team of knowledgeable devs to build Nougat + Kernel from scratch and then we'll have it working. I can't do it alone with the old computer I have, the R1HD would be long forgot of by the time I got Android Compiled haha.
Mr. Mazak I flashed your rom it went smooth, I was hoping the newest update was for 6.0.1. But I didn't lose any functionality, hopefully on my Cricket Service this update has patched some things to the radio device that will retain connection more steadily. I experienced a lot of coming and going with the 7.4.2 rom. None The Less you did a good job with this update Mr. My suggestion is find the same MTK chipset with a fully working 7.x rom and just port the /System but keep all our libs and inits from this release just for a test starter. And don't replace the camera app thats in AOSP 7.x. )
Click to expand...
Click to collapse
It was just wishful thinking. I have no idea how all of this is done. All I know is @mrmazak has helped me to fall in love with my phone again with this V8.3. The 7.4.2 did seem a bit buggy for my phone but this update works beautifully and I didn't even root it. If this remains true I will be happy with this phone for awhile even on 6.0
Really confused right now.
I was browsing through the settings menus. And found in the Settings-security- menu a toggle labeled "quick boot" ( not to be confused with "fastboot") . I enabled it then rebooted to see if it booted quicker. Didn't seem to make much if any difference. So I went back to turn it back off. And it wasn't there. I checked in my other phone , it wasn't there on that one either.
Did any body see this menu item, and if so where is is it?
Edit 1:
Few more power off , power on cycles to compare times. With other phone and defiantly seems to have turned on some faster boot option.
This phone goes from off to on in 5-6 seconds other phone takes about 20.
Edit 2:
OK , I panicked for a minute.
Couldn't find the setting and thought that it was another way to block sp flash tool by preventing you from ever being fully powered off.
But the setting was in accessibility not security.
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
detroitredwings said:
Mrmazak, first of all, thanks for the ROM, installed it yesterday. But I have a problem with SELinuxModeChanger app. First, I'm getting a security warning when installing it, then - when running it. And another message, with this app running - "can't obtain root", although SuperSU shows its status with green #, like every other app it gives root privileges to. On my other Prime phone, running 6.1 out of the box stock ROM, FM radio works just fine with SELinuxModeChanger app behaving flawlessly (no security warnings whatsoever). Any ideas?
Click to expand...
Click to collapse
The mode changer app is technically a security issue. I did have that warning a few times when using mode changer app from the XDA thread of the developer, then when I used the app downloaded from f-droid it worked with systemless root and didn't give the security warning.
The app downloaded from f-droid worked for me as well, many thanks!
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Letitride said:
Big thanks for getting this out, updated from previous debloated, rooted version to this modified 8.3 stock rom, rooted with SU v2.79 SR3, all is good - only App that won't show up nor install, even tried the ones off APK Mirror site - is my Dunkin Donuts App, LOL. Play Store now said it's not compatible and the APK started to install then failed - any ideas or suggestions on what to do ??
Otherwise, it's all good - I will survive without DD App, just run that from another device when I need my caffeine fix.
Click to expand...
Click to collapse
I also had an app that previously work, say is not compatible now.
Maybe has to do with apps that have links to pay accounts. And that has something to do with trustzone. (Tee1 & tee2)
Those sections I left out of the update. I will add it back in and test. Update when I do. It is also possible this problem is why Blu rolled back there update.
**EDIT**
well that didn't go well at all.
I flashed the new trustzone.bin files from the official update. Now phone no longer turns on and no longer connects to flash tool
**EDIT 2**
After much persistence and many failed attempts to get phone recognized in pc again. Finnaly got to a point that phone was cycling between "preloader" driver and "usb serial device", and with careful timing was able to start sp flash tool at just right time and the flashing back to original trustzone files seems to have recovered phone.
for the record i am not sure what steps made it work. But I was shifting back and forth between leaving phone sit on charge, then on charge with rubber band wrapped around power button, then not plugged in , and not plugged in with rubber band on power button.
Okay... persistence is key in customization, i guess! I am getting somewhere here!
mrmazak said:
The first link is needed to get phone unlocked so you can install twrp.
Click to expand...
Click to collapse
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
OldSkewler said:
Okay... persistence is key in customization, i guess! I am getting somewhere here!
Finally got thru the steps in order (1-2-3-4) then Step (5) and sub-step 1. I can also boot to TWRP.
Now this brings me to this thread, 8.3 Stock ROM. The thread assumes one knows how to install it and I suspect this could be as easy as uploading it to a folder in the phone then booting to TWRP and INSTALLING the ZIP file? Could someone clarify the steps to install this 8.3 ROM?
Thanks!
Click to expand...
Click to collapse
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Many ways to do that.
Easiest is to copy to phone while phone is connected to PC.
Cam also download file from internet with your phone.
Bottom line is get zip file to the phone boot to recovery and install
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
mrmazak said:
Yes. You are correct
Either put the zip file on external sd card , put card into phone boot into recovery mode and install , or put file directly onto phone .
Easiest is to copy to phone while phone is connected to PC.
Bottom line is get zip file to the phone boot to recovery and install
Click to expand...
Click to collapse
Right on man! I am officially running 8.3 ROM with April 5th 2017 Security Patch Level! Geez.. it was not easy but I got this working!
MrMazak, I followed all your instructions on both links, so could you tell me what exactly I have on my phone? Is it rooted? Bootloader Unlocked? The phone seems to be working fine but I don't know what level of access I have. Honestly I don't even know exactly what the differences between all these terms are.
Also, do I have or not SU? One of the steps under the .bat I believe install it. How do I access it?
Thanks again!
---------- Post added at 10:19 PM ---------- Previous post was at 10:18 PM ----------
Weasel0 said:
Anyone else having wifi issues after upgrading? While watching videos it seems the internet cuts out. The phone says it's still connected but I have to turn wifi off and back on for anything to work. Could be my router also but it didn't seem to be doing this until I installed 8.3
Click to expand...
Click to collapse
My install is pretty fresh, couple of hours, but as far as I can tell all is working fine with Wifi, As a matter of fact this is a new device only connected with Wifi and no SIM Card.... internet works fine.
Here's my understanding of getting custom ROMS for your device by doing little to no work.
If SHARP isn't releasing the source code, can't we just go and flash a ported ROM zip?
First, you find a device with exactly the same specs as yours: Easiest way to do this is googling phones with the same processor.
https://www.kimovil.com/en/list-smartphones-by-processor/qualcomm-snapdragon-400-msm8926
Now, we press "Compare" and see if we can find a phone that has exactly the same camera and/or other components.
Let's assume that our cameras are going to work out-of-the-box, and sort it down.
https://forum.xda-developers.com/leon
Oh, lookie! A phone with pretty much exactly the same specs, and a community that is making/porting ROMS for it?
https://forum.xda-developers.com/leon/development/aosp-5-1-1-lg-leon-ms345-t3611883
Hey, an Android 5.0 ROM?
Now, knowing the information we know now. Can't we logically go into the (aosp-5-1-1-lg-leon.zip) and change around the MANIFEST values to make sure they point to the correct places? Can't we change around the configuration so it will install?
I don't know all too much about porting ROMS, but if it's as truly as easy as I'm explaining it, why haven't we done it yet?
(Feel free to correct me if I have any details wrong! I'm open to criticism!)
Quick Update:
To begin porting other ROMs, I am compiling an actual flashable ZIP (Stock ROM Image) to use as a base for the other images. I am getting my sources from here: http://www.sharpusa.com/Home/CustomerSupport/SharpCareCenter/MobileSupport/OpenSourceCode.aspx
And compiling them using AnyKernel. I will post flashable ROM.zip here when I am done.
updates
Rhioun said:
Quick Update:
To begin porting other ROMs, I am compiling an actual flashable ZIP (Stock ROM Image) to use as a base for the other images. I will post flashable ROM.zip here when I am done.
Click to expand...
Click to collapse
any progress?
Yes, I managed to make a flashable Aquos Sharp zip, based off Kernel Version S4081.
Currently, I'm attempting to get a ported ROM over.
I'll post the flashable Stock ROM though:
https://drive.google.com/file/d/0B0Fuy6MV4s8RU0NUMzRvLVp5WjA/view?usp=sharing
hi thanks for all very good news
can i flash with 305sh factory unlocked and rooted ?
No, that is a ROM for the 306SH.
The 305SH files are on a Japanese version of the Sharp website.. the links on these forums somewhere.
I can't test 305SH files, since I only own a 306SH.
If you could find the links for the 305SH system.img and boot.img, I could compile a flash able ROM for you.
Else, search around for a TWRP backup for the 305SH that you could restore on your phone.
Rhioun said:
Yes, I managed to make a flashable Aquos Sharp zip, based off Kernel Version S4081.
Currently, I'm attempting to get a ported ROM over.
I'll post the flashable Stock ROM though:
https://drive.google.com/file/d/0B0Fuy6MV4s8RU0NUMzRvLVp5WjA/view?usp=sharing
Click to expand...
Click to collapse
Can you paste a few pictures? THX
This seems like a cool idea. I'm willing to help with some testing if I can catch up. I remember getting this phone a few years back and due its low popularity I never thought it would get rooted. Now that it is I am at a loss of what to do. (I think I may have messed up a few things during my previous attempts at rooting, I can no longer access my security tab and my phone no longer detects the sim card.)
Any tips on how to get it safely backed up? (not that it's in great shape) I tried the TWRP tool and that gave me the option to backup "recovery" and "boot" (not that I really know what those are). I am not sure if it's actually making the files or where I should be storing them or how I would recover from them. I can see the files with ES file explorer but not with windows.
I really need to figure out what I'm doing XD
A TWRP Backup is a nandroid backup, in essential, it took a backup of the whole partitions. The partitions include names that identify them, such as boot, recovery, cache, system, etc.
It is just asking you to restore what partitions you want from your nandroid backup.
Let's say, you updated to a new TWRP version, but it is buggy or something, and you wish to switch back. Simply click "Restore" and select only "recovery" and it should flash your nandroid backup of the recovery partition to your existing recovery partition, and you'll have your old TWRP again.
Since you messed a few things up already, I'd suggest you go with the full nandroid backup, leave everything selected, and click "Restore".
Hopefully you made the backup before you began fiddling too much with your phone!
Rhioun
Any progress at work?
I've tried porting multiple ROMs, looking for compatibility. I've had zero success in getting one to boot up. Either the device goes to a black screen after the primary Sharp Boot Logo, or it boots up TWRP immediately after the Sharp Logo.
I saw how another guy on these forums also made a flashable room for the Sharp Aquos Crystal using Superr's Android Kitchen, so I believe my next trial-and-error phase will lie there. However, before I do that, I plan to use his flashable ROM as a base to port other ROMs, and see if I have any more luck.
Maybe my flashable ROM was invalid somehow.
Anywho, I highly recommend anyone who's interested in porting ROMs for this phone to begin to do so. We have plenty of materials scattered about, and DuckDuckGo is your friend.
Don't hesitate to try.
Thanks, and I'll hopefully keep this thread updated about my progress.
I've working on an Android 5.1 RR ROM from the LG Leon. I've (so far) replaced a majority of firmware files and updated symlinks, dumped vendor files, replaced a few .ko files, edited the build.prop and updater-script, configured the fstab from the ramdisk, copied over the kernel built for the Sharp Aquos Crystal, and rebuilt the boot.img. I customized the updater-script to include chameleon.img, modem.img, and persist.img (partitions that assist with connecting to Sharp, and some kernel configurations).
This has been a lot of tweaking to the ROM, and I tested it and was thoroughly disappointed when my device began to bootloop. (Goes to Sharp 1st boot screen, and reboot, go to 1st boot screen, reboot, etc.). TWRP won't boot when this happens, and holding Volume Down+Power will yield nothing. You can't even power off the device, troubling because the battery is (nigh impossible to remove) not meant to be removed. No matter, although, holding Power Up+Power puts the device in fastboot more (the led will hold solid white) and from there you can successfully power off the device and start up TWRP. Luckily, I made a TWRP backup before I tried flashing the ROM, so I was able to restore back to that. However, I edited a good deal of things, so I just need to know what is causing the bootloop, or maybe then ROM, even ported, is simply incompatible with our Crystals.
I looked around, and found XDA Forums that promote the use of logcat to figure out why a device isn't booting. I am going to try this next, and if it yield nothing, I will find another phone to try porting a ROM from. (We have a good deal with the same processor, shouldn't be too hard.)
Sent from my Aquos Crystal
Still patiently waiting for a ROM. I'm still holding on to this device just because i have been watching this thread and i have hope it will have run custom ROM one day.
Geodripp said:
This seems like a cool idea. I'm willing to help with some testing if I can catch up. I remember getting this phone a few years back and due its low popularity I never thought it would get rooted. Now that it is I am at a loss of what to do. (I think I may have messed up a few things during my previous attempts at rooting, I can no longer access my security tab and my phone no longer detects the sim card.)
Any tips on how to get it safely backed up? (not that it's in great shape) I tried the TWRP tool and that gave me the option to backup "recovery" and "boot" (not that I really know what those are). I am not sure if it's actually making the files or where I should be storing them or how I would recover from them. I can see the files with ES file explorer but not with windows.
I really need to figure out what I'm doing XD
Click to expand...
Click to collapse
Sorry for my reply earlier, I skimmed your post and thought you were trying to RESTORE a backup since your phone was in such terrible condition.
Just to be clear, unless the 306SH gets a new recovery, there is usually no reason to backup "recovery" as that is just backing up your current TWRP.
(Usually used in case a new TWRP version is buggy and you want to restore back to your old one)
However, certainly backup boot as that contains all kernel files and ramdisk settings, and without it, the phone would not 'boot'.
Just backup everything. Leave everything checked. (Unless you're a stickler for space.)
I recently made a flashable Aquos Crystal Stock ROM (seems camera and data and everything work fine) with no carrier-specific apps installed.
I can supply you with that, or, if you'd prefer, I can make a TWRP backup of a factory default 306SH phone and send it your way,
for either of them, just put one on your SD Card and if TWRP Backup, press "restore" and select the backup I provided you with, or for flashable ROM, press "flash" and navigate to it.
There is really no difference between them.
However, some things to note if you do want me to supply you with a backup.
It has SUPERSU preset installed. (I can't change this. It made its way into about everything.) So, if you want to use apps like (Android Pay, Applike), you will have to open SuperSU, and click "UNRoot" and take it off.
I have fixed Kitkat 3rd Party SD Card write privileges, (bug in android 4), and that fix has also seemingly worked itself into my factory default as well. (No disadvantages to it, although..)
Both of these files will fix your issues and supply you with a factory default environment.
If you, or anyone else in this forum would like a factory default TWRP backup, or flashable zip, feel free to say so.
I'm at a standstill. I've gotten my hands on a niche version of CyanogenMod 11, and replacing some vital files, I got it to boot on Sharp Aquos Crystal.
However, files I replaced were apk's, system ui, libs, and breaks some (most) functionality of Cyan 11.
I need a boot log tool of sorts so I can replace files, do a boot log, figure out what is causing a boot loop, or forever boot, and fix it.
I looked online, and everyone is all about the logcat. However, I tried this and it says "waiting for device".
So the device does not reach booting adb daemon.
I need a tool that will save a boot log.txt to the SD card at boot, (I imagine init.rc ) so that I may debug the ROM and then use the working ROM (and logging tool) to port more recent ROMs.
Anyone know of any such logging facility/tool?
keep it up
Does anyone know of a boot debugging/logging tool? There must be one. Please reply to this forum or PM me about one, as I do need one.
It is vital to building a ROM, rather than stupidly copy-pasting and blind guessing playing at Roulette trying to get the ROM to work.
Please. I need one.
I used to do this a lot, but on a rooted phone with custom recovery. More afraid to futz around with Xiamoi's bootloader. The mtk updates are going from bad to worse, however. And still on Android 6.
I would take a known, good ROM. Unzip it. Edit and replace the build file with the options I wanted. Minimally, for this phone, change the mode to userdebug to get split screen.
Custom init.d scripts (not active on this device, I fear!).
I would manually delete bloatware. (HAD TO trim the ROM to get it to fit on the old dinosaur. Most everything had to be user-installed!)
Even insert system files.
Would then rezip and flash the ROM.
Anyone tried such on this phone? Should one dare?