Hey guys so i recently flashed 4.2.2 (11a i believe from a tot file). It worked great then i tried to get malladus 3.0.2 running, i got cwm installed (latest one) then i flashed 1xx to 24ap prep file then rebooted, both my twrp and download mode were broken. so i used the tutorial here http://forum.xda-developers.com/showthread.php?t=2582142 and now all i get is a black screen, also for some reason android seems to mount a bunch of partitions (i accidentaly formatted the first to fat). is there any way to fix the phone, or is it a goner?
Related
Hi,
I ve done dozens of flashing with my Sony and Samsung phones with no problem. Today i decided to flash something fresh on my acer a500 tab. I did my first mistake Please help cause im reading threads for 3 hours now and i dont know how to proceed.
Heres the story:
I was on stock ics 4.0.3 rooted. I used successfully the AfterOTA tool and flashed Bootloader ics v3.14.8 + Recovery Ra v3.1.7 That gave me the Skrilacs Recovery V8.
Then i did all the usual wipes and flashed successfully RE-FLEX XX 40.4 Rom. After the first boot i noticed that my internal storage wasnt empty. It gave me only 14gb free. There were still stuff in like photos, some music and apps remainings. I desided to wipe again and reinstall the rom. I did it a couple of times and i got the same result (internal storage was still with the same stuff).
On my last try to install the rom again it stucked on rom booting screen (bootloop). I can still get into CWM but cant find a solution.
Thanks in advance for any help..
Update: just managed to get it boot back on stock. My heart is back to its place now.
Thanks
Hi,
me and my friend recieved a N4 about 2 Days ago, and I flashed mine straight away with cm10.2 .
Now my Friend came to me and asked if I could flash cm for him too.
So I did push all files via adb to the Device, and unlocked the bootloader.
After flashing cwm I found the first difference that the Screen went black.
After a hard reset, I could boot into cwm, but unfortunatly cwm isn't able to mount the sdcard partition neither the Data partition,
so I took the way and tried to install cm10.2 through sideload, which wasn't a good Idea as there is no working android Version on the Phone now.
After trying to find out what wen't wrong, I found out that my friend installed the latest OTA Update 4.3, which I didn't.
What can I do now? Do I have to wait till Koush releases a new cwm Version which might works with the "new?" Partition Table of Android 4.3?
Any help appreciated.
lg g2 att rooted with stock ROM
i actually already found a fix here
http://forum.xda-developers.com/showthread.php?t=2451696
but i tried it and it didn't work.
the phone connects fine to my computer and ADB works even though it's in recovery, but after copy/pasting the code i'm still getting the same problem.
i've tried a full wipe, and trying to install an old backup. i've tried installing the stock rooted rom again, still ending up at CWM recovery.
any other options?
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
VegasIdaho said:
I have looked at a lot of posts here over the past few days and have not found an answer to my problem. I figure more info is better that not enough, so I'm sorry if this gets a little long.
I have 2 LG G2 VS980s and have recently moved from Verizon to T-Mobile. I have the phones rooted and decided to try some custom roms. I have tried (I think) a lot of different ways to do this, with limited results. I am using TWRP as the bootloader and have tried bumped and standard (I think). They both act the same way. I initially installed TWRP with AutoRec that installed 2.7.0.0 and then flashed to 2.8.6.0. I then tried the following roms: ParanoidAndroid (latest on website), cm11, and AOPK. All three of these resulted with the phone going into boot looping. I was then able to flash the stock rom back on using lg-toolkit and the phone boot fine. I have tried VS980 stock 4.4.2 24A and 4.4.2 27A, and the phone boots fine with each.
Using the same method above I loaded on the CloudyG2 2.2 and CloudyStock roms and they both booted fine.
So to my actual question. How exactly can I get all these other roms to boot so that I can try them out? I'm sure that I have missed something since some roms work and others on this forum has gotten the other roms working.
Your help is greatly appreciated.
Click to expand...
Click to collapse
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
v.konvict said:
Most of the latest cm and aosp roms use caf sources now. So u should flash lp bootstack for ur variant
Click to expand...
Click to collapse
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
VegasIdaho said:
I flashed the following file: bootstack-vs980-LP_39a-loki-signed.zip and then tried to load CM12 file: cm-12-20150619-NIGHTLY-vs980. After this the phone goes into bootloop. When I get back into TWRP (version 2.8.6.3) I try and restore the TWRP back up, but the sdcard had been wiped and only the following folders are left: 0, obb and TWRP (with no sub-folders, so no backups). Luckily, I have the backup on a thumb drive, restored it and it boots and runs fine.
I tried loading the bootstack file through TWRP (Install) with the above results. I tried to loading it through the app "Flashify". When I rebooted the phone went into TWRP, ran a script that I didn't catch and then rebooted just fine. However, when I installed CM12 in TWRP I still got the same results above. I have restored the backups (from the drive) and am now ready to try something again.
Just to be clear, I started with TWRP 2.8.6.3 and as far as I can tell, it never changed.
I still appreciate your help and I know there is a way to get this to work. I'm sure I am missing something simple.
Click to expand...
Click to collapse
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Choristav said:
It goes into bootloop because you flashed the lp bootstack with a non-caf rom.
Click to expand...
Click to collapse
Thanks for your reply. After reading the response from v.konvict above, I thought that CM12 would be caf, but it isn't. I've got several more ROMs working now by using different bootstacks, but it is trial and error with some of the ROMs.
So I've been having a lot of trouble today, here's a quick run-down of the situation:
- Have been using 16GB model with no problems for the past few weeks
- Installed the new 3.2 update yesterday, played games for hours, no problems
- I'm using a 128GB microSD card as adopted storage, but I removed it (in the Settings) and formatted it before rooting (put supersu on it to flash from TWRP)
- Followed a guide to root today (so that I can use SixAxis app), flashed TWRP no problem, flashed SuperSU no problem, everything worked fine
- Set the microSD card up as adopted storage again
- I copied over some of the backed up files i had (from Android/Data and Android/OBB)
- As I was reinstalling and testing some games/emus, I experienced multiple random reboots
- Attempted to boot into recovery, was met with android guy on his back
- Flashed TWRP from fastboot again
- Booted into TWRP and it worked, booted into system and still experienced reboots.
- Grabbed the latest factory image (3.1 i believe) from nvidias download center, made sure it was for the 16GB modal
- Flashed the image following the directions here http://developer.download.nvidia.co...IELD_ATV/3.1.0/HowTo-Flash-Recovery-Image.txt
My Shield TV has been sitting at the Android boot animation for the past half an hour. I tried flashing again and same result. Please help!
Ubelsteiner said:
So I've been having a lot of trouble today, here's a quick run-down of the situation:
- Have been using 16GB model with no problems for the past few weeks
- Installed the new 3.2 update yesterday, played games for hours, no problems
- I'm using a 128GB microSD card as adopted storage, but I removed it (in the Settings) and formatted it before rooting (put supersu on it to flash from TWRP)
- Followed a guide to root today (so that I can use SixAxis app), flashed TWRP no problem, flashed SuperSU no problem, everything worked fine
- Set the microSD card up as adopted storage again
- I copied over some of the backed up files i had (from Android/Data and Android/OBB)
- As I was reinstalling and testing some games/emus, I experienced multiple random reboots
- Attempted to boot into recovery, was met with android guy on his back
- Flashed TWRP from fastboot again
- Booted into TWRP and it worked, booted into system and still experienced reboots.
- Grabbed the latest factory image (3.1 i believe) from nvidias download center, made sure it was for the 16GB modal
- Flashed the image following the directions here http://developer.download.nvidia.co...IELD_ATV/3.1.0/HowTo-Flash-Recovery-Image.txt
My Shield TV has been sitting at the Android boot animation for the past half an hour. I tried flashing again and same result. Please help!
Click to expand...
Click to collapse
Had similar happen to me yesterday (stuck at boot animation after re-rooting following 3.2 update), I followed this:
http://forum.xda-developers.com/shield-tv/help/stuck-boot-animation-screen-t3263143
Not sure how important the order of flashing the files is, but I did it in the same order as posted....only thing is there is no "user data" file, so in place of that line I flashed the vendor file, like so:
fastboot flash vendor vendor.img
It worked perfectly for me. Was able to root again after all that, not sure what went wrong first time.