Database Info

clean rom

Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?

chibra said:
Looking for some input on clean ROM on the TF300T,
This is my second time trying to install it and both times it was successful, however as soon as the boot image loads up it stays stuck loading... I did download the file again thinking it may have been corrupted.
It has been sitting there loading for 20 minutes now.
I am using cwm the latest version and I did not install a kernel still running stock
Any ideas on what could cause this?
Click to expand...
Click to collapse
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.

Clean ROM is freaking amazing! Seriously just do it I love the mods I can make for it too! Can't wait till I get my volume long press seek mod done! Love this device!
Sent from my SGH-T999
"So I put my phone into airplane mode and threw it... worst transformer ever. -.-" -My friend

tobdaryl said:
CWM has issues on this unit. Many, many complaints. I use twrp. If you decide to use twrp be sure to choose JB and tf300t version.
Click to expand...
Click to collapse
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail

chibra said:
I initially when i first rooted intalled Twrp however i was not able to flash anything at all with it, it would give me errors.... that is the only reason i went to cwm.... I was able to make backups and restores with but ROMs flashing would just fail
Click to expand...
Click to collapse
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.

oryhight sullivan
tobdaryl said:
OK. It was just a suggestion since the problem you are experiencing is usually cleared by using twrp.
Click to expand...
Click to collapse
i m going to give twrp another shot...

i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
I'm sorry it is hard to tell since you have chosen an older twrp to install. The current is five versions later and was updated as the kernels were updated to account for changes. The rom you are flashing is based on 10.4.4.25.

chibra said:
i installed http://tinyw.in/5foT
JB version for the TF300T
This is the Rom i m trying to install
http://forum.xda-developers.com/showthread.php?t=2049322
Kernel is still stock and i ve left it that way through the aroma installer
Everytime i flash and reboot i get a boot loop
Click to expand...
Click to collapse
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.

What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
Wise words. Nobody likes to listen to me so im glad someone else suggested it!

elesbb said:
Use TWRP 2.4.1.0
You are using a very old version of TWRP that has bugs with AROMA installer. So that is most likely where your issues are.
Click to expand...
Click to collapse
Updated the TWRP to the version you mentioned still stuck in boot loop.

sbdags said:
What ROM are you ccoming from? What boot loader are you on.
Sounds to me like you need to upgrade your boot loader and possibly do a full wipe - make sure you are on latest TWRP first otherwise you could brick if you use an older recovery!
Click to expand...
Click to collapse
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running

chibra said:
The only ROM i was able to flash that was fully functioning is cm10.1,
i have also flashed PA 2.9 but had some bugs i couldn't stand (screen rotation not working, extended desktop with no pie)
as for boot loader it says 1.00e by "US _Epad-10.4.2.20-20121228" A03
I just updated the TWRP as recommended on the other post (v2.4.1.0)
on every flash i wipe dalvik / Cache / Factory reset.
Before attempting to boot into Clean Rom i also followed the steps on screen saying to wipe cache and dalvik.
I m hoping PA releases a 3.0 for this device and/or i m able to get Clean rom running
Click to expand...
Click to collapse
If you are coming from cm10.1 you will definitely need to do a full wipe as it is non stock. It does say this in the first post. You only do a dalvik and cache wipe when upgrading from the same ROM or in CROMI's case from stock.
Do a data wipe in recovery, make sure you have a titanium backup or equivalent if you want to restore apps.

Success!!!
It worked perfectly fine after i install the back up i did before i flashed my 1st costume rom,
I rooted made a back up at stock/rooted... It just would not install from a full wipe,
it install fine once i flashed that specific backup and dirty flashed then wiped dalvik and cache before booting.

Touchscreen not working after CyanogenMod 11 flash. SM-P900

Hi everyone,
I have an SM-P900 rooted via the latest Chainfire Auto-Root. After that I installed the custom recovery TWRP 2.8.0.0 via Odin.
Through this custom recovery I installed the cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip
Before I flashed CM I wiped everything except the internal and external storage. Then I installed the latest gapps and after that the thouchscreen stopped working. The S-Pen is working but I cant use it with my fingers anymore.
Greetings,
Andre

I flashed the latest stock rom (PHN-P900XXUANI1-20141010224130) with Odin, the touchscreen (without SPen) still doesn't work.
Has anybody an idea how I could get it back working?

Flashed an older Stock ROM for my region (DBT, P900XXUANAE) and updated with Kies to P900XXUANC4.
Then I did a factory reset.. still no touchscreen. But the SPen is working fine.

