Develop Bugs

stuck at google for 2nd time niw!

Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?

razi914 said:
Hello, this issue has happened to me before , I was on a 4.2.2 ROM , I flashed unofficial cm10.2 4.3 rom by carlos, the ROM was acting buggy, so I rebooted, and then I'm stucked at Google , rebooted into recovery , wiped everything , flashed another ROM , still stuck at Google, I had to wip everything including my SD data ;( , flashed Google factory image , rebooted fine, my question is , why I cannot roll back or install another ROM after flashing a 4.3 ROM? I always has to wipe all my data , I thought twrp was the problem, but this time I was using cwm, I'm so confused right now , I'm scared if I flashed a 4.2.2 ROM , then come back to 4.3 I will get stucked at Google again! What could be the solution to problem?
Click to expand...
Click to collapse
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize

Carlos_Manuel said:
Ok... so you wrote to my ROM thread about it and I try to help you!
1. Use CWM, I ahve no experience of TWRP and I can't help Nexus users who uses TWRP
2. Flash factory images by wiping everything
3. If you flash a ROM then in CWM wipe data factory reset <-- it keeps files in the internal storage
4. Then flash a ROM
5. If it happens again them maybe something is broken on your Nexus, then I recommend the phone service...
Sorry I'm busy ad I read that quick if I missed some lines or didn't understand something, then I apologize
Click to expand...
Click to collapse
You better get some rest bro, u didn't read anything,! This issue also happened to you also, you said a 10-15 pages back that ur stuck on google too after rebooting, ! P.s i will install dreams 4.1.x , and wait for a 110% stable cm10.2 by you!

if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.

lastforone said:
if you're reverting back from 4.3 to 4.2, you should do the Factory/Data Reset and you should boot into OS just fine, i had that problem too and that is how i sorted it out.
Click to expand...
Click to collapse
no didnt worked for me,, had to flash factrory image

[Solved] Bootloop after flashing any Touchwiz based rom

