Database Users

Flashing Rom always ends in boot loop?

I have had my N7 for a week now, and have unlocked and rooted it. I flashed the jr5 rom and it worked ok, but i decided I wanted to try the pure AOSP rom, so I did a data/cache/dalvik wipe and flashed the rom. It proceeded to boot and freeze at the Google screen. I rebooted into recovery, and attempted to restore from my backup (failed), flash the jr5 rom (failed), and reflash the AOSP rom (failed). I then decided to follow the instructions on ROOTZwiki and restore back to stock (although still unlocked). I restored to the factory image, and attempted to flash the CM10 AOKP rom, and was again met with the frozen Google screen. I made sure to wipe data and both caches each time i tried to flash a rom, but I always end up stuck at the Google screen. What could be causing this? I would really like to know if anyone has any idea, because I fully plan on running the full version of CM10 when it is released.

By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app

redmonke255 said:
By wipe Data you did factory reset in cwm? And what version of cwm are you using?
Sent from my Nexus 7 using XDA Premium HD app
Click to expand...
Click to collapse
yes i did a factory data reset each time. I am currently running v5.8.0.2 of cwm

could that be the problem? that my cwm is just outdated already?

No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium

CharliesTheMan said:
No that shouldn't be causing your problems, although I would recommend flashing TWRP recovery through goo manager.
I would first download a ROM on your computer and check the MD5. Then mount your nexus over USB and copy the new ROM over to the nexus sdcard directory and while its connected use your computer to check the MD5 on your ROM while its on the device. Then wipe data, cache, dalvic cache and system. Then install the ROM and Gapps and reboot. Make sure its only the to, and not a desperate kernel or anything for right now. When you reboot give it 10 minutes or so the first boots are often way long.
If that doesn't do it copy the stuff on your SD card over to your computer and then format the SD card.
To install TWRP, install goo manager from the play store, when you open the app just press menu, you don't need to browse for files or anything. Just press menu and then choose Install OpenRecoveryScript and when its done reboot or reboot to recovery, can't remember which did the trick, and it may take a couple of times.
Also remember that booting through boot loader to recovery requires the USB cord to be connected to a computer to avoid the Google screen looping.
Hope some of this was helpful.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Thank you for taking the time to help me. Before I do the goo-manager/twrp install, are there any inherent advantages or disadvantages of using twrp as opposed to cwm? Also, I hadn't thought to check md5s after moving the roms, so I will be doing that from now on.

Twrp works just fine.
In your recovery, can you mount and unmount all your partitions without any errors?
Sent from my Nexus 7

am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?

crache said:
am I finally doing it right?
I flashed EOS rom from a clean system and it worked fine. Decided to have gapps and installed via twrp. This would give me boot loop into recovery no matter wat combination of cache clearing etc used. So finally I did the counter intuitive and installed gapps zip followed by ROM zip. This seems to have worked though it seems backwards to me. Is this the correct procedure?
Click to expand...
Click to collapse
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.

simms22 said:
no. did the rom already come with gapps? the rom would wipe out whatever gapps you did flash before the rom.
Click to expand...
Click to collapse
I don't like Twrp not being able to boot into recovery from holding the buttons, especially running into these loops during installs. Had the sameresults with cwm though.Now I am having this boot loop with TeamEOS as well as Skanky (neither package gapps) I however only loop if installing gapps after the rom or wiping caches.
If caches and system are wiped, gapps installed, then the rom I get a functioning system.Can anyone shed some light on what trigers specific loops or how to review tje errors / panics?

I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?