Volans21 said:
Flashed an older Stock ROM for my region (DBT, P900XXUANAE) and updated with Kies to P900XXUANC4.
Then I did a factory reset.. still no touchscreen. But the SPen is working fine.
Click to expand...
Click to collapse
That's very strange - does the touchscreen work in TWRP?

No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?

Volans21 said:
No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?
Click to expand...
Click to collapse
flashing stock firmware with odin doesn't delete user data.
i have two versions:
1. it's hardware issue
2. flash twrp. wipe everything including internal data, then flash with odin your origianl stock firmware for your region. if it doesn't help, see above.
edit: i read your posts again. it looks like a hardware issue...

I agree, that's why I asked if it worked in TWRP - I feel it may be a hardware issue, coincidental timing?
bonuzzz said:
flashing stock firmware with odin doesn't delete user data.
i have two versions:
1. it's hardware issue
2. flash twrp. wipe everything including internal data, then flash with odin your origianl stock firmware for your region. if it doesn't help, see above.
edit: i read your posts again. it looks like a hardware issue...
Click to expand...
Click to collapse
Volans21 said:
No, its the same in TWRP.. only the S-Pen is working.
Another thing: I noticed that after I flashed a Stock ROM with Odin the configuration and data was not deleted. Is that normal? I can remember when I flashed my SGS2 with Odin it was set to factory defaults everytime. Is that because it was a three-part-firmware with PIT file?
Click to expand...
Click to collapse

Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery

natives bookmul
bonuzzz said:
Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery
Click to expand...
Click to collapse
would KIES allow him to update to P900XXUANC4 if he was on a p901, or would it not know the difference.?

bonuzzz said:
Volans21, where are you find three-part-firmware with PIT file?
maybe touchscreen stopped working after flashing pit file? but it only involves on partition scheme.. it's strange
but if touchscreen doesnt work in recovery, i think it's something with hw
stupid question: are you sure you have p900? may be something p901 or another not general device? because if i understand, you lost touchscreen after flashing custom recovery
Click to expand...
Click to collapse
notspike said:
would KIES allow him to update to P900XXUANC4 if he was on a p901, or would it not know the difference.?
Click to expand...
Click to collapse
@bonuzzz
No, I didn't find a three-part-firmware for my SM-P900.. maybe you missunderstood me: Years ago I flashed my Samsung Galaxy S2 (SGS2) with such a firmware.. I always thought, that the PIT file repartitioned my SGS2 and so the ROM was set to factory defaults. And thats why I was asking for a three-part-firmware with PIT file
I'm 100% sure that I have a SM-P900 (No LTE/4G, only Wifi). And thats what I did before the touchscreen stopped working:
A firmware update with Kies 3 to P900XXUANI1
Rooting with CF-AutoRoot (CF-Auto-Root-v1awifi-v1awifixx-smp900.zip)
Flashed TWRP 2.8.0.0 with Odin 3.07
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip) and started CM11 successfully
Flashed gapps for CM11 (gapps-kk-20140606-signed.zip)
Decided that I want to have a gapps version without all those bloatware, so I did:
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip)
Flashed gapps (pa_gapps-modular-pico-4.4.4-20141011-signed.zip) and started CM11 successfully
Worked some minutes with the tablet, rebooted the tablet and after that..
..the touchscreen stopped working.
@notspike
Kies knows the difference.. it even knows for which region the installed firmware is and installs the corresponding update.

Volans21 said:
@bonuzzz
No, I didn't find a three-part-firmware for my SM-P900.. maybe you missunderstood me: Years ago I flashed my Samsung Galaxy S2 (SGS2) with such a firmware.. I always thought, that the PIT file repartitioned my SGS2 and so the ROM was set to factory defaults. And thats why I was asking for a three-part-firmware with PIT file
I'm 100% sure that I have a SM-P900 (No LTE/4G, only Wifi). And thats what I did before the touchscreen stopped working:
A firmware update with Kies 3 to P900XXUANI1
Rooting with CF-AutoRoot (CF-Auto-Root-v1awifi-v1awifixx-smp900.zip)
Flashed TWRP 2.8.0.0 with Odin 3.07
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip) and started CM11 successfully
Flashed gapps for CM11 (gapps-kk-20140606-signed.zip)
Decided that I want to have a gapps version without all those bloatware, so I did:
Wiped everything with TWRP except internal/external SDCard
Flashed CM11 with TWRP (cm-11-20141008-UNOFFICIAL-SNAPSHOT-M11-v1awifixx.zip)
Flashed gapps (pa_gapps-modular-pico-4.4.4-20141011-signed.zip) and started CM11 successfully
Worked some minutes with the tablet, rebooted the tablet and after that..
..the touchscreen stopped working.
@notspike
Kies knows the difference.. it even knows for which region the installed firmware is and installs the corresponding update.
Click to expand...
Click to collapse
@Volans21
I've been experimenting with Cyanogen on my sm-p900 for about a week & 1/2 flashing back & forth with stock roms as well. Learning from the thread that Cyanogen is very different from the other roms, I wiped EVERYTHING except external sdcard when flashing back & forth & have not had any issues. Have you disabled Kies before trying to install as it will cause issues when flashing custom roms as well. Try disabling kies & doing a wipe of everything except external sdcard & then reflash the rom. I'm just a newbie trying to help so I hope this helps.
I also noticed that you didn't mention doing a backup in TWRP before doing anything. It would definitely serve you well to do so in the future as you will always be able to go back to what was working.

