Related
OK, so I successfully S-Off'd this phone using DirtyRacun. I backed up the stock functioning ROM, then went to flash Viperlte 2.2.0. Went through all the Aroma installer options, then went to flash. It breezed through the install process, leaving the phone without any operating system on it (Recovery didn't actually flash anything). Tried both CWM and TWRP, and same results each time.
So, I decided to simply try flashing the boot.img in the downloads for Viperlte 2.2.0 via fastboot, and after doing that, the phone still won't boot, and now whenenver I try to reboot into recovery, recovery flashes for a second, and then screen goes blank and boot loops.
Tried reflashing the stock boot.img and reflashed recoveries, same results each time. I'm at a loss. I don't understand what got messed up by fastboot flashing the boot img.
Any help is greatly appreciated!
Boostjunky said:
OK, so I successfully S-Off'd this phone using DirtyRacun. I backed up the stock functioning ROM, then went to flash Viperlte 2.2.0. Went through all the Aroma installer options, then went to flash. It breezed through the install process, leaving the phone without any operating system on it (Recovery didn't actually flash anything). Tried both CWM and TWRP, and same results each time.
So, I decided to simply try flashing the boot.img in the downloads for Viperlte 2.2.0 via fastboot, and after doing that, the phone still won't boot, and now whenenver I try to reboot into recovery, recovery flashes for a second, and then screen goes blank and boot loops.
Tried reflashing the stock boot.img and reflashed recoveries, same results each time. I'm at a loss. I don't understand what got messed up by fastboot flashing the boot img.
Any help is greatly appreciated!
Click to expand...
Click to collapse
how did you install recovery, the first time you must use adb and flash the recovery.img.
command is: fastboot flash recovery(what ever here).img example: fastboot flash recovery recovery-clockwork-touch-6.0.2.9-fireball.img
Ok, have the phone booting again (flashed ruu, then reflashed the dirtyracun hboot). Question still remains, why did I start bootlooping recovery after flashing the boot.img? And why wouldn't the Rom actually flash in recovery?
Again, any insight is appreciated.
Boostjunky said:
Ok, have the phone booting again (flashed ruu, then reflashed the dirtyracun hboot). Question still remains, why did I start bootlooping recovery after flashing the boot.img? And why wouldn't the Rom actually flash in recovery?
Again, any insight is appreciated.
Click to expand...
Click to collapse
flash the rom then the boot img then boot.
Aldo101t said:
how did you install recovery, the first time you must use adb and flash the recovery.img.
command is: fastboot flash recovery(what ever here).img example: fastboot flash recovery recovery-clockwork-touch-6.0.2.9-fireball.img
Click to expand...
Click to collapse
Yeah, did that. I was in recovery (TWRP) when I tried flashing Viperlte, but it never flashed the Rom after selecting all the options in Aroma. It stated that it did, but there's no way it did. It took less than a second to go from "installing" to "complete".
So, something is funky there.
Boostjunky said:
Yeah, did that. I was in recovery (TWRP) when I tried flashing Viperlte, but it never flashed the Rom after selecting all the options in Aroma. It stated that it did, but there's no way it did. It took less than a second to go from "installing" to "complete".
So, something is funky there.
Click to expand...
Click to collapse
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
also you must wipe cache,dalvic, data/factory reset,system
Aldo101t said:
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
Click to expand...
Click to collapse
I was on the latest release of TWRP (2.4.4.0). I have a recovery log from when it wouldn't flash the ROM. I'll spare the unnecessary strings, and just post the error itself:
error: file_write: write: I/O error
Installer Error (Status 1)
Edit: Just to add, I just successfully flashed SuperSU on the stock ROM using the same TWRP version (2.4.4.0).
Boostjunky said:
I was on the latest release of TWRP (2.4.4.0). I have a recovery log from when it wouldn't flash the ROM. I'll spare the unnecessary strings, and just post the error itself:
error: file_write: write: I/O error
Installer Error (Status 1)
Edit: Just to add, I just successfully flashed SuperSU on the stock ROM using the same TWRP version (2.4.4.0).
Click to expand...
Click to collapse
well, I don't know for sure i'd try 2.3.3 and see what happens
Aldo101t said:
well, I don't know for sure i'd try 2.3.3 and see what happens
Click to expand...
Click to collapse
I appreciate the suggestions. I'll give a few things a try.
Looks like it was the recovery, afterall. Flashed 2.3.3.0, and the ROM is currently flashing as we speak.
Thanks again!
Boostjunky said:
Looks like it was the recovery, afterall. Flashed 2.3.3.0, and it's currently flashing as we speak.
Thanks again!
Click to expand...
Click to collapse
anytime
Aldo101t said:
what version of twrp are you using
---------- Post added at 08:47 PM ---------- Previous post was at 08:45 PM ----------
for what it's worth some of the guys had problems, and went back to 2.3.3 and solved the problem, I've never had a problem and i'm running 2.4.4
also you must wipe cache,dalvic, data/factory reset,system
Click to expand...
Click to collapse
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
mdmower said:
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
I confirm aroma not working on 2.4.4.0 at least on my end.
http://img716.imageshack.us/img716/3192/1362812254888.png
mdmower said:
Hmmm, what's going on here? Aldo101t, do aroma installers work for you on 2.4.4.0? I wonder if its a simple reboot after flashing recovery problem. I need a way to reproduce this.
Sent from my Incredible 4G LTE using Tapatalk 2
Click to expand...
Click to collapse
well, i'm not sure. when i tried to flash viper 2.2 i had a problem, but i can't remember what i did now. i used the same recovery, got it installed, i think i restored a stock rom then reflashed viper and it worked, but i'm not sure.
it's been awhile since i've tried to flasn with aroma, so
i just tried flashing viper 2.2, DID NOT WORK, so i miss spoke.sorry
I have also had problems with aroma on several builds of twrp and several builds of cwm. I'm currently on cwm touch and if it fails to install (goes from 7% to done in a few seconds) just try it again till it flashes. Also seems to help me if zips are on the ext SD card. Not sure what's up with this but that's how I got it to work. Seems to be an aroma thing. Regular zips have no problems flashing.
Sent from my Incredible 4G LTE using xda premium
The LG G Pad 8.3 has a locked bootloader, and to bypass it we have two different tools: Open bump and Loki. Most custom roms now use Open bump (recommended), but some still use Loki. Jellybean and Kitkat bootloaders have different backlight settings, and kernels need to be adapted to match those backlight settings. So here I provide some flashable zips, so you can choose the bootloader that best suits your custom rom.
IMPORTANT: to install these files, reboot into recovery and flash the zip of your choice. After that, reboot into recovery again so the changes take effect. If you are stuck on Lollipop bootloader and have no access to recovery, check this post.
V50020F Bootloader is needed if the kernel in your custom rom/recovery is adapted to Kitkat bootloader backlight, like CyanogenMod 12.1 and TWRP official builds.
V50020F Bootloader: https://www.androidfilehost.com/?fid=24352994023707804
*** DEPRECATED (below) ***
V50010B Bootloader is needed if the kernel in your custom rom is adapted to Jellybean bootloader backlight, like those based on CyanogenMod old code.
V50010B Bootloader: https://www.androidfilehost.com/?fid=23991606952613674
V50020D Bootloader Loki is needed if the kernel in your custom rom is adapted to Kitkat bootloader backlight, but it's packed with Loki. All the files are from V50020D, except aboot.img from V50010B. This should not be used anymore, every custom rom should use Open bump instead of Loki. If you are a developer and want to use Open bump instead of Loki, check this commit.
V50020D Bootloader Loki: https://www.androidfilehost.com/?fid=23991606952613676
* If you are a developer and want to use Kitkat bootloader backlight settings (instead of Jellybean), check this commit.
Wow I may not have my Gpad yet but I think its getting easier now because of this base flashable zip. Thanks
This will automatically replace old version of TWRP if flash for the first time like this one?
http://forum.xda-developers.com/showthread.php?t=2641409
@jsevi83 Great Idea! :good:
How can we exactly use this?
Just want to make sure nothings bad gonna happen
Im currently on LRS Kitkat and old TWRP. If I want to replace it with CM 4.4.2 ROM. I have to wipe the system then use 4.2.2 base then the full CM ROM?
Just found out that even the new TWRP 2.7.0.1 is still not compatible LRS ROM
Its possible to replace recovery.img with old TWRP or perhaps Philz CWM?
Yeah, I'm a little lost too on how to proceed. If you can post some detailed instructions, it'd be much appreciated
yawako said:
How can we exactly use this?
Just want to make sure nothings bad gonna happen
Im currently on LRS Kitkat and old TWRP. If I want to replace it with CM 4.4.2 ROM. I have to wipe the system then use 4.2.2 base then the full CM ROM?
Just found out that even the new TWRP 2.7.0.1 is still not compatible LRS ROM
Its possible to replace recovery.img with old TWRP or perhaps Philz CWM?
Click to expand...
Click to collapse
ptargino said:
Yeah, I'm a little lost too on how to proceed. If you can post some detailed instructions, it'd be much appreciated
Click to expand...
Click to collapse
It's pretty simple, If your on a 4.4 stock (not aosp) and want to flash an aosp 4.4 rom (which uses 4.2 bootstack) flash the 4.2 zip then reboot into recovery from recovery (important) and then flash your rom normally. If your on 4.2 stock or aosp and want to flash a 4.4 stock rom, flash the 4.4 zip then do the same by rebooting into recovery from recovery and flash away. Its important to reboot into recovery from recovery after flashing these because if you boot your current rom, the kernel and other boot partitions won't match - bad things will happen.
annoyingduck said:
It's pretty simple, If your on a 4.4 stock (not aosp) and want to flash an aosp 4.4 rom (which uses 4.2 bootstack) flash the 4.2 zip then reboot into recovery from recovery (important) and then flash your rom normally. If your on 4.2 stock or aosp and want to flash a 4.4 stock rom, flash the 4.4 zip then do the same by rebooting into recovery from recovery and flash away. Its important to reboot into recovery from recovery after flashing these because if you boot your current rom, the kernel and other boot partitions won't match - bad things will happen.
Click to expand...
Click to collapse
Thanks, I added the instructions to the first post and mentioned you in the credits.
What do you meant boot into recovery from recovery?why boot into it twice? Im on stock 4.2 and want to flash 4.4
jsevi83 said:
Thanks, I added the instructions to the first post and mentioned you in the credits.
Click to expand...
Click to collapse
ok, so i did the thing where bad things happen, i tried flashing the 4.4.2 one thinking i had 4.2.2 and now its bootloop hell. Goes to teamwin screen then it auto runs "Running Open recovery script" then bootloops again. Hard reset does not work, just goes back into loop.
How can i undo the stupidity? thanks
RyanEJ25 said:
What do you meant boot into recovery from recovery?why boot into it twice? Im on stock 4.2 and want to flash 4.4
Click to expand...
Click to collapse
Boot into recovery, flash the chosen base zip, then press the reboot button and then recovery, this way it reboots into recovery again and the changes are applied. Then you flash the rom you want.
erwaso said:
ok, so i did the thing where bad things happen, i tried flashing the 4.4.2 one thinking i had 4.2.2 and now its bootloop hell. Goes to teamwin screen then it auto runs "Running Open recovery script" then bootloops again. Hard reset does not work, just goes back into loop.
How can i undo the stupidity? thanks
Click to expand...
Click to collapse
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
jsevi83 said:
Boot into recovery, flash the chosen base zip, then press the reboot button and then recovery, this way it reboots into recovery again and the changes are applied. Then you flash the rom you want.
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
Click to expand...
Click to collapse
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
erwaso said:
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
Click to expand...
Click to collapse
I don't understand how you got into that situation, I tested the zips a lot before publishing them. Anyway, if I were you I would install the KDZ file to get back to stock. There are some threads in the forum explaining how to do that.
erwaso said:
I understand that part. Problem is I don't have the chance to do anything. It goes from LG screen to teamwin logo to the flashing screen then back to the LG screen.
How can I stop the boot looping?
Click to expand...
Click to collapse
Free thanks...
Anyways, can you get into download mode?
Sent from my LG-V500 using Tapatalk
annoyingduck said:
Free thanks...
Anyways, can you get into download mode?
Sent from my LG-V500 using Tapatalk
Click to expand...
Click to collapse
Yes sir. But while I use the mobile tool in Windows Vista, it keeps stopping at 30% during extraction. I saw that YouTube video for unbricking going from 5 to 80 in a second during extraction.
So annoyed lol. Never happened to me before.
---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------
jsevi83 said:
I don't understand how you got into that situation, I tested the zips a lot before publishing them. Anyway, if I were you I would install the KDZ file to get back to stock. There are some threads in the forum explaining how to do that.
Click to expand...
Click to collapse
I was already in trouble before, I was rooted on 4.2.2 and did a factory reset before updating to Stock 4.4.2. I got stuck in twrp home screen and no matter what I tried to wipe or flash it went back to twrp home. So I tried to flash your 4.4.2 zip and now it's all boot loop happy lol
I saw that kdz thread. I'll try it when the kids aren't running around me in circles
erwaso said:
Yes sir. But while I use the mobile tool in Windows Vista, it keeps stopping at 30% during extraction. I saw that YouTube video for unbricking going from 5 to 80 in a second during extraction.
So annoyed lol. Never happened to me before.
---------- Post added at 06:41 PM ---------- Previous post was at 06:38 PM ----------
I was already in trouble before, I was rooted on 4.2.2 and did a factory reset before updating to Stock 4.4.2. I got stuck in twrp home screen and no matter what I tried to wipe or flash it went back to twrp home. So I tried to flash your 4.4.2 zip and now it's all boot loop happy lol
I saw that kdz thread. I'll try it when the kids aren't running around me in circles
Click to expand...
Click to collapse
Use mobile tool and do it again. Be sure your using the regular mobile tool, not the modified one for the kdz method. Get in dl mode, choose upgrade recovery option + manually enter your model # and serial #. Give it a good 5+ min to determine if it's actually hanging. If it does, unplug it and plug it back in and it'll continue. I did that once and it worked fine.
-VZW LG G2 VS980
annoyingduck said:
Use mobile tool and do it again. Be sure your using the regular mobile tool, not the modified one for the kdz method. Get in dl mode, choose upgrade recovery option + manually enter your model # and serial #. Give it a good 5+ min to determine if it's actually hanging. If it does, unplug it and plug it back in and it'll continue. I did that once and it worked fine.
-VZW LG G2 VS980
Click to expand...
Click to collapse
Thanks! I'll try it and report back. Appreciate the assist!
Ended up deleting all LG related anything on my comp, then reinstalling them as suggested in another thread. This worked lol. Now to root ioroot and see if I can't screw up again.
Thanks.
jsevi83 said:
It depends on what rom you want to have. If you want stock 4.4.2, flash any of the zips found in the forum (like the flashable V50020B), it will also change the base. If you want CM11 or any other AOSP based rom, flash the 4.2.2-base.zip, reboot into recovery again and then flash the zip of the rom.
Click to expand...
Click to collapse
I still don't get it. If I am on Pacman that says 4.4.2, what do I flash? How do I know if a certain rom is AOSP based, and what bootstack when it says 4.4.2? And if I'm already on PacMan 442, and want to get rid of the dim light issue, do I flash the appropriate zip, then reflash the rom? Or do I need to downgrade to stock 4.2.2 then flash 422 zip, then flash the custom rom again???
graphdarnell said:
I still don't get it. If I am on Pacman that says 4.4.2, what do I flash? How do I know if a certain rom is AOSP based, and what bootstack when it says 4.4.2? And if I'm already on PacMan 442, and want to get rid of the dim light issue, do I flash the appropriate zip, then reflash the rom? Or do I need to downgrade to stock 4.2.2 then flash 422 zip, then flash the custom rom again???
Click to expand...
Click to collapse
If you have the dim light issue at boot, flash the 4.2.2 base zip. If you want to install a custom rom based on stock 4.4.2, install the 4.4.2 base zip.
jsevi83 said:
If you have the dim light issue at boot, flash the 4.2.2 base zip. If you want to install a custom rom based on stock 4.4.2, install the 4.4.2 base zip.
Click to expand...
Click to collapse
Thank you for the prompt reply and help. Lest I belabor the point, I understand what you're saying from the beginning, but what confused me was the mention by another member that the 4.4.2 customs roms used 4.2 "bootstack" (whatever that means). So the question again is: if a custom rom says 4.4.2, is it really 4.4.2 or 4.2 boot stack (whatever that is)? And in which case, which zip do I use?? I can do it by trial and error, but need to be assured that shooting from the hip won't mess my tab unnecessarily. Again thanks for the help.
So after trying to completely wipe my GS3 and put it back to Stock before selling it, I think ive somehow managed to delete my current ROM and now cant boot.
It can enter recovery mode (CWM) and enter download mode and flash other recoveries throw Odin But I cant load a ROM back on.
I can't access the SD card and can't mount: /System, /preload, /external_sd, /sdcard
I tried sideloading throw ADB but it cant detect the device and Kies did recognize it when I tried a "firmware upgrade and initialization" but refused to work because of its 'current version' (or something like that)
Are there any recoveries that could help? can you flash a ROM directly throw Odin? (i cant seem to find any that work), how do I fix the storage mounting / folder tree?
i9305, CWM recovery v6.0.2.9 and was running CM 11, dont have any usable backups.
Thanks:good:
Go to sammobile and download the stock rom to your phone. If you want to put your phone totaly stock flash the stock recovery too
Bath Salts said:
So after trying to completely wipe my GS3 and put it back to Stock before selling it, I think ive somehow managed to delete my current ROM and now cant boot.
It can enter recovery mode (CWM) and enter download mode and flash other recoveries throw Odin But I cant load a ROM back on.
I can't access the SD card and can't mount: /System, /preload, /external_sd, /sdcard
I tried sideloading throw ADB but it cant detect the device and Kies did recognize it when I tried a "firmware upgrade and initialization" but refused to work because of its 'current version' (or something like that)
Are there any recoveries that could help? can you flash a ROM directly throw Odin? (i cant seem to find any that work), how do I fix the storage mounting / folder tree?
i9305, CWM recovery v6.0.2.9 and was running CM 11, dont have any usable backups.
Thanks:good:
Click to expand...
Click to collapse
You need to ask your question here >> http://forum.xda-developers.com/galaxy-s3/help-i9305 << wrong forum this is 19300.Hope you have not flashed anything from here this could brick your device! If you haven't do as suggested in post above but make sure it is for your model of phone.
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
eskorpiao112 said:
Go to sammobile and download the stock rom to your phone. If you want to put your phone totaly stock flash the stock recovery too
Click to expand...
Click to collapse
Stock recovery gets flashed with stock rom unless it is custom rom which sammobile ones are not
tallman43 said:
You need to ask your question here >> http://forum.xda-developers.com/galaxy-s3/help-i9305 << wrong forum this is 19300.Hope you have not flashed anything from here this could brick your device! If you haven't do as suggested in post above but make sure it is for your model of phone.
---------- Post added at 11:06 AM ---------- Previous post was at 11:01 AM ----------
Stock recovery gets flashed with stock rom unless it is custom rom which sammobile ones are not
Click to expand...
Click to collapse
And i flashed one before flashing the stock...
eskorpiao112 said:
And i flashed one before flashing the stock...
Click to expand...
Click to collapse
Why? Odin files overwrite it so whatever you flash before flashing stock rom with odin gets wiped...Also I mentioned it so that the op would not get confused not to have a go at you .
Ok dude
Not sure if I'm the only one that this is happening too i have flashed all MM roms with no success to even get pass boot screen only stays on one plus x boot animation screen. My
recovery is blu spark v12 clean install full wipes and it just wont boot up. Anyone know any solutions to help?
White e1003? I have the original black e1003, no problems with mm roms. There has been a lot of discussion about the white one in the mm topics.
Same for me, white e1003 can't boot MM ROMs.
But as I understand, almost all MM ROMs are based on ashwin007 CM13. So maybe there is just a problem with his kernel or something else in his ROM.
Just let him the time to see what's wrong.
Same here
Hi los1010, same here dude, sorry to say.
I have been in contact with two ROM creators, Sudamod & Cyanpop.
I'm using TWRP 2.8.7.0 Blu_Spark.r8 recovery, this might be the problem, from my experience
What we have come up with (sort of) is that it definitely is a kernel issue. i still think that if i changed my recovery it might work. otherwise the E1003 is the issue here, this model was meant to be only for Chinese huh? then they changed that policy to a European-allowed model. I really don't know. i recently went back to android after some years with ios. Please let me know if you find the resolution. I have to much to do to make it some time soon but i'll update this thread if i succeed.
i think you all should try the twrp recovery by master awesome
mohammedtabish said:
i think you all should try the twrp recovery by master awesome
Click to expand...
Click to collapse
I can't install another recovery for some reason, can't enter recovery after the new one's installed. Do i have to go back to stock recovery to flash a new one?
I've tried every recovery and I'm currently on master awsome TWRP, but it doesn't work.
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
andlin97 said:
I can't install another recovery for some reason, can't enter recovery after the new one's installed. Do i have to go back to stock recovery to flash a new one?
Click to expand...
Click to collapse
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
Dose not work for me, when i tried with rashr it made the recovery go into a bootloop so to speak..
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
andlin97 said:
Dose not work for me, when i tried with rashr it made the recovery go into a bootloop so to speak..
Click to expand...
Click to collapse
Can't help you in that bro but I think there might be chances that the recovery images u are downloading might be broken do check md5 checksum and download from other browser
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
dadaz007 said:
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
Click to expand...
Click to collapse
Oh!! Now I under stand only thing u can do is reach some dev of Opx like MA(master awesome)
I have this issue as well with a black E1003, just bought it. Doesn't matter what recovery I use. anything based on 6.0 doesn't work, not even recoverys.
mohammedtabish said:
Can't help you in that bro but I think there might be chances that the recovery images u are downloading might be broken do check md5 checksum and download from other browser
---------- Post added at 09:58 PM ---------- Previous post was at 09:57 PM ----------
Oh!! Now I under stand only thing u can do is reach some dev of Opx like MA(master awesome)
Click to expand...
Click to collapse
los1010 said:
Not sure if I'm the only one that this is happening too i have flashed all MM roms with no success to even get pass boot screen only stays on one plus x boot animation screen. My
recovery is blu spark v12 clean install full wipes and it just wont boot up. Anyone know any solutions to help?
Click to expand...
Click to collapse
sydeu said:
White e1003? I have the original black e1003, no problems with mm roms. There has been a lot of discussion about the white one in the mm topics.
Click to expand...
Click to collapse
dadaz007 said:
Same for me, white e1003 can't boot MM ROMs.
But as I understand, almost all MM ROMs are based on ashwin007 CM13. So maybe there is just a problem with his kernel or something else in his ROM.
Just let him the time to see what's wrong.
Click to expand...
Click to collapse
mohammedtabish said:
i think you all should try the twrp recovery by master awesome
Click to expand...
Click to collapse
dadaz007 said:
I've tried every recovery and I'm currently on master awsome TWRP, but it doesn't work.
Click to expand...
Click to collapse
mohammedtabish said:
And anyone tried removing the updator script thing???????
---------- Post added at 09:02 PM ---------- Previous post was at 09:02 PM ----------
No u can install recovery from fastboot or if phone is booting up then u install rashr and flash the img from that app
Click to expand...
Click to collapse
dadaz007 said:
What updator script thing ?
The problem is not that it can't flash. Flashing works without problem/error. The problem is that it doesn't boot like if there is no system or kernel. It's just stuck on 1+ logo, never seen animated boot logo (eg cm droid logo).
Click to expand...
Click to collapse
Guys i F**** DID IT!!!!!
YES! only thing is that now it says setup wizard has stopped but that's problem nr 2.
God i'm happy. I have the white E1003 Euro version AND IM RUNNING SUDAMOD 6.0!! got them goosebumbs all over me xD
Okay, where to start. Spread this boys. all the people having the problem.
I'm running Onyx costom recovery TWRP r8,
Download these four files Blu_spark r88 CM13, Open Gapps ARM for 6.0, SuperSU 2.67 and Sudamods latest ROM. Lets get going.
First, totally format data, (only when having a working recovery, otherwise, stupid.) wipe dalwik cache, system, data and cache. Transer following files to internal after the wiping. SuperSU 2.67 beta, ROM, Blu_sparkr88 CM13.
Flash kernel, flash rom, flash Gapps, flash kernel once more, wipe cache & dalwik cache and it worked for me. It worked. no longer the oneplus logo. Good luck my fellow Droids, i'll try to fix problem nr.2 it is way more popular so someone must have a fix.
Ok will try this
dadaz007 said:
Ok will try this
Click to expand...
Click to collapse
Regarding setup wizard crashed when you have phone up and running, Fixed that to. Mod the Gapps zip using a PC and remove setup wizard file from CORE, then flash the zip in recovery on phone. Problem nr.3, hardware buttons down on screen does not respond. only the right one which now is back. Huh.
andlin97 said:
Guys i F**** DID IT!!!!!
YES! only thing is that now it says setup wizard has stopped but that's problem nr 2.
God i'm happy. I have the white E1003 Euro version AND IM RUNNING SUDAMOD 6.0!! got them goosebumbs all over me xD
Okay, where to start. Spread this boys. all the people having the problem.
I'm running Onyx costom recovery TWRP r8,
Download these four files Blu_spark r88 CM13, Open Gapps ARM for 6.0, SuperSU 2.67 and Sudamods latest ROM. Lets get going.
First, totally format data, (only when having a working recovery, otherwise, stupid.) wipe dalwik cache, system, data and cache. Transer following files to internal after the wiping. SuperSU 2.67 beta, ROM, Blu_sparkr88 CM13.
Flash kernel, flash rom, flash Gapps, flash kernel once more, wipe cache & dalwik cache and it worked for me. It worked. no longer the oneplus logo. Good luck my fellow Droids, i'll try to fix problem nr.2 it is way more popular so someone must have a fix.
Click to expand...
Click to collapse
Good job! I would guess it's end stk with his latest Blu spark r88 that solved it
Everyone here interested, i suggest you use cyanpop instead, trid to flash it the same way, it works much much better with the onyx. No Gapps problem either.
Maybie it was the format of the partition that did it then. Sounds strange that you can't fastboot another recovery though?
Yes i know, i have tried but it says Remote:dtb not found. I don't know why but could it be the migration from blu_Sparks custom made recocery for onyx to TWRP v12 that screws it up? Do i have to format or wipe anything before? Have tried with rashr and fastboot.
I think what did the trick is "Blu_spark r88 CM13" , thanks
[PLEASE READ BELOW]
Code:
*** Disclamer * Your warranty is now void. * *
We are not responsible for bricked devices, dead SD cards, * thermonuclear war,
or you getting fired because the alarm app failed. Please * do some research if you
have any concerns about features included in this ROM * before flashing it! YOU are
choosing to make these modifications, and if * you point the finger at us for messing
up your device, we will laugh at you.
[Sorry if this DevDB thread is ugly, I will organize is later]
Hi, this is Jiiro.
I have finally finished compiling and testing out this LineageOS custom ROM for the SM-T350.
You may have seen @andr0idfr3ak's post on LineageOS for the SM-T350 (mine is updated).
I am now going to announce that I am going to be the maintainer for the SM-T350 development of LineageOS for now.
More custom ROMs are coming through!
Specs:
Samsung Galaxy Tab A SM-T350 8-Inch Tablet (16 GB, Titanium)
SM-T350 XAR GT58WIFIXX/GT58WIFI
Known bugs:
External Audio not working
Camera
Things that work:
Internal Audio does work (For example, using headphones)
Bluetooth Audio does work
Download Links:
Latest as of August 1, 2018
Latest Updato Firmware
Latest Unofficial LineageOS
Latest TWRP from Ashyx
Latest ODIN
*Note: I don't know if ********** is trusted, I downloaded it and ran it and had no problems whatsoever
Steps:
1) Get ODIN
2) Go to Download mode on your Samsung device
3) Flash TWRP
4) In TWRP go to Wipe > Advanced Wipe and click on
a) Dalvik / ART Cache
b) System
c) Data
d) Internal Storage
e) Cache
5) Go to Download mode after that
6) Go back on your ODIN and flash the firmware from Updato
7) After that happens, go back to Download mode and flash TWRP again
8) Do Step 4 and after that move onto Step 9
9) Have ADB on your machine, be in TWRP while this happens
10) Go to Advanced > ADB Sideload
11) On your computer type
Code:
adb sideload [Destination of your LineageOS .zip]
12) You're done! It will take about 5 minutes to boot.
Sorry if the guide is confusing, I will try to rephrase them again later.
XDA:DevDB Information
[ROM][UNOFFICIAL][LINEAGEOS 15.1][ANDROID 8.1][SM-T350], ROM for the Samsung Galaxy Tab A series
Contributors
Jiiro, deadman96385, ashyx
Source Code: https://github.com/Galaxy-MSM8916/android_device_samsung_gt58wifi
ROM OS Version: 8.x Oreo
ROM Kernel: Linux 3.10.x
ROM Firmware Required: T350XXU1CQJ5 | T350XAR1CQJ5
Version Information
Status: Beta
Created 2018-08-08
Last Updated 2018-09-06
lets get this thread started I been on your Rom a day or 2 now and i like it. Its gives me a picture in picture , and it saves on storage big time from all the apps Samsung puts on these tablets. Thanks for the work.
Thanks for keeping the tab A 8" alive!!! And working on a speaker fix!!
Any luck with the audio?
Please fix this soon
RebuffedRacer13 said:
Any luck with the audio?
Click to expand...
Click to collapse
Please fix this soon
I dont know what I'm doing wrong, but i cant get this to install or boot. I've followed every single step and after it's done, i get a black screen... Please help
ELProfeMcK said:
I dont know what I'm doing wrong, but i cant get this to install or boot. I've followed every single step and after it's done, i get a black screen... Please help
Click to expand...
Click to collapse
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Do you have to sideload lineage OS or can you install via Twrp?
Also, is there a problem with the default camera app? Can you install like,open camera or Google camera? Or does it just not work at all? And internal/external audio. Do you mean headphones will or won't work? And would installing different audio drivers like Viper or something fix it?
Sorry, just want to know before I install. ?
Techguy777 said:
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Click to expand...
Click to collapse
I was doing everything using Twrp 3.1 sm-t355. Im on stock nougat 7.1.1 CQJ5 8/1/17 security patch, so basically the latest official from Samsung.
I will try using your method to see if it works. I'll update twrp to 3.2.1and not wipe internal storage.
I appreciate the reply and help. Thanks :good:
Techguy777 said:
Well let's see if we can help you out. What ROM were you on first and what firmware were you also on. I'm on nougat firmware but I usually run ghost ROM Android 6 with with permissive kernel. Also I used twrp 3.2.1 from Android freak on XDA somewhere.
Here's what I did
Flash twrp 3.2.1 in twrp from smt355 3.1 extracted image and flashed image to recovery partition in twrp not Odin.
I was on nougat firmware but running ghost project marshmallow .
I wiped data , cache, system not internal.
Flashed lineage zip with pico open gapps 8.1 arm.
Let it boot up for 5 to 10 minutes and worked.
---------- Post added at 05:13 PM ---------- Previous post was at 05:06 PM ----------
Let me add if you guys use twrp 3.2.1 make sure to not wipe your efs or restore it just use system, data, boot backup and restore if you do mess up the efs I have the fix on XDA if you get invalid mount and it won't boot up .
Click to expand...
Click to collapse
I can't find 3.2.1
Can you post a link?
lividhen said:
I can't find 3.2.1
Found it! But it says it's for oreo... Is it safe to install?
I'm on a rooted stock 7.1.1.
Never mind! ? I didn't see it!
Click to expand...
Click to collapse
Were you able to install twrp 3.2.1 it should work fine with stock nougat. Did you try flashing lineage again? Its really stable and boots right.
I recommend trying pico gapps first
---------- Post added at 10:55 PM ---------- Previous post was at 10:18 PM ----------
lividhen said:
Do you have to sideload lineage OS or can you install via Twrp?
Also, is there a problem with the default camera app? Can you install like,open camera or Google camera? Or does it just not work at all? And internal/external audio. Do you mean headphones will or won't work? And would installing different audio drivers like Viper or something fix it?
Sorry, just want to know before I install. ?
Click to expand...
Click to collapse
Bluetooth and headphones work no external speaker. I tried different audio mods viper and it works with Bluetooth or headphones wired but no external speaker. Camera I can't remember I don't ever use it.
---------- Post added at 11:31 PM ---------- Previous post was at 10:55 PM ----------
lividhen said:
I can't find 3.2.1
Can you post a link?
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=962339331458992706
ELProfeMcK said:
I was doing everything using Twrp 3.1 sm-t355. Im on stock nougat 7.1.1 CQJ5 8/1/17 security patch, so basically the latest official from Samsung.
I will try using your method to see if it works. I'll update twrp to 3.2.1and not wipe internal storage.
I appreciate the reply and help. Thanks :good:
Click to expand...
Click to collapse
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Techguy777 said:
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Click to expand...
Click to collapse
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
ELProfeMcK said:
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
Click to expand...
Click to collapse
yep. that is also my situation.
blackness, evrywhere.
ELProfeMcK said:
Nothing Man :crying: I tried your method and it didn't work. I flashed TWRP 3.2.1 on TWRP 3.1 and i keep getting the black screen. I downgraded the firmware and repeated all the steps and nothing. I'm running out of options... I also understand and know everything about the security patches but i got the tablet last weekend like that. My luck
I know TWRP 3.2.1 and lineage OS install correctly and I think they boot up because i can hear and see the tablet connecting to PC.... It's just that the screen is all black for some reason
Click to expand...
Click to collapse
Yes I've heard of that you need to shine a bright light on you're screen or turn up you're brightness on you're google account I've noticed that I shut of live display and adaptive lighting on all my phones and google saves my account information so when I load my ROM and account for the first time it automatically sets brightness. It did work you're right the screen brightness is the problem others have had this.
Techguy777 said:
Yes I've heard of that you need to shine a bright light on you're screen or turn up you're brightness on you're google account I've noticed that I shut of live display and adaptive lighting on all my phones and google saves my account information so when I load my ROM and account for the first time it automatically sets brightness. It did work you're right the screen brightness is the problem others have had this.
Click to expand...
Click to collapse
I put my phone's flashlight and i could see the lineage set up but I've tried everything to get it to light up to full and it won't. Same for TWRP. I don't know what to do.
ELProfeMcK said:
I put my phone's flashlight and i could see the lineage set up but I've tried everything to get it to light up to full and it won't. Same for TWRP. I don't know what to do.
Click to expand...
Click to collapse
You need to go into twrp setting's and you'll see a row of options at the top click the 3 rd option its brightness and screen time out. On the ROM you go into settings and turn off the automatic brightness and set it
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
If someone knows how to turn up brightness with adb or something please do share. I understand it's hard to work with if you can't see the screen options.
Techguy777 said:
I posted link to twrp 3.2.1 if you need it on this thread.
Flash twrp 3.2.1
Wipe dalvik/art cache, data, cache, and system in twrp
Flash lineage rom
Flash gapps reboot
Wait 10 minutes sometimes it's slow
I'm on nougat firmware 7.1.1 CQJ1.
But it should work on you're firmware if not downgrade to mine and try that.
I don't update firmware or security patches unless its a Android upgrade like nougat to Oreo. The reason why is because I notice the google security patches always close up rooting and other things and don't really offer anything.
Click to expand...
Click to collapse
Flash twrp with twrp or Odin?
And if it's twrp do you extract the .tar file?
Okay! I installed it! Now can someone please tell me how to turn on the backlight? I tried the brightness thing bit the backlight still stays off.
Would another kernal fix it?
Techguy777 said:
You need to go into twrp setting's and you'll see a row of options at the top click the 3 rd option its brightness and screen time out. On the ROM you go into settings and turn off the automatic brightness and set it
---------- Post added at 04:37 PM ---------- Previous post was at 04:36 PM ----------
If someone knows how to turn up brightness with adb or something please do share. I understand it's hard to work with if you can't see the screen options.
Click to expand...
Click to collapse
I did this in both TWRP and lineage O.S, brightness won't change. My brother told it could be kernel related but i dont understand why it works for some and black screens for others