hye everyone. i'm having an issue with the Gtab plus. its actually weird issue. it seems like i can't wipe data/ factory reset. or even flash a rom every time i try to do the above methods it success until i reboot my device everything come back. if i flashed a stock rom to the gtab plus it will be successful and when the device starts its like i didn't flash anything. i'v tried wipe data / caches from Touch CWM since its the only CWM that doesn't require reboot after flashing it using "update from sdcard from the stock recovery mode" and no success when the device restart everything back. i even formatted the Sdcard from the PC but yet if i reboot the device everything will be restored i'm like "OMFG" what is going on with this device. and most of the time its on Kernel PANIC stats. any help/advice ? what i should do ? because i have tried almost everything. and btw its still on stock 3.2
bump.
k0sh said:
hye everyone. i'm having an issue with the Gtab plus. its actually weird issue. it seems like i can't wipe data/ factory reset. or even flash a rom every time i try to do the above methods it success until i reboot my device everything come back. if i flashed a stock rom to the gtab plus it will be successful and when the device starts its like i didn't flash anything. i'v tried wipe data / caches from Touch CWM since its the only CWM that doesn't require reboot after flashing it using "update from sdcard from the stock recovery mode" and no success when the device restart everything back. i even formatted the Sdcard from the PC but yet if i reboot the device everything will be restored i'm like "OMFG" what is going on with this device. and most of the time its on Kernel PANIC stats. any help/advice ? what i should do ? because i have tried almost everything. and btw its still on stock 3.2
Click to expand...
Click to collapse
Did you buy this tablet new with 3.2 on it? It's possible you have EMMC memory failed which is a hardware fail that occurs when wiping memory on ICS.
DigitalMD said:
Did you buy this tablet new with 3.2 on it? It's possible you have EMMC memory failed which is a hardware fail that occurs when wiping memory on ICS.
Click to expand...
Click to collapse
Nope never flashed the ICS it was with my sister so she has no clue what is ics lol. Its really strange, i even tried to hard brick it but as soon as it restarts it return to the old rom with everything there. Any udeas???
k0sh said:
Nope never flashed the ICS it was with my sister so she has no clue what is ics lol. Its really strange, i even tried to hard brick it but as soon as it restarts it return to the old rom with everything there. Any udeas???
Click to expand...
Click to collapse
Describe exactly the process you are using to flash.
k0sh said:
hye everyone. i'm having an issue with the Gtab plus. its actually weird issue. it seems like i can't wipe data/ factory reset. or even flash a rom every time i try to do the above methods it success until i reboot my device everything come back. if i flashed a stock rom to the gtab plus it will be successful and when the device starts its like i didn't flash anything. i'v tried wipe data / caches from Touch CWM since its the only CWM that doesn't require reboot after flashing it using "update from sdcard from the stock recovery mode" and no success when the device restart everything back. i even formatted the Sdcard from the PC but yet if i reboot the device everything will be restored i'm like "OMFG" what is going on with this device. and most of the time its on Kernel PANIC stats. any help/advice ? what i should do ? because i have tried almost everything. and btw its still on stock 3.2
Click to expand...
Click to collapse
it's not a hardware probem ..the only reason is ..ur tab's bootloader is locked so u need to unlock bootloader then every thing 'll be ok .
Hi Everyone
I recently bought a One plus one with much difficulty.
Then I decided to root it
I did everything, unlocking bootloader, installing twrp and then super su.
After that I decide to install a rom while following all the procedures.
When the rom finished installing on twrp, I reboot the phone and it show's the madhi rom and ends up with the swirling colours thing.
I waited for more than 20 minutes and nothing happened.
Tried re flashing and yet the same result.
I then decided to wipe cache, dalvik cache and system and install another rom but the same thing. It installs successfully on twrp but when the system is booting it gets stuck. I have already tried other roms via adb sideload but still no luck.
I'm not sure if i call this soft bricked or something else
Unfortunately I was an idiot, forgetting to back up the stock rom.
I can't seem to find anyone else who has this problem. I have rooted my htc one m7 before (which also got hard bricked), so i have a little experience.
I would really appreciate the help.
Did you check the md5 of the downloaded ROMs before flashing? You might corrupt downloads.
Transmitted via Bacon
Try pulling a logcat while booting and recovery log after flash
SilentChaos said:
Hi Everyone
I recently bought a One plus one with much difficulty.
Then I decided to root it
I did everything, unlocking bootloader, installing twrp and then super su.
After that I decide to install a rom while following all the procedures.
When the rom finished installing on twrp, I reboot the phone and it show's the madhi rom and ends up with the swirling colours thing.
I waited for more than 20 minutes and nothing happened.
Tried re flashing and yet the same result.
I then decided to wipe cache, dalvik cache and system and install another rom but the same thing. It installs successfully on twrp but when the system is booting it gets stuck. I have already tried other roms via adb sideload but still no luck.
I'm not sure if i call this soft bricked or something else
Unfortunately I was an idiot, forgetting to back up the stock rom.
I can't seem to find anyone else who has this problem. I have rooted my htc one m7 before (which also got hard bricked), so i have a little experience.
I would really appreciate the help.
Click to expand...
Click to collapse
Dont worry buddy , i had the same issue , look at my post ( page 2 ) and hopefully this might help
http://forum.xda-developers.com/oneplus-one/help/help-to-flash-cyanogenmod-11-to-11s-t2840751/page2
Hello all
I am facing a strange issue of phone when I took it I out of pocket it started I use multirom was on secondary rom slimkat latest when this happened. When I took it from the pocket it was on my internal rom PA latest beta2 and lost my baseband to unknown and wifi also not working so I went to twrp to flash the radio zip went fine flashing it but when rebooted there was no baseband so tried again for few times but no luck.
So I decided to start clean by removing all secondary roms and did a factory reset of the internal rom and flashed the PA 4.6 beta2 and gapps to start clean but after that the issue started happening it boots till the welcome screen to select language from there it rebooting again into a endless times tried for times to flash the rom again but still it rebooting from that screen . My phone is unusable now.
Can someone guide me how to start clean from here and to boot a rom properly.
Really hoping someone here can help me out on this. Thanks in advance.
Really need some help to get my device back up and running. Right now my phone is on endless reboot loop from the welcome screen of the rom with multirom twrp recovery.
Fingers crossed and waiting. :/
Why don't you start from scratch aka cm11s
-Tunasty
AhmedFaiz said:
Hello all
I am facing a strange issue of phone when I took it I out of pocket it started I use multirom was on secondary rom slimkat latest when this happened. When I took it from the pocket it was on my internal rom PA latest beta2 and lost my baseband to unknown and wifi also not working so I went to twrp to flash the radio zip went fine flashing it but when rebooted there was no baseband so tried again for few times but no luck.
So I decided to start clean by removing all secondary roms and did a factory reset of the internal rom and flashed the PA 4.6 beta2 and gapps to start clean but after that the issue started happening it boots till the welcome screen to select language from there it rebooting again into a endless times tried for times to flash the rom again but still it rebooting from that screen . My phone is unusable now.
Can someone guide me how to start clean from here and to boot a rom properly.
Really hoping someone here can help me out on this. Thanks in advance.
Really need some help to get my device back up and running. Right now my phone is on endless reboot loop from the welcome screen of the rom with multirom twrp recovery.
Fingers crossed and waiting. :/
Click to expand...
Click to collapse
If you read the OP for the PA 4.6 it says not to use the latest gapps as it doesn't work so try out the one that the OP recommends
Sent from my A0001 using Tapatalk
Tunasty said:
Why don't you start from scratch aka cm11s
-Tunasty
Click to expand...
Click to collapse
I think I need to do that. I am at work now need to download the cm11s from the official link. Can you link me to a good guide to start from scratch. Will try clean later today. So I need to go to fastboot manually by pressing vol up button and power button to enter?
Is it a known issue or are there others with the same issue. Please link me there too.
Thanks for the advice.
jojohnson250 said:
If you read the OP for the PA 4.6 it says not to use the latest gapps as it doesn't work so try out the one that the OP recommends
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Used the old micro gapps I don't think that is the issue here. All this started after losing my radio and wifi not working after that strange reboot from my pocket. When I connect to android file transfer it shows no files in the phone and can't move anything to the device also.
Started from scratch and back on stock cm11s. Gone stay pure stock for a while before I start rooting again.
Flashed official cm11s rom through fastboot mode.?
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
kennylrmsailo said:
Please Help
I was in miui ROM then I tried flashing Metallium ROM, after I flashed it, it booted up but, it wasn't restoring my previous apps, so I skip that part, but then when I got to the home screen I wasn't able to access my stuffs in my phone memory.
So I thought maybe I need to change the data to f2fs, so I went to the recovery and did and flashed the Metallic ROM again, but this time it didn't boot at all, there was a bootloop and I could get past the start up screen.
I tried my older ROMs the one that I had, but it's all giving me the same response now, I have switch before but I never have had this problem. Please help, how do I flash other lollipop ROM again.
Click to expand...
Click to collapse
Anyone out there? Need help desperately.
Anyone?
samuelcr93 said:
Maybe changing to f2fs and doing a factory reset. If that doesn't help, flash stock ROM via fastboot.
Click to expand...
Click to collapse
Yeah that might work but I'm kinda looking for a solution where I don't have to flash the stock again because I lost all my moto g stuffs some months back.
And another thing is that when I flash MIUI its working fine again and I'm able to access all the file in my phone storage also. Any suggestions?
Mmmm if you are using TWRP you could connect the phone to the PC and make a backup while you are in recover mode. Then format again data partition to f2fs and make a factory reset including internal storage and finally flash your ROM and restore your files.
But if that is not working then the only option is flashing Stock ROM
If MIUI is still booting it means that your data partition is still ext4
I apologize if this is posted, but we now have an official build of Marshmallow for our Oppo r7 Plus (F) Variant. link attachedhttp://download.cyanogenmod.org/?type=nightly&device=r7plus
Excellent! I am going to test it right now and will report!!!!
Update: I was on ColorOS, flashed cm13 recovery and done factory reset, formatting cache is taking around 8 minutes, is that normal?
Flashing ARM64 opengapps for 6.0 end up with error: E:Installation error in /sideload/package.zip (Status 255) - seems like recovery problem as many people report this issue. I only dont know if TWRP will work with CM13 rom
Personally I'm using a 12.1 recovery at the moment. The 13.0 recovery is still WIP AFAIK.
Gesendet von meinem R7plusf mit Tapatalk
Ok, will try cm12.1 recovery, what about gapps? Which one to use? Btw I have done factory reset again, flashed cm13 rom only, phone rebooted and loading apps (total of 87 I think), then done reboot, then only showing blue android logo for very long time, like 10 minutes followed with another "starting apps" screen with 21 left or so, now another reboot with blue android logo. Is this normal for MM roms? Still not finished.
EDIT: after another 5 minutes same screen appears with saying starting android... 21 apps left, blue android logo when done - seems to be as bootloop as it is going nowhere from here.
CM13 rom flashed fine over TWRP, flashing gaaps now seems to be alright as well (open_gapps-arm64-6.0-mini-20151218).
Very exited, good job
so far I am getting the boot-loop also. will wait to here what Nexus5-32GB will post (if any success with the cyanogen recovery) before reverting back
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Nexus5-32GB said:
Sadly "Androis is starting... Starting apps" is last message I can see, the soft reboot then followed wit this bootloop. Same when flashed with and without gapps from TWRP, cm12.1 and cm13 recoveries.
When doing factory reset in CM12.1 recovery I get this:
-- Wiping data...
Formating /data...
E:Failed to start /data/data/org.cyanogenmod.audiofx
Formating /cache...
Click to expand...
Click to collapse
check out my post after this (well before now)
coled3 said:
Guy's I got it to boot up and install so far everything seems to work okay (Minus minor distortion when automatically switching to landscape, portrait and at start up) . I am going to post a picture if I can. I believe the issues arise when we try updating to Marshmallow from lollipop and we have made major modifications. (for example I had lolli viper and a host of other customization's). I had to do a factory reset wipe and format. I then installed a backup that was untouched bone dry cyanogen mod (no g apps yet). let that boot-up and rebooted into recovery. I then downloading the nightly form (today) the 18th from the website with the marshmallow G-apps. Pushed to my sd card, wiped cache and installed the nightly and installed the correct marshmallow G-apps (ARM 64 6.0) right away. After this,I rebooted phone (it will take a while; almost as long as it did when the first nightly for lollipop came out and we flashed from color OS). It's up and running on my phone. I also still have and used the twrp recovery.
Click to expand...
Click to collapse
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Nexus5-32GB said:
going to give this a go, but I was doing factory reset and format as well, is that mean the factory reset doesnt work as it should? Flashing cm 12 rom first to be able to boot to cm13 rom later is very strange way when you think about it
Click to expand...
Click to collapse
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
coled3 said:
indeed i agree 100%. I really think it boils down to if we have any customization. I had the same error (in regards to the audio FX) You should try installing a fresh clean cyanogen nightly without g-apps or any mods. Let it boot-up and try the steps i mentioned. do you have an audio customization or any that might have changed something (it shouldn't matter but I'm considering any and everything)? If this is the case the recovery might need tweaking as that would mean somehow or someway it doesn't allow us to properly wipe and format (another consideration). I really hope you and everybody else can also update. I'm trying to upload screenshots of my phone
Click to expand...
Click to collapse
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Nexus5-32GB said:
I was on ColorOS while ago, went to TWRP and done manual wipe of Dalvik, System, Data and Cache. Installed latest cm12.1 rom without any gapps and let it boot up to home screen. Went back to TWRP and done same wipe as before. Installed cm13 without any gapps and this time I got little further than ussualy, I could see message "finishing boot" but again end up in bootloop as before. So no luck in my case...
About the error in TWRP: yes I was using viper4android before and it seems the TWRP recovery doesnt wipe the device right way - well actually not even CM recoveries can I think.
Click to expand...
Click to collapse
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
coled3 said:
The events you listed I went through the same exact sequence. Keep trying it took for me; after a painstaking install experience of course. Also you're right Cyanogen recovery doesn't allow full wipe and install.
Click to expand...
Click to collapse
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
coled3 said:
let me know if it ends up working. I also had to hold power button to restart a couple of times after installing 13 and eventually took. Fingers crossed for you!!!!! "GO NEXUS.. GO ..GO.. GO NEXUS " HEHE
Click to expand...
Click to collapse
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Nexus5-32GB said:
As I never give up :victory: I am flashing stock rom now - via stock recovery. Will try flash twrp and install cm13 straight after full wipe of ColorOS then. There is basiclly nothing more I can do really...
EDIT: same bootloop after "finishing boot" screen. Hope developers will be happy from this research
Click to expand...
Click to collapse
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Nexus5-32GB said:
am not gonna mess with restarts and so on. What I just did was, I installed the cm12.1 and tried to run system update which downloaded the cm13 rom and flashed it in twrp ending with same bootloop. I dont really know how devs could make this working on their phones at all.
Click to expand...
Click to collapse
Well, I took my 12.1 installation without any wipe, went to CM recovery from 12.1, installed my (self compiled at that time) build + opengapps (it's important to install those before booting M for the first time), booted, done. I don't have any /system mods though.
I guess I'll try the nightly and see what happens there. Did anybody of you get a logcat of the failed boot attempts?
Gesendet von meinem R7plusf mit Tapatalk
unni84kollam said:
pls help me with the stock recovery ..before flashing stock recovery should i clean wipe using twrp..what all should i select for a clean wipe..i had issues with flashing stock recovery..when i selected wipe data and cache in oppo stock recovery it wipes for a secnd and then swithc off..could not get beyond that..after many twrp boot loops now i have a cm12 working ..but battery is very poor..so i want to go back to stock..please tell the steps..
Click to expand...
Click to collapse
Just follow this quide with flashing twrp, only instead of twrp flash the stock recovery image. http://forum.xda-developers.com/showpost.php?p=63189590&postcount=5 Sorry, there is only boot command, you should type "fastboot flash recovery stock.recovery.img" - when "stock.recovery.img" is a filename of your stock recovery downloaded on your computer.
No need for wipe when installing recovery. I recon to install stock recovery and then install stock ColorOS from it, let it boot, install twrp later and do what you want then.
Looks like it's broken for everyone. I tried multiple recoverys, full wipes including /system and no joy. Guess we'll just have to wait!