spked said:
I'm reviving this thread since I have a similar issue. I am using TWRP. I have no problem performing a wipe (I do a factory reset, plus dalvik cache wipe), or flashing a new ROM (I've tried SGT7 and PA2.11). I can boot into the ROM fine. Once I try to flash Gapps, I get stuck in a boot loop that ends up going back to recovery. I've tried different combinations of operations, with different versions of gapps, but nothing works. I've tried:
gapps-jb-20120719-signed
gapps-jb-20120726-signed
both from goo.im, MD5 checked, without success. I'm stuck using SGT7, because that one includes Google account, and Play Store, so that can get me going... Only thing, I haven't wiped the data partition, because that's a bigger hassle. Do you guys have any clues as to what I should try next?
Click to expand...
Click to collapse
Do you flash the rom and gapps and then reboot, or flash the rom, reboot, then flash gapps?

Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.

dirtyhamster73 said:
Did anybody get out of their bootloop? I flashed paranoid droid with twrp and I didn't select "signature verification" or "md5 check" as I read before hand on another forum that it wasn't needed and to actually not tick "signature"....so now I'm in a bootloop, volume buttons and power does get me in to a few selections, "reboot", "power off" and "recovery". When I select recovery it just takes me to the black screen with "Google" on it. No idea how to get out of this loop....I'm researching now but I am not understanding much....I'm so use to Samsung devices, getting out of bootloop with those are a piece of cake, this I'm clueless and helpless on. So does anybody have a way for me to either reflash the rom or get me to where I can go back to stock? I used wugfresh to root. Thanks.
Click to expand...
Click to collapse
Can you get to bootloader?

If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2

Jordanooo said:
Can you get to bootloader?
Click to expand...
Click to collapse
I finally got in, so I'm all set. Thanks! I have no idea why I was having a hard time...twrp wouldn't pop up once I was in boot loader. I must of tried like 20 times. Anyway....I'm in and I just reflashed and it was fine.
---------- Post added at 05:42 PM ---------- Previous post was at 05:40 PM ----------
armyboy11b said:
If your using an older version of cwm it will boot loop and or cuase bad flashes with new builds
Upgrade cwm or just use twrp
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I'm using twrp...for whatever reason I couldn't get it to pop up to reflash. But I'm good now. Thanks!

Boot Loop

I unlocked and rooted my tablet awhile ago when i first got it.
Now i had the bright idea to flash cwm on it and I can't fix it.
I can get twrp to start i cleared the cache dalvik and other format
it several times and still no results any suggestions?
On twrp it says no OS installed. Did it delete it when i formatted it?
It also says its an insecure image rom i think
I'm thinking i need to flash a stock rom but i'm not sure how since it's not really letting me

May I knw whch tab u r usng and did u tried to flash a custom rom
your's
ajeteja.
---------- Post added at 03:58 PM ---------- Previous post was at 03:58 PM ----------
Flash a custom rom
your's
ajeteja.

cwm fail
i just tried to flash cwm i'm not sure what you mean by tab. twrp v 2.5.0.0? and i downloaded the cwm from the app in the play store

If your twrp is working then flash a custom rom fir nexus
your's
ajeteja.

kamedende said:
I unlocked and rooted my tablet awhile ago when i first got it.
Now i had the bright idea to flash cwm on it and I can't fix it.
I can get twrp to start i cleared the cache dalvik and other format
it several times and still no results any suggestions?
On twrp it says no OS installed. Did it delete it when i formatted it?
It also says its an insecure image rom i think
I'm thinking i need to flash a stock rom but i'm not sure how since it's not really letting me
Click to expand...
Click to collapse
Wugfresh toolkit.

[Q] Super S4 and KT Kernel problem

KT kernel is causing my phone to reboot on Super S4 when launching various apps. I could only find one place to snag the stock kernel which I tried and it fixed those problems. But now dropbox fails when trying to export files. Also the Amazon market fails when trying to download apps. I couldn't even update Lucky Patcher without getting a parse error. It seemed like a permissions issue so I tied to fix permissions in TWRP but that didn't help.
Any suggestions? Should I go back to KT kernel and try to figure out why it reboots my device? Or stick with stock and try to figure out the permissions problems? Or should I try a different kernel completely? Or should I just stick my phone up my ying yang and get an etch a sketch? Any help would be appreciated.

