Stuck in Cyanogemod 10 Splash screen - AT&T, Rogers HTC One X, Telstra One XL

Yes it's me, your friendly neighborhood noob!
I am on the AT&T one x with HBoot 1.14 and I need help, I'm stuck in the Cyanogenmod 10 splash screen. I downloaded the lastest .zip from CyanogenMod's downloads and mounted and copied the file to my SD, then installed it using TWRP, then used the boot.img from the unzipped version of the file. It seemed to install correctly but now when I try to boot into CM10 it gets stuck on the splash screen. Let me know what other info I need to give and any help is appreciated. I know this problem is probably getting old but I've tried some things I've read in other threads and nothing is working. Thanks.

G45zupa said:
Yes it's me, your friendly neighborhood noob!
I am on the AT&T one x with HBoot 1.14 and I need help, I'm stuck in the Cyanogenmod 10 splash screen. I downloaded the lastest .zip from CyanogenMod's downloads and mounted and copied the file to my SD, then installed it using TWRP, then used the boot.img from the unzipped version of the file. It seemed to install correctly but now when I try to boot into CM10 it gets stuck on the splash screen. Let me know what other info I need to give and any help is appreciated. I know this problem is probably getting old but I've tried some things I've read in other threads and nothing is working. Thanks.
Click to expand...
Click to collapse
might wanna make sure you flash your boot.img via fastboot
read this article http://forum.xda-developers.com/showthread.php?t=2064621 to get to know better about CM10.1 or http://forum.xda-developers.com/showthread.php?t=1790032 for CM10
they have all the instructions there, just need to read it. hope that helps.
note: its also better if you do S-Off, it will makes flashing the rom much easier check this thread http://forum.xda-developers.com/showthread.php?t=2155071

I posted a thread about this happening to me recently. Flash the boot.img from fastboot. Even after I did so, I had to flash the ROM and boot.img like 15 times before it finally worked

G45zupa said:
Yes it's me, your friendly neighborhood noob!
I am on the AT&T one x with HBoot 1.14 and I need help, I'm stuck in the Cyanogenmod 10 splash screen. I downloaded the lastest .zip from CyanogenMod's downloads and mounted and copied the file to my SD, then installed it using TWRP, then used the boot.img from the unzipped version of the file. It seemed to install correctly but now when I try to boot into CM10 it gets stuck on the splash screen. Let me know what other info I need to give and any help is appreciated. I know this problem is probably getting old but I've tried some things I've read in other threads and nothing is working. Thanks.
Click to expand...
Click to collapse
Did you flash the boot.img through fast boot? And did you wipe cache,dalvik cache and system? If coming from another rom you should mostly do a factory reset too.

thanks
Wow so I thought I had already wiped cache and factory reset but must not have because I did so again and it worked. Now I feel dumb. Thanks though for the links on CyanogenMod 10.1.

Related