What do you mean with "disable Kies"? I know Kies as the software for managing a Samsung device with a PC.. but I didn't know that I could disable it on the phone/tablet.
Of course I did a backup with TWRP, I just didn't list i because I thought doing a backup can not cause the touchscreen to not work. Maybe I should have said that I tried to fix the touchscreen by restoring the TWRP backup.. but it didn't help. :/

Volans21 said:
What do you mean with "disable Kies"? I know Kies as the software for managing a Samsung device with a PC.. but I didn't know that I could disable it on the phone/tablet.
Of course I did a backup with TWRP, I just didn't list i because I thought doing a backup can not cause the touchscreen to not work. Maybe I should have said that I tried to fix the touchscreen by restoring the TWRP backup.. but it didn't help. :/
Click to expand...
Click to collapse
That really is sounding more and more like a hardware issue the more I look at the steps you've tried. If even wiping all data/cache/dalvik and flashing from odin stock firmware isn't fixing it it could be. The fact in twrp it's acting that way too sort of supports this.

Yes, I think so, too.

Volans21 said:
Yes, I think so, too.
Click to expand...
Click to collapse
To close this case: I sent the device back to the distributor, it was a HW issue and fixed.. even after flashing a custom ROM.
Now I flashed CM11 again.. 2 days ago. Touchscreen is still working!

[q] help with note 4 root stuck with faulty firmware and offset touch

My Note 4 was running 4.4.4 kitkat and I just decided it was time to update the firmware to Lollipop 5.0.1. I made backups of all my stuff and downloaded the lollipop firmware from Sammobile.com. I put my phone into recovery and used odin 3.0.9 to install it. After it booted up it was working fine for a few minutes. Then i installed the CWM but i accidentally installed the wrong one. I have the note 4 SM-N910P but i installed the CWM for the SM-N15P. And i flashed it using BL instead of AP in odin. After it booted up I started having issues. The touch screen wont respond correctly. When i touch the screen it actually clicks around 1.5 cm diagnolly down to the right and sometimes it doesn't respond at all. After that I tried several options
Re installing the firmware full wipe - didn't work
Reinstalling the wrong CWM the right way on AP and then factory resetting - didn't work
Wiping it from CWM recovery mode- didn't work
Wiping it from settings menu - - didn't work
Wiping it from reg Recovery mode- didn't work
Installing an older version of firmware. (4.4.4 KITKAT)- when i did that it didn't even install, it was still running lollipop. - didn't work
Installing the correct CWM and wiping it from CWM and Stock Recovery - didn't work
So ive tried all this several times in different orders to no luck. I still cant uninstall lollipop or factory/hard reset it. Is there some other program or method i can use to fix my note 4 touch issues and reinstall the firmware for real.
Thanks in advance
Update: I am on the sprint network

marktrudeau9 said:
My Note 4 was running 4.4.4 kitkat and I just decided it was time to update the firmware to Lollipop 5.0.1. I made backups of all my stuff and downloaded the lollipop firmware from Sammobile.com. I put my phone into recovery and used odin 3.0.9 to install it. After it booted up it was working fine for a few minutes. Then i installed the CWM but i accidentally installed the wrong one. I have the note 4 SM-N910P but i installed the CWM for the SM-N15P. And i flashed it using BL instead of AP in odin. After it booted up I started having issues. The touch screen wont respond correctly. When i touch the screen it actually clicks around 1.5 cm diagnolly down to the right and sometimes it doesn't respond at all. After that I tried several options
Re installing the firmware full wipe - didn't work
Reinstalling the wrong CWM the right way on AP and then factory resetting - didn't work
Wiping it from CWM recovery mode- didn't work
Wiping it from settings menu - - didn't work
Wiping it from reg Recovery mode- didn't work
Installing an older version of firmware. (4.4.4 KITKAT)- when i did that it didn't even install, it was still running lollipop. - didn't work
Installing the correct CWM and wiping it from CWM and Stock Recovery - didn't work
So ive tried all this several times in different orders to no luck. I still cant uninstall lollipop or factory/hard reset it. Is there some other program or method i can use to fix my note 4 touch issues and reinstall the firmware for real.
Thanks in advance
Update: I am on the sprint network
Click to expand...
Click to collapse
Are u sure the problem is in ROM, not hardware issue