You can try flashing the stock kernel. Its located in the thread or a quick search in the Dev forum.
Did the MD5 SUM match?
Did you follow the install instructions? (Reboot recovery - full wipe)
Did you update Google services framework?
Sent from my SPH-L720 using XDA Premium 4 mobile app
---------- Post added at 06:29 PM ---------- Previous post was at 06:28 PM ----------
Stock kernel
http://forum.xda-developers.com/showthread.php?p=53630603
Sent from my SPH-L720 using XDA Premium 4 mobile app

This is what worked for me
I am happy to report absolutely zero issues on my S4 installing and using Super S4. Let me detail what I did, and maybe you can go back to square one and start over with better results. Prior to installing SS4 I had the OTA version 4.4.2 with NAE modem.
1) After reading through the Super dev thread, I decided to use Philz recovery. I downloaded this one: philz_touch_6.23.9-jflte.tar.md5 and flashed it with Odin 3.07. I made sure to disable the auto reboot, as that has caused trouble for me in the past.
2) I downloaded 1.4 odexed and copied the file to my ext sd card. Then I checked the Md5 sum of the file on the card.
3). Booted to recovery, used the "Wipe Data/Factory Reset>-Clean to Install a new ROM" feature. Twice.
4) Under "Advanced" wiped Dalvik, twice also.
5) Rebooted recovery. DON'T FORGET THIS!
6) Flashed the ROM zip.
7) After flash, Selected "no" instead of "disable install recovery"
Everything came up beautifully. Be careful which KTweaker profiles you use, I had weird stuff happening with the "battery saver" profile. I am using Ktoonsified V6 now and battery life is great.
Hope this helps!

Try the 5-28 build of Kt. Wipe your ktweeker data and cache then flash an older build and redownload your profiles of choice is reset your own. I had some reboots on the latest which I'm sure you can retweek and solve but I've not had time so reverted to 5-28 and smooth criminalv5 just to keep me going though bonfire season lol.
Sent from my SPH-L720 using xda app-developers app

Upgraded 2017U from Rooted 7.0 to 7.1.1 in a few steps and didn't lose any data?

Not sure how this happened or if it'll work for anybody else???
I did do a WeShare backup of apps and data prior to starting, just in case TiBu didn't work after the update.
I was planning on just starting over with stock Android 7.0 on my A7 (2017U)..... So I booted into TWRP, formated my data, then followed the steps in this thread, skipping the B29 rollback steps: https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
1) As I mentioned above, I booted into TWRP and did a format
1.5) Wiped everything except Micro SD and USB OTG (this step alone should have nuked all my data?)
2) went to Mount and ticked "read only"
3) Flashed A2017UV1.1.0B15_bootstack_by_DrakenFX.zip
4) Flashed A2017UV1.1.0B15_systemstock_by_DrakenFX.zip
5) Wiped Cashe/Dalvik
6) Rebooted (unplugged my usb cable first, not sure if I needed to or not but it hung the first time when it was plugged in)
I seen a screen that said "Decrypting Data", which scared me....But took about 2 minutes, then booted up and EVERYTHING was stock and right where I left it! All my apps and data was still there, along with the stock apps I had previously removed via TiBu.
I checked for and found the 7.1.1 update - It updated perfectly fine!
I booted into the bootloader, flashed TWRP 3.1 (using my PC fastboot command)
Rebooted into TWRP and flashed su2.79 (and my font) -wiped cashe/Dalvik (again).
Before rebooting, I also did the "reboot disemmcwp" using the TWRP terminal - Not sure if I needed to, but I did?
Rebooted, and I now have rooted, stock 7.1.1 and didn't have to spend 2 hours setting everything back up again!
Not sure you will have the same results as I did... I was frankly really surprised I didn't have to start over (like I planned on doing).
Good luck!

Well, I know what I'm doing after putting the toddler to bed tonight! Thanks for this!
edit: One question, when you format, it was just cache, dalvik and data you choose yea?