Hi,
For about a few days, I can't flash any touchwiz based rom, even the ones I could flash without any problem before. After I flash any touchwiz rom, my phone goes into a bootloop cycle. Though I can boot into recovery and download mode with key combinations. I don't know when this happened for the first time but as far as I can remember, it would be after I flashed some 4.4 AOSP rom (could be Omnirom, I'm not sure though)
What I did to recover from boot loop:
- Wipe cache, wipe dalvik cache and reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, reboot, no joy.
- Wipe cache, wipe dalvik cache, wipe data, wipe data/media, reboot, no joy.
- Pulled out the battery between these steps too.
At first, I thought something was wrong about the aroma installer itself because the phone was getting frozen during aroma installer setup screen, then I came up that it was caused due to my older CWM version, so I updated the recovery and it didn't freze again during installation.
And by the way, I've lost my efs partition during these processes, thankfully I've had a nandroid backup from a couple of months before.
Now I'm stuck with AOSP roms and the only way I can use a touchwiz rom is to flash the stock rom via odin. But I want to use the new leaked version based Note3 featured roms.
I've seen similar topics at S4 section but I couldn't be sure if I can do the exact steps for an N7100 international device.
I'm pretty familiar with linux system and I can use adb so I can provide any kind of information you need to diagnose this issue. Thanks in advance. Best regards.
HOW I SOLVED THIS PROBLEM
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.

Guys, I really need some help.. Any idea about what might the problem be?
Sent from my GT-N7100 using XDA Premium 4 mobile app

Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful:http://d-h.st/fWr

Full wipe cache and reset in recovery menu, clear everything, you should be up and running.

akp.ajinkya said:
Download HD wipe script,flash the script zip via cwm/philz then try installing the rom of your choice.
I found the script from tamirda's phoenix rom thread and is very useful..
Click to expand...
Click to collapse
Thanks for the reply. I flashed this superwipe script, then flashed DN3 rom but still I got stuck at Samsung Galaxy Note II screen boot loop. I really don't understand this. What am I missing? What would happen if I wipe the entire internal memory block, I mean the whole things, even the root partition too.. I'm thinking that maybe there's some file inside the root partition that prevents me to flash touchwiz roms or perhaps something wrong about touchwiz based roms' bootloaders.. I'm truely pissed..
(InsertNameHere) said:
Full wipe cache and reset in recovery menu, clear everything, you should be up and running.
Click to expand...
Click to collapse
Have you read my first message? I remember that I've mentioned I've done already what you ask me to do.. Believe me I wouldn't shoot a new thread if I could've solved my problem with such easy steps. I've already done so many wipes, including internal SD and whatsoever.. I'm really confused and NEED help. Thanks anyway..

I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.

Im having the same problem but after flashing kernels (e.i. saber & perseus).
Im currently running on Tigra rom. Is this a compatibility issue or im just missing something here too?
I came across flashing bootimg but this thread http://forum.xda-developers.com/showthread.php?t=1752270
is for One S, im not sure if will work on Note 2 & haven't tried it yet.
Any suggestions? help pls...

akp.ajinkya said:
I think you can go for the method you mentioned.But also give a try to start fresh i.e pit file flashing...wiping everything n installing stock rom then rooting,flashing custom recovery n then installing any TW custom rom.
Also give other TW based roms a try too.
Click to expand...
Click to collapse
Well, the problem is gone.
What I did was the things you said.
- Wiped everything (system, data, sdcard, of course internal sdcard)
- Flashed n7100 16GB pit file via odin
- Flashed stock rom via odin
- During these steps, I realized that my CSC code had been changed, I've corrected it acording to my country code
- Rooted my phone again
- Flashed CWM 6.0.4.3 recovery
- Flashed DN3 V3.1 rom
- Bingo, I successifully booted into DN3 rom but had no WIFI
- Flashed MJ5 bootloader
- Rebooted, then WIFI worked without a problem
- Setup my phone and did some restore
It's all good now. Thanks for everything, I hope these steps can help someone facing the same problem.

Happy to help you bro

[SOLVED] Unable to install custom rom after modem upgrade

Hello,
I have a unique issue. I'm having a problem installing any custom rom on my t999 (tmobile). I have been using a custom rom for over a year. Always used TWRP. Started with Paranoid Android and for the last few months I've been using PAC-Man (nightly) roms. I was having gps lock issues, I decided to upgrade the modem to a leaked UVUEMJC, this fixed the gps lock issue. But after the reboot, I was stuck on bootloader screen. The only way I could get the rom to work was to backup the rom, flash the system and data, and after that, the rom would work until reboot. I did this a few times until it stopped working. My efs was corrupted, IMEI missing, To recover it, I went into download mode, and noticed in red Warranty bit =1. I used odin to flashed a rooted cf 4.3 samsung touchwiz rom (root66_TMO_T999UVUEMJC). All imei/efs issues were fixed. I decided to try installing a custom rom again, PAC-Man rom, it installed just fine, all EFS/IMEI info was intact, but at reboot, I got stuck on the CM bootlogo. This happens everytime. IF I recover a backup, it gets stuck on the boot logo. I'm using TWRP v2.6.3.
Anybody have any suggestions on how to fix this issue?
Thanks!

Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.

Perseus71 said:
Install TWRP 2.6.3.1. Then take a Nandroid.
Next wipe /Data. Then flash your Custom Rom. Wipe Dalvik + Cache after the Flash. Reboot and report.
Click to expand...
Click to collapse
Thanks for the reply Perseus71. I'll give it a shot!

acedik said:
Thanks for the reply Perseus71. I'll give it a shot!
Click to expand...
Click to collapse
Upgrading to the newest TWRP did the trick! Everything is working fine now. :good:
Thanks for the help!

I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D

Donny Orbit said:
I'm also having trouble flashing PAC-man.
SGH-T999LUVUBMK4
Factory reset everything, wiped SD card.
Tried latest TWRP and CWM.
Suggestions?
D
Click to expand...
Click to collapse
You need to post info about the error
Sent from my SGH-M919 using Tapatalk

It says
E: Error executing updater binary in zip '/external
Error flashing zip '/external_sd/pac_d2tmo-night
I tried flashing the Rom that doc fixed specifically for the T999LTE for the CM10.1.2 also with no avail.
Same problem.
D

wipe Dalvik and Cache before trying the rom again. If

Updating to 4.4.4 Sickness

Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.

its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops

rblckmnjr84 said:
its better to use the latest recovery like twrp becuz in twrp 2.8.0.1 which is the latest recovery you can choose wipe and then advance wipe and choose dalvik cache,system,data and cache then wipe and that normally takes care of the boot loops
Click to expand...
Click to collapse
CWM and Philz also allow you to wipe system, data, cache, and even the non-existent Dalvik cache partition.... Your post makes it sound like TWRP is the only recovery that does that Just saying..
jonnyboy2040 said:
Hi, I'm on the 4.4.2 version of the Sickness, with the MDL bootloader. I've updated the modem to NH7.
Do I need to go through the whole process of updating the firmware, re-rooting, etc., or can I just do a full wipe and update to the Sickness' 4.4.4 V3?
I tried a full wipe and installing it today, but I ran into bootloops/other failures.
Click to expand...
Click to collapse
As to your question; you should be able to do a full wipe (system/data/cache and even though it literally does nothing because the partition doesn't exist, dalvik) and then flash with no problems. I would say that since you're still one of us few lucky ones still with MDL bootloaders, try to keep an official update as a very last option!
Were you trying to flash a kernel or any other mods along with the ROM? If so, flash only the ROM itself and see how it works.
You say bootloops/other failures... that means you bootloop a lot, and when you don't bootloop something else happens. Could you be more specific on the "other failures?" Any error messages? Were you able to pull a logcat? Did you compare the MD5's? Doesn't sound like a bad download, but you never know...

i understand what you saying however i ran into the same problem using philz touch and got the latest twrp and havent got stuck in boot loops since i read a forum on this and using older recovery to flash kitkat roms has been having people phones stuck in a boot loop and throwing errors after flashing and they updated the recovery to fix it

Sh*t, I have TWRP 2.6 and never have a problem. IMO (and some others) newer versions don't seem to play well with others. That goes for all Recoveries.
As for your issue, you might have a bad DO. Try re downloading the ROM, full wipe and then flash.

well my phone didn't like philz touch it works better with the latest twrp recovery

I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/

lordcheeto03 said:
I actually ran into this last night with philz.. I tried flashing insane 4.4.4 v3 and got stuck in a bootlooop I couldn't recover from. It flashed v1 just fine, but it just wasn't having any of v3. I had to use Odin to flash the latest TWRP and have had no problems.... :/
Click to expand...
Click to collapse
Sickness mentioned something about a script that was causing bootlegs when flashing

(HELP) Bootloop OP3

I have my OP3 rooted and bootloader open today I installed the newest version of Oxygen OS I installed the software throught TWRP but i forgot to wipe dalvik and the cache but surprise the boot back without problem but i went to install supersu from also TWRP said everything was installed ok and I restarted but now is on a bootloop I already wipe dalvik and cache several times and im not sure how to installe again stock recovery or even how I will be able to install Oxygen OS again, help please.

Just wipe system and data in TWRP and flash OOS again. You can get the zip file here: http://forum.xda-developers.com/oneplus-3/how-to/mirrors-official-oxygen-os-roms-ota-t3410870

jlrodriguez said:
I have my OP3 rooted and bootloader open today I installed the newest version of Oxygen OS I installed the software throught TWRP but i forgot to wipe dalvik and the cache but surprise the boot back without problem but i went to install supersu from also TWRP said everything was installed ok and I restarted but now is on a bootloop I already wipe dalvik and cache several times and im not sure how to installe again stock recovery or even how I will be able to install Oxygen OS again, help please.
Click to expand...
Click to collapse
hey first off no need to make multiple threads for the answer and secondly your question could be searched and to be honest just flash another rom. If you rooted your phone but not sure what to do afterwards thats not good. Please take time and read up on things before you go any further...
Just want to make sure you dont make multiple threads again and don't find yourself in issues that you cant get out of. .... Good Luck