HTC One X Flash and SDcard issue

Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason
zad2k2 said:
Good Morning,
I have run into a problem with my HOX. After rooting and unlocking, I attempted to flash a custom ROM. Well, in my haste I flashed the new boot.img before transferring the new ROM to the phone. I have now formatted all info in all areas of the phone (wrong move I know). I can boot into fastboot, I can boot into CWM.
The problem lies in the mounting of the SDcard. I read through countless threads and everything I have tried up to this point has netted zero results. I have been flashing since the old Win Mobile days. I have a fairly strong understanding of ADB. I am not a developer, nor do claim to have the knowledge of one. I am reaching out and asking for help. I have CWM, version 5.8.3.1 touch. I also tried flashing back to the original boot.img and still no dice. Perhaps I have missed a step, I hope that is all. I did make a quick post in another thread, but it was made before I read allot of the other threads, so I am double posting. I am open to trying any advice that is offered.
Thank You all so much
Jason
Click to expand...
Click to collapse
1. Wrong section, things like this should be in Q&A
2. Did you flash the CWM recovery with working ADB? If so you should be able to push the rom to your sdcard from recovery (someone correct me if I'm wrong about that).
RUU back to stock?
Sent from my HTC One X using XDA
Enter Fastboot re flash a recovery that has ADB working either teamwins or the CWM that has working ADB. Then push the rom to the sd card through ADB in recovery.
My apologies for posting in the wrong area...Thank you for the quick responses. I reflashed the current CWM, no luck. I flashed the recovery from Teamwin and things are looking up. I was able to look at the sdcard in recovery and I was able to push the ROM to the sdcard via ADB. However, when I try to install the zip, it gives the error again "can't mount sdcard" failed....hmmm Any other ideas or thoughts??
Thank You
Jason
I just wanted to say thank you to those who helped. All the time wasted, I never relocked before trying to flash RUU!!
made same mistake
...everything was too cool to be true,
rooted my HOX with
One Click HTC One X Root by kennethpenn (Win/Mac/Linux) (Recommended)
then
Auto Deodex/Debloat AT&T One X by kennethpenn
then let my HOX relax for a week, but past weekend after install CWM with
How To: Install CWM Recovery on HTC One X (AT&T)
Filed under Development, Guides by Kenneth Pennington
i was not sure about wether to install ROM
CleanROM DE 2.1 -★| Sense / AOSP Blend | Smooth! | Refreshing! |★-
or
CleanROM 2.4.5 SE -★| Landscape! | EQS! | APM! | Clean! |
i download both and then restart in recovery then i did
install zip from sdcard, but instead of do it over CleanROM 2.4.5, I did it with CleanROM DE 2.1
after reboot i realize that i screw it big time since CleanROM DE 2.1 comes without boot.img
so now when i start my HOX just reboot by itself after 5sec, the only thing i am able to do is start on recovery and when i tried to install all over again thru install zip from sdcard i just get
"E: Cant mount /sdcard/"
I ran AT&T RUU_Evita_UL_Cingular_US-1.83.502.exe and RUU 1.73 but it cant detect my HOX
help!!!
I found this for you. Give it a try. It was not my work just googled.
This is for people who have the following problem:
Cannot boot into ROM (e.g Stuck at the HTC Logo)
Boot Loop
Re-locked bootloader while having a non-working ROM
Cannot flash RUU because battery is below 30%
[edit] Try this first
The most common problem is being stuck at the HTC Logo after flashing a ROM, try clearing the fastboot cache with these steps:
Power off your phone and hold the power button + volume down
Choose fastboot from bootloader
Connect the phone to your computer
In command prompt window opened in your platform-tools folder type:
fastboot erase cache
Choose "Reboot" in fastboot menu
If this doesn't work, try the rest of the guide
http://forum.xda-developers.com/wik...very_-_what_to_do_in_the_event_of_a_bad_flash

[Q] Help Flashing ROM

Thanks for your help and time in advance. I am trying to flash a ROM to my At&T HTC One X. It is HBOOT 1.14 running ics 2.20. I am specifically trying to flash ViperXL and have failed about 3 times so far. I keep getting my phone stuck in a boot loop. It is no longer in a boot loop because I have flashed the factory ROM. My phone is rooted and I have TWRP as my recovery. I have some specific questions to ask:
1) What version of ViperXL should I use? I think I might be trying to flash the wrong version.
2) Do I leave the entire file zipped when I put it on my sd card or do I specifically extract the boot.img file and keep that file separate from the zip file?
3) If I have Flash Image GUI from the playstore should I use that to flash it? If so do I still follow step 2 above?
This is what I have been doing so far:
1) Downloading this file: ViperXL 3.2.1 - Android File Host (685MB) from http://forum.xda-developers.com/showthread.php?t=1868236
2) Using WInRar to extract its contents and move it to my sd card.
3) Using Flash Image GUI to select boot.img and then pressing flash.
4) Rebooting my phone and then wa-la, boot loop. I have actually been following a youtube video on how to do it but I'm not getting no luck.
If there is an easier way please inform me. I am a noob but love this stuff. Please be specific with instructions so I can enjoy an awesome custom ROM.
Again, thank you for your time and have a great day.
dirty2k9 said:
Thanks for your help and time in advance. I am trying to flash a ROM to my At&T HTC One X. It is HBOOT 1.14 running ics 2.20. I am specifically trying to flash ViperXL and have failed about 3 times so far. I keep getting my phone stuck in a boot loop. It is no longer in a boot loop because I have flashed the factory ROM. My phone is rooted and I have TWRP as my recovery. I have some specific questions to ask:
1) What version of ViperXL should I use? I think I might be trying to flash the wrong version.
2) Do I leave the entire file zipped when I put it on my sd card or do I specifically extract the boot.img file and keep that file separate from the zip file?
3) If I have Flash Image GUI from the playstore should I use that to flash it? If so do I still follow step 2 above?
This is what I have been doing so far:
1) Downloading this file: ViperXL 3.2.1 - Android File Host (685MB) from http://forum.xda-developers.com/showthread.php?t=1868236
2) Using WInRar to extract its contents and move it to my sd card.
3) Using Flash Image GUI to select boot.img and then pressing flash.
4) Rebooting my phone and then wa-la, boot loop. I have actually been following a youtube video on how to do it but I'm not getting no luck.
If there is an easier way please inform me. I am a noob but love this stuff. Please be specific with instructions so I can enjoy an awesome custom ROM.
Again, thank you for your time and have a great day.
Click to expand...
Click to collapse
wipe cache dalvik system and factory reset in recovery
fastboot flash boot boot.img or use the gui to flash the boot.img extracted from the viper rom
install the viper rom within recovery.
read more before you end up with a brick.
it says all this right in the second post of the viper thread
"Download the ViperXL 3.0.0 from the download section
Confirm the md5 checksum is correct on both files (it will be noted on the dl page)
Place the file somewhere on your phone storage
Reboot to TWRP recovery
Backup current ROM
Install ROM using twrp and select wipe during aroma install if coming from another base
If you have 1.14 hboot you will need to flash the boot.img in fastboot. You will need to extract this from the ROM zip. I have found the following tool useful: [TOOL] HTC Auto Boot.img Installer (One Click Tool)
Reboot and Enjoy"
All Flash Image GUI does is flash the boot.img, which is a small part of the overall ROM. You also need to have the entire ROM zip on your SD card. Boot into bootloader, then go into TWRP recovery. Once in TWRP, go to Wipe, do a factory reset (do not factory reset in bootloader, as it will corrupt your SD memory), wipe Dalvik, wipe cache. Then select Install, and navigate to the ROM zip. The ROM will begin to install. AROMA will then launch, giving you a variety of install options specific to ViperXL. Go through the AROMA options. Then when the ROM install is complete, TWRP will give you the option to reboot. Reboot and enjoy.
Do not extract rom lol. Flash it as is!
Sent from my One X using Tapatalk 2
flash successful
Thank you everyone for your replies. I got the ROM flashed and it's working great.
redpoint73 said:
(do not factory reset in bootloader, as it will corrupt your SD memory
Click to expand...
Click to collapse
Wow how did you figure this out? I now know why my sd corrupted on me once. I did click that once in my life. In fact it put me i have the "soft brick and gonna cry" category, complete with post in q&a.
There needs to be a sticky for things like this.. Little nuggets of knowledge.
The sticky should also contain the factory recovery.
And then the sticky should be mandatory before you are allowed to download roms, recoveries, etc. It would save headache for many.
wdkingery said:
Wow how did you figure this out? I now know why my sd corrupted on me once. I did click that once in my life. In fact it put me i have the "soft brick and gonna cry" category, complete with post in q&a.
There needs to be a sticky for things like this.. Little nuggets of knowledge.
The sticky should also contain the factory recovery.
And then the sticky should be mandatory before you are allowed to download roms, recoveries, etc. It would save headache for many.
Click to expand...
Click to collapse
Agreed. I too fall into the category of accidently bootloader factory resetting and almost dieing lol
it has been stated not to factory reset in bootloader, i have posted it probably almost 100 times. i'm glad this thread is finally over it was making me itch and twitch.
wdkingery said:
Wow how did you figure this out? I now know why my sd corrupted on me once.
Click to expand...
Click to collapse
Its a fairly common mistake, and as DvineLord stated, it been discussed quite a bit in various places.

[Q] Problem with booting roms htc amaze 4g

Hey Guys,
I have a rooted htc amaze 4g i rooted, s-on with Hasoon2000 tool. I currently have the clockworkmod recovery installed but have also installed team wins recovery and 4ext recovery in the past trying to figure out my problem but to no avail. Im currently running the newest version stock ruu for tmobile. I have been having the issue of getting my phone to boot my roms properly and cant figure out why. I have installed CM10 rom and The viper rom. for the amaze and both roms do the same thing. During flashing of the zip files in recovery everything seems to work fine with both roms and install properly. Once installed and i go to reboot the phone, it will get stuck on the boot screen of whichever rom I installed and never actually boots the phone fully. Im at a loss and have many hours trying to get the roms to boot but i can not figure out why both roms always get stuck on boot screen. The viper rom will flash my capacitative buttons on the bottom and vibrate periodically but still wont get past the boot screen, Sorry if i left out any information out or if im making a newbie mistake (which im hoping for). I have an understanding of things but im no expert by any means, just let me know if you need to know more.
Thanks!
zebediah101 said:
Hey Guys,
I have a rooted htc amaze 4g i rooted, s-on with Hasoon2000 tool. I currently have the clockworkmod recovery installed but have also installed team wins recovery and 4ext recovery in the past trying to figure out my problem but to no avail. Im currently running the newest version stock ruu for tmobile. I have been having the issue of getting my phone to boot my roms properly and cant figure out why. I have installed CM10 rom and The viper rom. for the amaze and both roms do the same thing. During flashing of the zip files in recovery everything seems to work fine with both roms and install properly. Once installed and i go to reboot the phone, it will get stuck on the boot screen of whichever rom I installed and never actually boots the phone fully. Im at a loss and have many hours trying to get the roms to boot but i can not figure out why both roms always get stuck on boot screen. The viper rom will flash my capacitative buttons on the bottom and vibrate periodically but still wont get past the boot screen, Sorry if i left out any information out or if im making a newbie mistake (which im hoping for). I have an understanding of things but im no expert by any means, just let me know if you need to know more.
Thanks!
Click to expand...
Click to collapse
i think you might have S-on boot into fastboot and list us everything there please!
Trozzul said:
i think you might have S-on boot into fastboot and list us everything there please!
Click to expand...
Click to collapse
Sorry if im misunderstanding you but i do have s-on as it says in bootloader. I booted into boot loader, selected fastboot and the contents are as follows:
*** Unlocked ***
Ruby PVT SHIP S-ON RL
Hboot-1.93.0002
eMMC-boot
Fastboot
Recovery
Factory Reset
Clear Storage
SimLock
Image CRC
zebediah101 said:
Sorry if im misunderstanding you but i do have s-on as it says in bootloader. I booted into boot loader, selected fastboot and the contents are as follows:
*** Unlocked ***
Ruby PVT SHIP S-ON RL
Hboot-1.93.0002
eMMC-boot
Fastboot
Bootloader
Reboot
Reboot Bootloader
Power Down
Click to expand...
Click to collapse
so yeah that's a easy fix, your gonna want to take a file out of the Rom (CM10.zip) its going to be called Boot.img and your going to put on your SD card of the phone along with the ROM and the preferred gapps if you want one. your going to need to flash these in this order
Boot.img >CM10.zip >Gapps! if you were to get s-off you don't need to do this you can flash stuff normally.
Trozzul said:
so yeah that's a easy fix, your gonna want to take a file out of the Rom (CM10.zip) its going to be called Boot.img and your going to put on your SD card of the phone along with the ROM and the preferred gapps if you want one. your going to need to flash these in this order
Boot.img >CM10.zip >Gapps! if you were to get s-off you don't need to do this you can flash stuff normally.
Click to expand...
Click to collapse
Do I take the original rom that i extracted the files from, compress the boot img, then compress the remaining files back into the cm10.zip minus the boot and flash in order? Or do i just extract the boot img out of cm10.zip and compress it to zip and flash, then do the same flash with an unaltered version of cm10.zip in proper order?
zebediah101 said:
Do I take the original rom that i extracted the files from, compress the boot img, then compress the remaining files back into the cm10.zip minus the boot and flash in order? Or do i just extract the boot img out of cm10.zip and compress it to zip and flash, then do the same flash with an unaltered version of cm10.zip in proper order?
Click to expand...
Click to collapse
No no no no your making it hard on yourself bro, zips are a little like folders but when you drag stuff out of it, it copys the file instead of moving it, not all flashes have to be .zip types like I said before go into the cm10.zip with winrar or 7zip and take out boot.img flash the boot.IMG and then the ROM followed by the gapps after, its a good question to ask, if I knew was much as I know about winrar before started flashing roms I would have asked the same thing
Trozzul said:
No no no no your making it hard on yourself bro, zips are a little like folders but when you drag stuff out of it, it copys the file instead of moving it, not all flashes have to be .zip types like I said before go into the cm10.zip with winrar or 7zip and take out boot.img flash the boot.IMG and then the ROM followed by the gapps after, its a good question to ask, if I knew was much as I know about winrar before started flashing roms I would have asked the same thing
Click to expand...
Click to collapse
Okay, i have a few updates. First off i changed my recovery from clockwork to ext cuz i read on another thread 4ext is what i wanted for my scenario with s-on. Secondly i got teamveoms rom 1.7.2.3 which they fixxed the flashing of faux123 kernel and tried flashing again. I
zebediah101 said:
Okay, i have a few updates. First off i changed my recovery from clockwork to ext cuz i read on another thread 4ext is what i wanted for my scenario with s-on. Secondly i got teamveoms rom 1.7.2.3 which they fixxed the flashing of faux123 kernel and tried flashing again. I
Click to expand...
Click to collapse
you can use any custom recovery with S-on you just need to take out the boot.img for every rom you want to flash, if you dont want to do this every time you need to get S-off, i think you can flash Sense Roms with s-on without the boot.img
(oh and sorry about not noticing that you have s-on in your first post, i was sort of skimming!)
Trozzul said:
you can use any custom recovery with S-on you just need to take out the boot.img for every rom you want to flash, if you dont want to do this every time you need to get S-off, i think you can flash Sense Roms with s-on without the boot.img
im sorry I didn't realize that my post didn't post all the way idk what happened there. I do have team venom
(oh and sorry about not noticing that you have s-on in your first post, i was sort of skimming!)
Click to expand...
Click to collapse
I'm sorry I didn't realize that my post didn't post all the way. I did get teamvenom 1.7.2.3 installed properly once the faux kernel installed like it should during aroma installer and its runnin good. I do like it but would like to try a few more roms for sure before I decide. I did try and do exactly what you said with extractin the boot.img out of cm10 and flashing them seperately with the boot.img flashed 1st then cm10zip second and I am still having the same problem. The HTC screen pops up first then the cryanogenmod boot screen and it gets stuck there. I used to have the same problem the tv 1.7.2.1 andd I then got the updated 1.7.2.3 version which fixxed the faux kernel flashing issue and after that it installed properly. But I still get the same problem with cm10. Sorry if i'm a pest just want me a jellybean Rom! Lol
zebediah101 said:
I'm sorry I didn't realize that my post didn't post all the way. I did get teamvenom 1.7.2.3 installed properly once the faux kernel installed like it should during aroma installer and its runnin good. I do like it but would like to try a few more roms for sure before I decide. I did try and do exactly what you said with extractin the boot.img out of cm10 and flashing them seperately with the boot.img flashed 1st then cm10zip second and I am still having the same problem. The HTC screen pops up first then the cryanogenmod boot screen and it gets stuck there. I used to have the same problem the tv 1.7.2.1 andd I then got the updated 1.7.2.3 version which fixxed the faux kernel flashing issue and after that it installed properly. But I still get the same problem with cm10. Sorry if i'm a pest just want me a jellybean Rom! Lol
Click to expand...
Click to collapse
hmmm i do not know what todo at this point, i think you wanna take it to the official forms for the device, sorry mate.
Edit: maybe try a Sense rom first? also what version of CWM did you have before? only X.x.x is important to know.

[Q] Can't change ROM, reboot loop

I can't change my current ROM, I'm running Baked with Android 4.2.2, I had TWRP 2.7.0.0 and now I upgraded to 2.8.0.1 with the same results.
I've tried with several ROMS, I do the steps for each rom carefully, making a backup before doing a full wipe, etc, and after the install, when I reboot, I get stucked on the loading screen, I don't even see the custom ROM logo, just the Asus logo.
After the boot loop, I enter again in recovery and recover the Baked backup, and it works again.
I'm really desperate because the Baked ROM don't run well, is very slugish, so for me an upgrade is mandatory.
I've tried with several custom ROMs, the last one I tried was KatKiss Lollipop.
Any help would be greatly appretiated
krusty_da said:
I can't change my current ROM, I'm running Baked with Android 4.2.2, I had TWRP 2.7.0.0 and now I upgraded to 2.8.0.1 with the same results.
I've tried with several ROMS, I do the steps for each rom carefully, making a backup before doing a full wipe, etc, and after the install, when I reboot, I get stucked on the loading screen, I don't even see the custom ROM logo, just the Asus logo.
After the boot loop, I enter again in recovery and recover the Baked backup, and it works again.
I'm really desperate because the Baked ROM don't run well, is very slugish, so for me an upgrade is mandatory.
I've tried with several custom ROMs, the last one I tried was KatKiss Lollipop.
Any help would be greatly appretiated
Click to expand...
Click to collapse
What is your bootloader version ?
Are you doing a full wipe before installing ?
Thx Josh
If you can adb to it then go for a full wipe and try...same thing happened to me going from stock 4.2 to katkiss 4.4.4..
Look for the post i just did in tims thread for 4.4.4.. its got the links to the post...
Remember. ..wipe 'misc' as it seems gremlins like to hide in there..
Worked for me...
lj50036 said:
What is your bootloader version ?
Are you doing a full wipe before installing ?
Thx Josh
Click to expand...
Click to collapse
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
dgcruzing said:
If you can adb to it then go for a full wipe and try...same thing happened to me going from stock 4.2 to katkiss 4.4.4..
Look for the post i just did in tims thread for 4.4.4.. its got the links to the post...
Remember. ..wipe 'misc' as it seems gremlins like to hide in there..
Worked for me...
Click to expand...
Click to collapse
I installed ADB on my pc (win8 x64), and started to do the blob backup mentioned on the first link in your other post, followed all the instrucions, after the "Step 1" in the "Wheelie" menú, the tablet shuts of, as it should, but when I turn it on again, it no longer boots into android, it gets stuck in a boot loop, now I don't have TWRP anymore, I have the FlatLine CWM, so I can't recover the image created with TWRP, so I'm stuck with recovery,
I'm still trying to fix it, I'll try to revert to stock and start from there.
Thanks to the both of you, wish me luck!
krusty_da said:
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
Thanks to the both of you, wish me luck!
Click to expand...
Click to collapse
That is the issue mate you need to be on the bootloader ending with 27.5 ....... :good:
Let me know if you need any help making that happen .....
Thx Josh
krusty_da said:
My current bootloader is 10.6.1.15.3, and I'm doing a full wipe, I follow carefully the instructions every time.
I installed ADB on my pc (win8 x64), and started to do the blob backup mentioned on the first link in your other post, followed all the instrucions, after the "Step 1" in the "Wheelie" menú, the tablet shuts of, as it should, but when I turn it on again, it no longer boots into android, it gets stuck in a boot loop, now I don't have TWRP anymore, I have the FlatLine CWM, so I can't recover the image created with TWRP, so I'm stuck with recovery,
I'm still trying to fix it, I'll try to revert to stock and start from there.
Thanks to the both of you, wish me luck!
Click to expand...
Click to collapse
Yes, dont worry too much as I was in the same boat.. lost the recovery a few times.. and or couldn't get recovery to mount any partitions..
If you have still got ADB connection then use Busters wipe... multiple times.. as it cleaned mine out..
Then I used the easyflasher to flash the CWM kitkat Version and used this to flash Tims Kitkat off the external SDcard..
booted in to Kitkat with out loading Gapps.. let it settle then booted in to the recovery then booted to Bootloader..
and reflashed TWRP 2.8.. flashed Gapps with this and its all settled in..
One thing that I made sure off was to boot the device after flashing a recovery.. somewhere in all the instructions it says to to this.. So I made sure I did it..
otherwise I kept getting that password screen in TWRP...and if i got that then I knew it was not mounting anything..
K.. keep at it.. if there is will there is a way and as said if you have an unlocked bootloader and ADB you are half way there already..
Good luck..
lj50036 said:
That is the issue mate you need to be on the bootloader ending with 27.5 ....... :good:
Let me know if you need any help making that happen .....
Thx Josh
Click to expand...
Click to collapse
Thanks! I'm loading Lollipop for the fisrt time now!
I found a tutorial here to change the bootloader:
http://forum.xda-developers.com/showthread.php?t=2187982
And downloaded the latest firmware from here:
http://www.service.asus.com/#!downloads/c1wax
Thanks again

Custom ROM Issue... Stuck Booting...

Hey androids, I submitted this question as a reply to the guide thread already earlier... just thought it might get noticed in this forum alittle quicker... any help would be appreciated
I'm working on a recalled tablet that I rooted to keep using, and up until recently the ROM i had installed on it worked famously (bliss pop with android 5.1.1). Now, I was having some issues with it and thought "Well, i'll try out a different rom!"
So, I already had root (obviously) and I had already successfully installed a rom to this tablet... Using TWRP (both the 2.8.x.x I used previously and the newest one available for the shield) I have backed up, wiped, and flashed the images to 3 different roms + gapps for the appropriate versions...
first, I was going an issue with it mounting the \data partition so it wouldn't flash anything... then I repaired and rewiped the partitions, and got (what appeared to me in the logs) a clean and successful install of the roms. Each time I successfully flashed a ROM and GAPPs zips I would go to boot the ROM and my table would sit on the "NVIDIA" boot screen forever, never advancing to boot the ROMs.
I was worried that I had made a mistake and bricked the thing (though, it's been on borrowed time anyways being a recalled tablet). But I was able to force shutdown the tablet and reboot it into TWRP for another try. Each time I cleared the previous flash, wiped the cache and system partitions, and would get another clean install... but each time, it would get stuck on that same boot screen....
Anyone have any suggestions? thoughts? ideas? fixes? answers?.... anything? lol
Thanks folks!
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Is the newest TWRP *not* a MM bootloader?
TWRP is a recovery. A bootloader is a bootloader.
This is covered in every rom thread that updated from L to M.
lafester said:
This is covered in every rom thread that updated from L to M.
Click to expand...
Click to collapse
I'll re-look, the guides i've read have only covered flashing TWRP, then using them to flash the ROM and GAPPs... Which is what I did the first time I rooted it and put on a custom ROM... though maybe I didn't delete the original bootloader the first time and did so accidentally this time?
Thanks for the heads up though people, we'll see if I can straighten it out now that I know what I'm looking for
edisso10018 said:
Assuming you are trying to flash MM custom roms: You need the MM bootloader.
Click to expand...
Click to collapse
Ok, so I've downloaded the shield recovery zip, flashed the boot.img to the boot... nothing, then I read on one of the guides here that the "blob.img" is the bootloader... but the zip has a blob, without the .img
So I then attempted to add .img, and flash it to "boot" in TWRP, and there was an error, saying the file is too large...
do you (or someone else) know where to find a guide on where to find/how to flash a MM bootloader?
thanks
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
MilesD37 said:
Ok, so I found guide with links to the latest firmware update; I flashed it, rebooted, and now I've gotta past the "Nvidia" boot screen into the Bliss boot screen... It's been here for a couple minutes now, gonna give it alittle bit and then try to install the other ROM I had tried.
Click to expand...
Click to collapse
Im stuk with the same probem, can you sendme the Link to the gide please

Categories

Resources