Bolandk said:
Well, I know what I'm doing after putting the toddler to bed tonight! Thanks for this!
edit: One question, when you format, it was just cache, dalvik and data you choose yea?
Click to expand...
Click to collapse
Actually, after the format I wiped everything except Micro SD and USB OTG....This step alone should have nuked all my data? So I really don't know how my current apps and data survived a format and a complete wipe? I did do a WeShare backup right before all of this, just in case I didn't get root back and wanted to restore my apps using that app.... I doubt that had anything to do with it.

tele_jas said:
Not sure how this happened or if it'll work for anybody else???
I did do a WeShare backup of apps and data prior to starting, just in case TiBu didn't work after the update.
I was planning on just starting over with stock Android 7.0 on my A7 (2017U)..... So I booted into TWRP, formated my data, then followed the steps in this thread, skipping the B29 rollback steps: https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
1) As I mentioned above, I booted into TWRP and did a format
1.5) Wiped everything except Micro SD and USB OTG (this step alone should have nuked all my data?)
2) went to Mount and ticked "read only"
3) Flashed A2017UV1.1.0B15_bootstack_by_DrakenFX.zip
4) Flashed A2017UV1.1.0B15_systemstock_by_DrakenFX.zip
5) Wiped Cashe/Dalvik
6) Rebooted (unplugged my usb cable first, not sure if I needed to or not but it hung the first time when it was plugged in)
I seen a screen that said "Decrypting Data", which scared me....But took about 2 minutes, then booted up and EVERYTHING was stock and right where I left it! All my apps and data was still there, along with the stock apps I had previously removed via TiBu.
I checked for and found the 7.1.1 update - It updated perfectly fine!
I booted into the bootloader, flashed TWRP 3.1 (using my PC fastboot command)
Rebooted into TWRP and flashed su1.79 (and my font) -wiped cashe/Dalvik (again).
Before rebooting, I also did the "reboot disemmcwp" using the TWRP terminal - Not sure if I needed to, but I did?
Rebooted, and I now have rooted, stock 7.1.1 and didn't have to spend 2 hours setting everything back up again!
Not sure you will have the same results as I did... I was frankly really surprised I didn't have to start over (like I planned on doing).
Good luck!
Click to expand...
Click to collapse
it worked.. but A2017UV1.1.0B15_systemstock_by_DrakenFX.zip did n't booted, so i flashed stock nougot from the BadBoyz rom.. and followed your steps.. it booted to 7.1.1

@tele_jas @`SBR` is it ok to not wipe the Internal Storage ?
Sent from my ZTE A2017U using Tapatalk

khangozzy said:
@tele_jas @`SBR` is it ok to not wipe the Internal Storage ?
Sent from my ZTE A2017U using Tapatalk
Click to expand...
Click to collapse
I was fairly certain I did, but had a couple tell me that I probably didn't "check" that box in TWRP?? I'd back up your internal storage, just in case?!?!
Someone also said it wasn't necessary to wipe your internal storage, since the base is so close? I guess you could try it without wiping your internal storage? If it's all jacked up, go back and wipe it.

tele_jas said:
Rebooted into TWRP and flashed su1.79 (and my font) -wiped cashe/Dalvik (again).
Before rebooting, I also did the "reboot disemmcwp" using the TWRP terminal - Not sure if I needed to, but I did?
Click to expand...
Click to collapse
Hello, can you post the file that you rooted with?
I'm trying with 2.79 SR3 but I get bootloops and can't boot phone up.
With what supersu did you root?
Thanks!
EDIT: fixed, don't use SR3, use SuperSU-v2.79-201612051815.zip
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

sipe1 said:
Hello, can you post the file that you rooted with?
I'm trying with 2.79 SR3 but I get bootloops and can't boot phone up.
With what supersu did you root?
Thanks!
EDIT: fixed, don't use SR3, use SuperSU-v2.79-201612051815.zip
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Yes, v2.79.... Sorry, my fat thumb must have hit the one (1) and I originally posted v1.79...But it's v2.79