Problem while flashing a new ROM

My phone is rooted. I have CM recovery installed. I am trying to flash a ROM but the installation is failing at 47%. It shows this message "Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and restarts the phone. When I try to wipe data or wipe media from recovery it restarts the phone. Even if I try to install from emulated storage it restarts the phone. I think there is something wrong with the storage. Can anyone help?

Karthikprabhu22 said:
My phone is rooted. I have CM recovery installed. I am trying to flash a ROM but the installation is failing at 47%. It shows this message "Detected filesystem ext4 for /dev/block/platform/msm_sdcc.1/by-name/system" and restarts the phone. When I try to wipe data or wipe media from recovery it restarts the phone. Even if I try to install from emulated storage it restarts the phone. I think there is something wrong with the storage. Can anyone help?
Click to expand...
Click to collapse
Hi, are you on latest version of CWM corresponding to your phone model ? (let us know what phone model too )
Have you tried to flash and try with TWRP's latest version for your model ? (what's model, once again...)
What rom are you trying to flash (brand and build) ? Is your bootloader up to date ?
Not easy to help you without some precise informations...

satanas17 said:
Hi, are you on the latest version of CWM corresponding to your phone model? (let us know what phone model too )
Have you tried to flash and try with TWRP's latest version for your model? (what's model, once again...)
What ROM are you trying to flash (brand and build)? Is your bootloader up to date?
Not easy to help you without some precise information...
Click to expand...
Click to collapse
I had TWRP earlier. But it suddenly stopped working. I tried to reflash it didn't work. Then I tried CWM which was flashed successfully but was freezing. Currently, I have the latest recovery by CyanogenMod. It works fine.
My phone is Moto G XT-1033 (falcon).
I haven't updated my bootloader. I will try doing it.
Thank you

I am facing same problem in twrp recovery but now everything working fine after flashing stock recovery and twrp again

Tjsdj said:
I am facing same problem in twrp recovery but now everything working fine after flashing stock recovery and twrp again
Click to expand...
Click to collapse
:good:

MOTO G (simcard issues with latest CM13 nightly)

I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......

iHackIt said:
I flashed latest CM 13 nightly (cm-13.0-20160910-NIGHTLY-falcon.zip) and facing some issues: (Moto g xt1033 Cm13)
1. Simcard is not detecting.
2. Whenever i try to call it just reboots.
It is showing me IMEI number so, thats mean simcard is working....
and other things that i think can be problem:
I have bricked my phone and recovered by using this thread http://forum.xda-developers.com/moto...oto-g-t2833798.
whenever i try to flash stock firmware it just reboots to recovery everytime (tried all android version of stock).
Only cm13 able to boot successfully and above mentioned problems occurs.....
PLEASE HELP ME AS THIS IS MY PRIMARY DEVICE......
Thank you so much.......
Click to expand...
Click to collapse
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:

karanksj said:
1. Firstly Bro calm down and have some patience while installing ROM's.
2. You have to totally reset your device back to stock. Factory reset it and wipe all data incl.system,apps caches.
3. Download stock rom "untouched version" 5.0.1 from this link http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510 according to your devices' model. (P.S. remember to thank him.)
4. Restart your phone in fastboot mode by pressing pwr+vol down button together for 10 secs. and flash evrything using fastboot...evrything incl the recovery.
5. Your device must be booted to stock now.
6. Root it again flash recovery,flash a custom rom..and enjoy.
Note: If the device is your primary device,take a lot of backup's before hand and be cautious and read forums before flashing a new ROM. :laugh:
Click to expand...
Click to collapse
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.

iHackIt said:
Yes i have flashed all the files step by step the untouched version of android 5.1. While flashing there was no error in flashing.
after flashing stock rom mu device always reboots to the recovery. (i also wiped all partitions before flashing.
Thank you for reply.
Click to expand...
Click to collapse
I quoted 5.0.1 not 5.1 brother It worked for me every time.

karanksj said:
I quoted 5.0.1 not 5.1 brother It worked for me every time.
Click to expand...
Click to collapse
Sorry for misreading...:silly:
I cant flash 5.0.1, 4.4.2,4.4.4
When i try to flash it gives errors and warnings (only 5.1 works )
i will share errors...
works in the sense it was flashed perfectly but it also boots to the recovery everytime like CM13
My bootloader version is 41.1A..