Hi guys,
After an attempt to install the new EOS JB rom, I got stuck at the loading screen and would not go further. I then tried to recover my backup rom and that still gets stuck at the boot screen. Can anyone point me in the right direction? I did some google search and I tried alot of methods. I am getting scared that I could brick my device and I need some guidance before I go any further. Please help!
The backup doesn't work because u need to flash the kernel,
In order to do that, Just flash your previous rom or if u know which kernel u had, flash the kernel
My TF101 will no longer boot. I was running the CM10 preview build, but I was having some random reboots and other issues, so I decided to flash CM9 this weekend. Like a good boy, I backed up apps with Titanium Backup and did a full backup in CWM (Roach).
I flashed the the ROM and GAPPS and was able to boot no problem. I used Titanium to restore my apps. I rebooted after the restore and was stuck on the boot animation for close to 20 min. before I forced a shutdown and went back into CWM. First, I tried a factory reset and tried to reboot, with the same effect, then I restored my CWM backup and had the same boot problem, then I tried a earlier CWM backup that also had the same effect.
I'm starting to worry about battery levels now. I started on a full charge, but it's been running a lot. I'm also out of ideas barring NVFlash, which I don't want to do unless I have to.
Is this the same issue?
---------- Post added at 05:06 PM ---------- Previous post was at 04:38 PM ----------
Took the advice and tried flashing a ROM that thankfully I still had on my SDCard that was CM10 based and that let me restore my backup.
Prof-KOS said:
My TF101 will no longer boot. I was running the CM10 preview build, but I was having some random reboots and other issues, so I decided to flash CM9 this weekend. Like a good boy, I backed up apps with Titanium Backup and did a full backup in CWM (Roach).
I flashed the the ROM and GAPPS and was able to boot no problem. I used Titanium to restore my apps. I rebooted after the restore and was stuck on the boot animation for close to 20 min. before I forced a shutdown and went back into CWM. First, I tried a factory reset and tried to reboot, with the same effect, then I restored my CWM backup and had the same boot problem, then I tried a earlier CWM backup that also had the same effect.
I'm starting to worry about battery levels now. I started on a full charge, but it's been running a lot. I'm also out of ideas barring NVFlash, which I don't want to do unless I have to.
Is this the same issue?
---------- Post added at 05:06 PM ---------- Previous post was at 04:38 PM ----------
Took the advice and tried flashing a ROM that thankfully I still had on my SDCard that was CM10 based and that let me restore my backup.
Click to expand...
Click to collapse
ICS based ROMs can't boot up with JB kernels and CWM backups don't contain the kernel as far as I am aware. If you want to go back to CM9, you would have to flash the appropriate kernel. Once you put CM10 on your device, it would contain a JB kernel, hence why it couldn't restore your nandroid.
Sent from my Transformer TF101 using Tapatalk 2
i9apps said:
The backup doesn't work because u need to flash the kernel,
In order to do that, Just flash your previous rom or if u know which kernel u had, flash the kernel
Click to expand...
Click to collapse
I never flashed the kernel, I have been on stock. The EOS team says that JB will run with stock kernel so I did not change anything. How would I flash the kernel if I am stuck at boot screen? And which kernel should I get
Why can't you go back to CWM recovery, (holding down power and volume down button until you see some text then volume up?
For any ROM fresh install, you need to wipe data (factory reset), davik cache, cache, all in CWM Recovery before installing the ROM and kernel (optional).
AstroTrain said:
Why can't you go back to CWM recovery, (holding down power and volume down button until you see some text then volume up?
For any ROM fresh install, you need to wipe data (factory reset), davik cache, cache, all in CWM Recovery before installing the ROM and kernel (optional).
Click to expand...
Click to collapse
I tried but apparently my CWM version does not work well with tf 101. I found a solution by flashing another CWM. Here is guide for those with the same problem.
http://www.transformerforums.com/for...0-windows.html
Everything worked perfectly after I switched CWM to the rogue one
instinct408 said:
I tried but apparently my CWM version does not work well with tf 101. I found a solution by flashing another CWM. Here is guide for those with the same problem.
Everything worked perfectly after I switched CWM to the rogue one
Click to expand...
Click to collapse
Your link is broken and i would love to try it.
I have the same problem.....
I rooted, installed Rom Manager to get CWM Recovery installed and then flashed the new CyanogenMod 10 - B1 ♦ K.A.T. As soon as I restarted, after it appeared that the flash went fine, it hung at the boot screen - not frozen just wont go any further.
I tried rebooting by holding the power button, I tried re-flashing both the CY 10 and the original Rom and tried "restoring" my backed up rom.
I have tried recovering through Easy Flasher but I don't think my PC is seeing the transformer properly.
I have ADB drivers installed but because the TF dose not boot properly it dose not seem to get there.
I have let the battery drain as some report a resolve when they get it to power down all the way but as soon as I plug it in and power it up it goes back to the boot screen and stays there.
Please help as I cant afford to lose this pad (yes I knew the risks).
Related
Hello!
I was on the HKTW build as of yesterday. I have Tenfar's recovery and CWM installed too.
I attempted to install Kennith Penn's Alien Rom V2 and it seems like its flashing no problem... However, I get stuck in a boot loop.
I tried restoring to a previous back up , and that loops now too
So, I attempted to flash 2.3.4 Fruit cakes ( http://www.multiupload.com/U1EOJVAKPO ) and it seems that it is flashing it properly, because I got back my stock "AT&T" boot logo (from the factory) but, that goes into a boot loop too...
Can anyone please help point me in the correct direction of getting my device to boot the rom/ image properly? Is there a setting I need to ensure is checked on CWM (like mounts or something?) ... at this point, I cant even boot into Tenfars recovery... just CWM...
This sucks!
Thanks in advance for any help!!!
ssmr2t said:
Hello!
I was on the HKTW build as of yesterday. I have Tenfar's recovery and CWM installed too.
I attempted to install Kennith Penn's Alien Rom V2 and it seems like its flashing no problem... However, I get stuck in a boot loop.
I tried restoring to a previous back up , and that loops now too
So, I attempted to flash 2.3.4 Fruit cakes ( http://www.multiupload.com/U1EOJVAKPO ) and it seems that it is flashing it properly, because I got back my stock "AT&T" boot logo (from the factory) but, that goes into a boot loop too...
Can anyone please help point me in the correct direction of getting my device to boot the rom/ image properly? Is there a setting I need to ensure is checked on CWM (like mounts or something?) ... at this point, I cant even boot into Tenfars recovery... just CWM...
This sucks!
Thanks in advance for any help!!!
Click to expand...
Click to collapse
Bootloops in 99.9% cases means that you need to wipe.
1. Go back into CWM, wipe data / factory reset, wipe cache, go to advanced and wipe dalvik cache.
2. Flash the desired rom.
3. Go into CWM again and do all the wipes again.
And you should boot no probs.
p.s. these 3 steps should your blue print to installing any rom btw. even you want to backup apps - use TB.
thank you for your help....ive actually dome all of that and still no go
ssmr2t said:
thank you for your help....ive actually dome all of that and still no go
Click to expand...
Click to collapse
Have you tried wiping via fastboot?
moto-fastboot -w
p.s. do you have the latest CWM recovery? there can be problems if you arent using the latest one.
xploited said:
Have you tried wiping via fastboot?
moto-fastboot -w
p.s. do you have the latest CWM recovery? there can be problems if you arent using the latest one.
Click to expand...
Click to collapse
+1. i was having the same problem not too long ago and that fixed my problem.
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
danlk2 said:
I attempted to flash a Liquid Smooth rom yesterday. I rebooted into the bootloader, and chose recovery mode. I wiped all cache, then installed the zip. I followed this by installing the gapps zip immediately, which I think I shouldn't have done.
When I rebooted it, it was stuck on the liquid smooth screen for a while, I know this is normal, but when it sat there for an hour and fifteen minutes I knew something was wrong. If I hold down both volume keys and the power button I can reboot into the bootloader again, but when I now choose recovery mode, it gets stuck on the google load screen.
Can anybody help me out?
Click to expand...
Click to collapse
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
irishrally said:
Plug the N7 into your PC before you boot into the bootloader.
You were correct to flash gapps immediately after flashing the ROM. Maybe the ROM didn't flash correctly because you only wiped caches. If you are coming from a different ROM you will need to do a factory reset. If you didn't back up your apps and don't have a nandroid, then you might want to wipe caches, format system, and reflash the previous ROM and try to boot in and backup your apps. Might not work but worth a shot if you got stuck where you are now with no app backups.
Click to expand...
Click to collapse
Wow, that didn't even cross my mind, I did this and I've got the rom up and running now. Thanks a lot.
I have to think I'm not the first to be in this situation but my searches didn't turn up anything that looked familiar.
I rooted the stock phone and installed TWRP 2.6xx a month or two ago with no issues. Everything's been running great and I decided it was time to make another backup using TWRP.
After a successful backup I wiped dalvik and cache out of habit and went to reboot -- TWRP said I was not rooted and wanted to know if I wanted to install SuperSU? This question was unexpected since I'd been rooted for a long time, and I decided to just say yes. The phone rebooted and stopped at the Samsung Galaxy S4 boot screen. I did up-volume reboot to recovery, but it seemed to hang at the TWRP blue screen -- I later discovered it will eventually get to the menu after a minute or two of the blue screen. I tried wiping cache and dalvik again and rebooting -- every time I try to reboot now it asks if I want to install SuperSU -- whether I say yes or no seems to make no difference -- I've tried both several times. Every time it hangs at the Samsung boot screen, or it takes forever to get to TWRP if I'm booting to recovery.
I've tried wiping cache, dalvik and data with no improvement. I finally tried formatting data, but again no improvement. I also tried restoring my backup several times and wiping cache and dalvik but still stuck.
I prior to today's problems I'd used TWRP a number of times and I don't recall it asking the SuperSU question, so I am thinking that is the key to this problem, and I'm wondering if anyone knows what it means?
You need to go to 2502 twrp, 26+ has hanging problems and possible Partition issues, also what rom are you on? Do you need to flash super su along with the rom /gapps?
Here's the twrp forum for us SPH-L720
The last page has a download link for the most stable build for us good luck!
http://forum.xda-developers.com/showthread.php?t=2262999
I'm running what came on the phone, just unlocked, rooted, and installed TWRP.
I ran CM10.1 on my previous phone and currently on my tablet, but my impression from running it previously is CM is a downgrade in voicemail functionality (you get these annoying text messages and have to call the voicemail), and I'm assuming it doesn't support the special GS4 hardware features like being able to hover your finger.
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Nerva said:
OK I installed TWRP 2502 and it now boots to recovery normally. However, it still asks me before rebooting if I want to install SuperSU, and it hangs on the Samsung boot screen.
Click to expand...
Click to collapse
How did you root? CF auto root also installs SuperSU
Do you have a back up from when you were rooted? IF twrp keeps giving you problems, use cwm, are you able to get past the Samsung boot..
Yeah that's what I did back when I rooted it months ago. I tried running CF auto root again today and it didn't work, so I ran it from Odin and it did work that time, but there was no change -- still hangs on the Samsung boot screen, although now I'm back to the stock recovery. So I tried installing the stock MF9 firmware from Odin -- still hangs on the boot screen. I don't know what to do at this point...
After mf9 install avd stock recovery did you factory reset
Yes, I did a factory reset -- followed the video instructions by qbking77. Still hangs on the boot screen.
Take out battery.. Put back in. Go to stock recovery, holding all 3 buttons volume up factory reset.. If you used odin abd flashed mf9 it should fix you?
---------- Post added at 06:02 PM ---------- Previous post was at 05:54 PM ----------
Well I guess I tried man, someone who has more knowledge should chime in now
---------- Post added at 06:05 PM ---------- Previous post was at 06:02 PM ----------
This
http://forum.xda-developers.com/showthread.php?t=2400192
Im also stucked with the same problem!! After flashing my rom succesfully it just ask ur device is not rooted swipe to install!! I tried all the posiblities!! but i stuck with the boot image!! pls help me!!
From experience it sounds like you should head over to sammobile and Odin back to stock and start fresh.
1. Odin to stock
2. Root phone
3. Put desired recovery
4. Flash ROM (be sure to read dev install instructions some require reboot of recovery after wipe)
5.try to restore backup (best if you flash ROM that is backup then restore backup)
6.if you went into nae or ng2 you cannot downgrade to me
7.google has many solutions
Sent from my SCH-I545 using XDA Free mobile app
Sorry for necro, but did anyone figure out a solution to this? This just happened to me.
Just Reflash it
We have the same issue, tried to install supersu binary, after installing through twrp recover, my phone went bootloop, as i've tried to search the internet, the issue doesn't fix by by most of the users unless they reflash their device. though its a bit hassle starting from zero, but atleast, you got ur device back
This helps me:
1. Run Odin on your computer and, after entering download mode on your phone, establish a connection between your devices with the help of the USB cable.
2.Note: for download mode – power off your smartphone and then press and hold, at the same time, the Power, Volume Down and Home buttons.
3.Odin will try to recognize your device; if everything works as expected, on the program the “added” message will be displayed and the ID:COM field will be turned yellow, or blue. (Note: if that’s not happening, unplug the USB connection, close Odin, force restart your phone and reinstall the USB drivers on your computer before retrying the steps from above)
4.From the program click on the “PA” button and load the custom recovery image; don’t check Re Partition and Auto Reboot options.
5.When done, click on “start” and wait while TWRP recovery is being added on your phone
6.In the end, Odin will display the “pass” message and the ID:COM filed will be turned green (or other color) with message - RESTART; you can then remove the USB cord and reboot your smartphone.
I have had this prob on a few things , if you have a backup,flash any mod that will go to the device will do then run the backup and reflash should work .and if you have twrp try to reformat all but the system and see if that helps.
Good luck.
Hi to everyone.
Today, I installed the TWRP and the ROM and both were installed correctly on a Le Pro3 X722. The problem started when the Google services were updating. Suddenly, the phone restarted and entered in a bootloop. I was not even able to enter the TWRP. The page freeze on LE-Recovery logo and then crashed (fill full of lines). I disconnected the battery for a while and then, I was able to enter the TWRP for 2 time but recovery crashes in few seconds. I wanted to wipe and install a clean rom but I cannot enter TWRP anymore.
Please, Is there someone that could help me?
Thank you very much in advance
PS. My phone is not recognized via ADB. I tried with the AIO Tool but my device is not detected.
Hi, I followed the whole process for Qfil explained here:
Leeco Le Pro3 x720 Hard Brick
So the phone was running lineageos 15.1 nightly from 22.08 which i guess was kind of really unstable (even opening twitter in the morning could turn off the device. It could be turned back on right away though), xposed framework v90 w/yt...
forum.xda-developers.com
Installation was correct but nothing change in my phone:
- same start page and bootloop
- Same problem trying to access the recovery.
Now, i can connect via fastboot and I would like to install a fastboot rom (preferable EUI stock 20) but I cannot find one. All links are dead.
Thank you very much in advance
Hi guys I've been searching and cant seem to find an answer. My xt907 is rooted and my boot loader is unlocked I'm running CWM. If i install any 4.3 roms they work great for initial boot but as soon as i reboot it hangs at the warning boot loader unlocked screen. And the only way i can get the phone working again is to get to ap fastboot and use the DROID_RAZR_M_Utility_1.20 to factory reset everything. If i flash a 4.2.2 rom i don't have any problems. Any ideas guys ? Ive searched and cant seem to find an answer anywhere. Thanks in advance!
My first flash of 4.3 did this... after that I used twrp and haven't had it happen since...
Sent from my XT907 using xda app-developers app
The latest TWRP+mounting system prior to data/system wipes will probably solve your problems. Also, if you have a backup stored, you shouldn't need to fastboot every time.
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Ryan F said:
I've been having the same problem. I thought it might be because I was using CWM, so I thought I'd give it a go with TWRP 2.323. I made a backup, wiped System, Formatted Data and wiped cache and Dalvik cache and installed [ROM][4.4.1][Official][OSE Rom][XT907].
It installed and booted up fine. After a restart, it hung on the bootloader screen. After booting up into TWRP and restoring the backup, it's still hanging on the bootloader unlocked screen. Doh!
I just reinstalled the new ROM and will hope I don't have to restart while I'm out today. Any ideas on things I can try to get things working?
Click to expand...
Click to collapse
twrp 2323???
You need twrp 2630
see my goodies.
aviwdoowks said:
twrp 2323???
You need twrp 2630
see my goodies.
Click to expand...
Click to collapse
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
Fastboot!
Extract the recovery.img from the zip.
But why do that, just flash the zip from your twrp you now have installed
Ryan F said:
Okay, I downloaded xt907-twrp-2.6.3.0. In trying to flash with fastboot, it's hanging on <waiting for device>. USB Debugging is enabled and the device is showing up. Thanks for the help!
Click to expand...
Click to collapse
I believe the one that Avi has is a .zip, not a .xml, so it needs to be flashed in recovery. Load it up on your SD, boot into the recovery you have now, flash the new recovery, and then reboot recovery.
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Ryan F said:
TWRP 2.6.3.0 flashed successfully. Unfortunately, that didn't help at all. My phone still froze on the boot screen. I then booted into the new recovery, wiped everything and reinstalled the rom. Now it won't even boot the first time into the ROM, it just freezes on the boot screen. Help!
*EDIT
I just reinstalled it again and formatted data on top of the wipes this time. It booted into the new rom this time, but it did not get past the boot screen after restarting still.
Click to expand...
Click to collapse
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
aviwdoowks said:
If your rom DL is corrupt?
Also
Arrrghhh has advice on twrp 263, http://forum.xda-developers.com/showthread.php?goto=newpost&t=2573153
It should apply to our 263 also.
---------- Post added at 11:40 PM ---------- Previous post was at 11:29 PM ----------
I use their version (Q)(EDIT ONLY 261 HAS USB MOUNT) and it has usb mount! But it is hard to navigate but I am used to it
Click to expand...
Click to collapse
Okay, I downloaded the zips again to make sure. This freezing at bootloader screen has happened with every of the dozen or so roms I've tried installing over the past 6 months since I unlocked the bootloader.
RikRong said:
Many people ran into this issue when 4.3 came out and then someone realized that we were forgetting something when wiping. It was something that we did when the BL was first unlocked, but everyone seemed to forget about it. We were forgetting to mount system, prior to performing wipes of the data/caches. Like Avi said, first, I would DL the ROM again and then place it in your SD. When you wipe, do the FDR option first. After that, go into mount and mount system. Then, go into the advanced wipe options and wipe data, system, cache/dalvik, and format data again. At this point, you can install the ROM as normal, don't re-mount system prior to installing, though. When I am done wiping, I always reboot recovery, but you don't have to do that.
Click to expand...
Click to collapse
Could you clarify a little bit?
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
What's the FDR option?
---------- Post added at 09:21 AM ---------- Previous post was at 09:07 AM ----------
Ryan F said:
1.) Mount system
2.) Wipe (Factory Reset: data, cache, dalvik)
3.) Format data
4.) Install zips
Click to expand...
Click to collapse
Following the above steps didn't solve it The rom installs fine, boots up for first time normally, but still freezes on the bootloader screen after a restart.
Try geting to the bootloader options & choose normal pwr up.
The new twrp will stick at the big M sometimes.
Then the file is bad or you are missing the install steps. FDR (Factory Data Reset) is the first option you get when you go into the wipe menu, before you go into advanced options. Make sure you're wiping system too, after you mount. If it doesn't work, then it's a bad file or you're still doing something wrong. Upgrading to the most current TWRP and mounting system fixed the issues for 99% of the people. The other 1% just have one of those phones that is "quirky."
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
beady1 said:
okay not sure if your still having this problem. But i never did solve my issue just kept using 4.2.2. But i just flashed the new jbx kernel and a KitKat rom the other along with the newest version on safestrap and i have no issues. Everything flashed and installed perfectly and it boots like a champ. So maybe just skip over 4.3 like i did and see if you still have the issues. Sorry didnt see you were trying to flash 4.4. Only thing i can suggest is make sure you have newest safestrap and wipe out the old etc. But im sure everyone already touched on this stuff before me
Click to expand...
Click to collapse
Part of your problem is because you are using SS. If you're BL is unlocked, get rid of SS and use CWM or TWRP. SS is not a real recovery replacement, your stock recovery is still there. That's probably part of the reason you had issues.
possibly but i have 0 issues now so its not a big deal.
I have the stable Cyanogenmod 10.1 installed on my phone now. I'm able to restart my phone without any consequences finally. Yay.
I also tried the cm-11-20131221-NIGHTLY-xt907.zip build. That one would initially start up fine, but a restart gave me the frozen bootloader screen. I tried it twice, redownloading it, too. Gah, it's frustrating not being able to try out different roms, but at least I have one that works!
Well, thanks for the help guys. I'd still like to be able to install other roms, so if anyone else has something I can try, I'll do it!
Please help me. I'm using a Google Nexus 6P. I'm in a softbrick state (bootloop). At first, i taught a simple flash of stock factory image from google with help. But nothing helped. I tried everyhting from the internet asked me to do. I used adb, fastboot, nexus toolkit, but nothing helps. The phone keep on bootlooping. I can go to bootloader and recovery. The bootloop starts when i was flashing a nandroid backup (PureNexus Rom) from a BenzoRom. When i finished flashing the nandroid backup, the bootloop starts. I even did a factory reset, wipe everything, flash a fully stock rom (7.0.0), but the phone won't start..please help me XDA..i really need your help!
Are the android versions of Benzo and PureNexus the same?
CharliexCharger said:
Are the android versions of Benzo and PureNexus the same?
Click to expand...
Click to collapse
Yes it was 7.0 for both of them
afdhalzaed said:
Please help me. I'm using a Google Nexus 6P. I'm in a softbrick state (bootloop). At first, i taught a simple flash of stock factory image from google with help. But nothing helped. I tried everyhting from the internet asked me to do. I used adb, fastboot, nexus toolkit, but nothing helps. The phone keep on bootlooping. I can go to bootloader and recovery. The bootloop starts when i was flashing a nandroid backup (PureNexus Rom) from a BenzoRom. When i finished flashing the nandroid backup, the bootloop starts. I even did a factory reset, wipe everything, flash a fully stock rom (7.0.0), but the phone won't start..please help me XDA..i really need your help!
Click to expand...
Click to collapse
Welcome to the club..
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page38
---------- Post added at 07:50 PM ---------- Previous post was at 07:44 PM ----------
Same thing happened to a lot of us. Some were able to recover and some were not, unfortunate I couldn't no matter what I tried. And believe me I tried everything possible. Fastboot , toolkits no go , as for me I couldn't even access recovery. So I did the next best thing, as I was able to flash factory images and lock bootloader I had to rma the device. Waiting on the new one now.
BIGSAMDA1ST said:
Welcome to the club..
http://forum.xda-developers.com/nexus-6p/help/figure-brick-t3450921/page38
---------- Post added at 07:50 PM ---------- Previous post was at 07:44 PM ----------
Same thing happened to a lot of us. Some were able to recover and some were not, unfortunate I couldn't no matter what I tried. And believe me I tried everything possible. Fastboot , toolkits no go , as for me I couldn't even access recovery. So I did the next best thing, as I was able to flash factory images and lock bootloader I had to rma the device. Waiting on the new one now.
Click to expand...
Click to collapse
that's hard..your device was in hardbrick state yes? mine is in softbrick..that's why im so stressed out why this thing cant be fixed..because usually soft brick is easy to be fix..
afdhalzaed said:
that's hard..your device was in hardbrick state yes? mine is in softbrick..that's why im so stressed out why this thing cant be fixed..because usually soft brick is easy to be fix..
Click to expand...
Click to collapse
I was able to flash all factory images manually, I was able to use a toolkit which I normally won't use to download all the images fine. Just that when it came to booting up or even accessing recovery it was a no go. Everything flashed fine via fastboot or toolkit.
I actually did it! oh my god i actually did it! i got out from the freaking bootloop! and trust me i tried EVERYHTING else. Only this method, for me at least, helped. I will described exactly what i did.
1. You need a nandroid backup. Any nandroid backup for your phone is good i think. You NEED to know what version of nandroid backup you are having, and what version of ROM.
2. Wiped, erased everything on my phone.
3. Reverted my phone to stock version of the nandroid. (Google Factory) (For me i reverted to MTC20F full stock because my nandroid backup was on PureNexus MTC20F, used flash all.bat)
4. Tried booting to system but failed, still bootlooped.
5. Flashed TWRP, for me, TWRP 3.0.2.0 works. My suggestion, don't go above this version of TWRP, lots of problems!
5. Flashed the custom ROM the nandroid you had (for me, the nandroid backup was PureNexus MTC20F 6.0.1, so i flashed the PureNexus ROM running MTC20F vendor)
6. I tried rebooting to system, but not to avail.
7. I restored the nandroid backup i had earlier.
8. Progress, the boot animation appeared. Before, only Google logo poped out and then it restarts again.
9. Flash back to full stock MTC20F. (flash all.bat without wiping anything)
10. The phone fully boots!