tele_jas said:
Yes, v2.79.... Sorry, my fat thumb must have hit the one (1) and I originally posted v1.79...But it's v2.79
Click to expand...
Click to collapse
Still have problem with Super SU binary not installed.
Can you post exact zip that you installed? Can't get root root to work.

sipe1 said:
Still have problem with Super SU binary not installed.
Can you post exact zip that you installed? Can't get root root to work.
Click to expand...
Click to collapse
I pulled it from the link in this post: https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Here is the direct link: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

tele_jas said:
I pulled it from the link in this post: https://forum.xda-developers.com/showpost.php?p=68873482&postcount=2
Here is the direct link: https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Click to expand...
Click to collapse
Thank, problem was in F2FS data.
So no F2FS for data partition, and use SuperSU-v2.79-201612051815.zip https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip

Hey man i know this is a dumb question but where can i download the weshare app? cannot find it on the us google store :C Thanks bro

J0nhy said:
Hey man i know this is a dumb question but where can i download the weshare app? cannot find it on the us google store :C Thanks bro
Click to expand...
Click to collapse
It was pre-installed on my phone as a stock app - Bottom left corner in the pic attached here, if a pic of the icon helps (I know I sometimes over look apps).
If you don't see it, maybe search for it?? Your launcher may be hiding it?

I thought A2017UV1.1.0B1 is "7.0" not "7.1.1"???

tamahouse02 said:
I thought A2017UV1.1.0B1 is "7.0" not "7.1.1"???
Click to expand...
Click to collapse
If it's, but I was rooted and running several custom mods... So I had to revert back to stock 7.0 and then check for the upgrade (as mentioned in my OP).

tele_jas said:
It was pre-installed on my phone as a stock app - Bottom left corner in the pic attached here, if a pic of the icon helps (I know I sometimes over look apps).
If you don't see it, maybe search for it?? Your launcher may be hiding it?
Click to expand...
Click to collapse
I had that on my phone before upgrading to 7.0 lol im just sticking to titanium backup, thanks man

tele_jas said:
I was fairly certain I did, but had a couple tell me that I probably didn't "check" that box in TWRP?? I'd back up your internal storage, just in case?!?!
Someone also said it wasn't necessary to wipe your internal storage, since the base is so close? I guess you could try it without wiping your internal storage? If it's all jacked up, go back and wipe it.
Click to expand...
Click to collapse
Follow your guide without wiping Internal storage, flash B15 stock system, booted and update OTA, fastbooted twrp, rebooted trwp then flash SuperSU, then restored my B15 data backup.
Everything is fine so far.
Sent from my ZTE A2017U using Tapatalk

twrp

So I just bought a used g6 us997 and have unlocked the bootloader following the guide by autoprime and have flashed twrp 3.1.1 and when I first booted into twrp I swiped to allow modifications. Then I flashed magisk V14. So my question is did I do something wrong because of the messages that are in red in the pics?

Go to mount and mount system lol

basicreece said:
Go to mount and mount system lol
Click to expand...
Click to collapse
I tried that and it won't let me. It vibrates when I try and check system but it won't highlight.
Sent from my Pixel XL using XDA Labs

Welp.
I've been having the same problem. I was literally about to post the exact same thing. I've rooted my phone before but now I can't after I've been messing around and failing to install Fulmics rom on my phone countless times.
---------- Post added at 03:57 AM ---------- Previous post was at 03:47 AM ----------
After messing around with the mounting and making the system read only, I somehow managed to install SuperSU, even though I was getting the same error, and I tested it by installing a custom boot animation.

You using the latest TWRP?
3.2.0?

I had the same issue this morning.
to fix:
- Select Wipe
- Select Advance wipe
- Tick system only
- Select Repair or change file system
- Select repair file system
- Reboot
- Try again