[Q] SGT-P7500 3G Doesn't boot anymore -err:0x4 - Galaxy Tab 10.1 Q&A, Help & Troubleshooting

This morning as took my tablet the screen did not switch on, i tried to reboot then it stuck on bootanimation, then i tried to wipe; it still stuck on
bootanimation. Next I tried a complete wipe and installed a new Rom --> same Problem only goes to the bootanimation.
Then I tried to flash with odin, it tells me "complete write operation failed" and err:0x4. Nvflash isn't working too. So what can I do. I was on CM 10.1 nightly before, and evertything worked very well till this morning. I still can go to Download mode but twrp is not working anymore.
Thanks in advance in sorry about my poor english.
Regards.

Maybe the last edit will give you a hint:
http://forum.xda-developers.com/showthread.php?t=1276873

@dvb127 This morning the same happend to my Tablet. Could you find a way to fix it?
I have been running a CM-Version of january and switched to nightlies a couple of days ago. I can't remember anything else I changed
What I tried: flashed a new version of CWM (6.0.3.2) via ODIN and installed the january & newest CM via CWM. Both worked fine.
Still the same problem. When I boot the tablet it reboots several times and gets stuck in the CM bootanimation. Factoryreset and wiping /data causes a reboot.

NetZwerg said:
@dvb127 This morning the same happend to my Tablet. Could you find a way to fix it?
I have been running a CM-Version of january and switched to nightlies a couple of days ago. I can't remember anything else I changed
What I tried: flashed a new version of CWM (6.0.3.2) via ODIN and installed the january & newest CM via CWM. Both worked fine.
Still the same problem. When I boot the tablet it reboots several times and gets stuck in the CM bootanimation. Factoryreset and wiping /data causes a reboot.
Click to expand...
Click to collapse
I flashed a Stock Rom with Odin first, i had to too this in a win XP PC, because it didn't work in win8, rooted again, now I'm in cm again without any pproblems.

Hey, thanks a lot - worked for me as well

Related

Phone stuck at boot logo with various cm9 roms

Hello.
After running for months cm7 old baseband with no prob, today i decided to try cm9.
So i grabbed my copy of Arjen cm9, latest nightly, gapps, installed it. Then upgraded to new baseband 20G using LGMDP.
The phone booted, all fine, but there was no network. So i tryed reinstalling the new baseband, same story. The third time i reinstalled the new baseband, phone booted with stock lg gingerbread. So i reinstalled arjen cm9, but phone remained stuck at boot animation at the firts rebooot before installing google aps.
Then i decided to restart the process once again and redoing root, recovery etc. These are the step i took:
1) used KDV to reinstall lg stock ginger with 20G baseband.
2)rooted from gingerbread, installed rom manager, installed CWM.
3) reboot in CWM, wiped all, formatted with ext size 256mb and swap size 64mb.
4) copied rom and gapps, wiped everything another time.
5) installed arjen cm9, re booted, again stuck at boot animation.
6) re formatted, re wiped, tryed another rom ([2012.6.5] MIUI PORT by DHK).
7)rebooted, again stuck at boot animation.
No matter how many time i reboot or how many CM9 version i try, after the new baseband upgrade only the lg stock gingerbread seems to boot without remain stuck at boot animation.
Please help me with this new baseband/ cm9 thing, because i seem the only one that doesn't get it!
EDIT: now after 30 min stuck at miui boot animation, i rebooted the phone and this time it started the cm9 logo, then an icon of battery charging appeared in at the center of the screen and then phone dead! What the hell is happening guys? This is driving me mad, lost the the entire morning and until now trying to get this working.
Madpiercing said:
Hello.
After running for months cm7 old baseband with no prob, today i decided to try cm9.
So i grabbed my copy of Arjen cm9, latest nightly, gapps, installed it. Then upgraded to new baseband 20G using LGMDP.
The phone booted, all fine, but there was no network. So i tryed reinstalling the new baseband, same story. The third time i reinstalled the new baseband, phone booted with stock lg gingerbread. So i reinstalled arjen cm9, but phone remained stuck at boot animation at the firts rebooot before installing google aps.
Then i decided to restart the process once again and redoing root, recovery etc. These are the step i took:
1) used KDV to reinstall lg stock ginger with 20G baseband.
2)rooted from gingerbread, installed rom manager, installed CWM.
3) reboot in CWM, wiped all, formatted with ext size 256mb and swap size 64mb.
4) copied rom and gapps, wiped everything another time.
5) installed arjen cm9, re booted, again stuck at boot animation.
6) re formatted, re wiped, tryed another rom ([2012.6.5] MIUI PORT by DHK).
7)rebooted, again stuck at boot animation.
No matter how many time i reboot or how many CM9 version i try, after the new baseband upgrade only the lg stock gingerbread seems to boot without remain stuck at boot animation.
Please help me with this new baseband/ cm9 thing, because i seem the only one that doesn't get it!
EDIT: now after 30 min stuck at miui boot animation, i rebooted the phone and this time it started the cm9 logo, then an icon of battery charging appeared in at the center of the screen and then phone dead! What the hell is happening guys? This is driving me mad, lost the the entire morning and until now trying to get this working.
Click to expand...
Click to collapse
What do you see when you're booting your phone?
Fastboot Mode? Stuck at LG logo?
Sent from my LG-P500 using xda premium
EDIT: now after 30 min stuck at miui boot animation, i rebooted the phone and this time it started the cm9 logo, then an icon of battery charging appeared in at the center of the screen and then phone dead! What the hell is happening guys? This is driving me mad, lost the the entire morning and until now trying to get this working.
Click to expand...
Click to collapse
when you see the battery logo..hold power button again..and your phone will boot normally..
If dont works so go to recovery a and from cwm reboot system..other way to start the phone..
LG-P500-ICS-4.0.4
I've done it guys.. I had to install again gingerbred and 20G with KDZ, then re rooted, donwloaded rom manager, installed CWM, and then i installed again CM9 and it worked.. dunno what's gone wrong last time, i have done the exacts same steps and now it works!
Thanks for the help

Made a big problem for myself. Help please.

I have previously installed custom ROMs before and have successfully been running wanamlite for several months, however, i tried to install CM11 today.
I installed CM10.2 first to get CWM 6.0.4 and then continued to flash CM11. It was successfully installed and booted fine but apps kept crashing such as the playstore. I decided to go back to my wanamlite backup so went back, cleared the caches and went to restore to find that it couldnt find any files. Now when i try to reboot i get the Cyanogen mod cymbol then it loads the background but with a message that reads "the process com.android.phone has stopped" and i cant do anything from there. It will still boot into recovery and download yet this happens everytime i try to boot the phone into the normal mode.
So what did I do wrong? Whats the extent of my problem? & does any bright soul know if and how i can fix it?
Thankyou everyone
Jakeymd said:
I have previously installed custom ROMs before and have successfully been running wanamlite for several months, however, i tried to install CM11 today.
I installed CM10.2 first to get CWM 6.0.4 and then continued to flash CM11. It was successfully installed and booted fine but apps kept crashing such as the playstore. I decided to go back to my wanamlite backup so went back, cleared the caches and went to restore to find that it couldnt find any files. Now when i try to reboot i get the Cyanogen mod cymbol then it loads the background but with a message that reads "the process com.android.phone has stopped" and i cant do anything from there. It will still boot into recovery and download yet this happens everytime i try to boot the phone into the normal mode.
So what did I do wrong? Whats the extent of my problem? & does any bright soul know if and how i can fix it?
Thankyou everyone
Click to expand...
Click to collapse
With what recovery did you perform the backup? Maybe flashing that recovery will let you restore your backup.
All sorted now. I flashed the stock rom through odin and started again with the jeboo kernel and took extra care when flashing everything and now it's all working. KitKat-ed.
Missing some of the aspects of touchwiz a bit and i got a lower score on antutu than with wanamlite but i'll stick with it for a big, if only for the bragging rights when i get back to work on Monday.

[Q] Soft Brick. Cyanogen recovery loop. Will you please help?

Hello, i will try to be thorough.
BUT, i am a noob and didnt write down everything i did.
Have a I717 at&t note 1. with the 4.1.2 update originally OTA installed by keis.
I recently rooted it using Saferoot. it went well and i didnt see any problems. i flashed a custom rom and didnt like it so using clockworkmod recovery i went back to the 4.1.2. I then tried pac lollipop >pac_quicyatt_lp.beta-1.unofficial_20150327< i liked this rom but needed to flash Gapps.
This is where the trouble started. i didnt/dont know the proper procedure to flash the Gapps on top of or into the rom.
I first tried >gapps-5.0.x-20150404-minimal-edition-signed.zip< and it looked like it loaded correctly. but nothing appeared in the phone. the pac rom was still working well.
I then did more research and tried >gapps-lp-20150222-signed.zip< , again it looked like it loaded well but nothing showed up "in" the phone.
right here is where things got screwy. i had been using clorkworkmod for recovery and rebooting. and i think somewhere in developer settings i clicked something about how rebooting is handled.
because after trying to install the Gapps it went into Cyanogen recovery... and loops.
no matter what i do it goes back to cyanogen recovery.
I never knowingly installed cyanogen and dont know why it all of a sudden is going into cyanogen recovery over and over.
a list of things that may have bearing:
1. i tried reinstalling the pac rom. it loads and completes but it still just goes to recovery.
2. tried different ways of clearing cache and data wipes.
3. computer, kies, and odin 3.09 do not recognize phone.
4. have proper drivers on computer. phone was previously recognized by kies and cpu (4.1.2).
5. currently the only way to get anything into phone is by pulling sd card and reinstalling with info on it then using cyanogen recovery.
6. i have searched for about 11 hours and tried a bunch of things. but just restarts in cyanogen recovery
7. i was scared to fully try things i found that wernt specifically for the i717.
8. i could not find an original gingerbread rom. they all seemed fishy (needed downloaders. or ended in .zip.rar)
9. had backed up with clockworkmod and with titanium recovery (while in 4.1.2).
I dont know if i can reach the clockworkmod save through cyanogen recovery.... if so it seems like a great option.
10. at the bottom of the screen while loading rom is.... ---->>> E: cannot load volume /misc
11. only pac rom will successfully re-flash (even though it still just goes back to cyanogen). any other flash and it crashes halfway through.... i then restart and it just loops back to cyanogen recovery.
I searched here and tried the five recommended posts.
I could not try a lot of the "fixes" because the phone isnt recognized by cpu or odin (computer does beep when connected but doesnt show up anywhere).
Can you help me get back my phone please?
Randall
added
This is the only site i am asking for help on. I am willing to reply quickly and put in the time!
Thank you very much for reading this far.
Randall

[CM 13] Recovery didn't work, after trying to update phone too!

When I updated Cyanogenmod to CM13 my recovery stopped working (I turned on "update recovery with system"). I didn't can apply ANY updates from SD card and from PHONE STORAGE too.
To fix it I tried to update CM to 13 from 10-02-2016 to 13-02-2016. But... It didnt ANYTHING happened! It was only black screen. But now I can't turn on my phone! Recovery mode is not turning on too! I have only not working phone with not working recovery when it will turn on too!
I need my phone tomorrow, please, HELP ME! What can I do?!
Recovery: CM13 recovery.
It is not bootloop, I have:
BLACK SCREEN
After Samsung logo.
It is very important, does somebody know what to do?
I have new news:
After turning on I have samsung logo and for about one second Updating System message! Without loading bar . After it of course black screen!
I didn't do any backups of my phone, but I can wipe all data, but I NEED WORKING PHONE!
@tom790
Try flashing this kernel I attached with odin. Next try rebooting to recovery. If you get a working TWRP recovery, then flash the rom you want to use as normal. Please read this guide if you want to use CM13 and avoid common issues.
Same problem here after trying to update to the newest nightly (also with "update recovery with system" on in developer settings) I assume that this function isn't working correctly. The only alternative is as mentioned above - flash kernel+recovery with Odin and make changes afterwards.
I have same problem. I tried to install this kernel above with ODIN but no luck, after sucessful flash logo and black screen. Any other advice or tips? Is there any chance to recover some data from internal card?
And exactly the same issue here. Will try the workaround from the first answer by noppy22.
OK, succeeded. I used ODIN with the kernel tar file from noppy22, put the S2 into download mode (that was still possible, recovery mode couldn't be accessed), flashed the kernel. Phone rebooted automatically into recovery and started (continued?!) with the installation of CM 13.0. And here I realize the issue. The OTA was the nightly of CM 13.0 which I inadvertently chose to be flashed over the running CM 12.1. Bad idea!
Caveats: I see the yellow triangle now which didn't show up before. No problem for me - it's more than 4.5 years old. And there is still the error that "Google play service was terminated" which showed before I triggered the OTA update of CM 12.1.

Fixing Boot loop on Samsung Galaxy S+ (GT-I9001)

Hello everyone. This is my first thread on this XDA and I hope if somebody could help me. First of all, I know this phone was released in 2011 and it is considered old and outdated but I could really aprreciate help. I checked many threads and Youtube guides (I considered only those with good rating) and spent total of approximately of 16 or more hours in order to fix this but none of them were good for my case.
So here's the problem. Problem appeared about 20 months ago. First, I installed CM 11 on phone and everything was working fine except for the front camera. Then I tried flashing back to Stock ROM which I've downloaded from SamMobile. I used Odin for both times. After process was over, my problem appeared. Every time I turned on the phone it didn't get past Samsung Galaxy S+ logo. So I figured out it was Boot loop and that it can be fixed. I just couldn't find the working way.
Here are things I've tried: 1) Flashing Stock ROM via Odin without wiping cache first
2) Flashing CM 12 via Odin without wiping cache first
3) Flashing CWM Recovery via Odin, wiping cache and then flashing Stock ROM via Odin
4) Putting phone in Download mode, connecting it to PC and running Kies (Kies couldn't connect the phone because device wasn't responding)
From above mentioned only number 3 partially worked. CWM installed correctly but after I flashed Stock ROM I got same Boot loop problem again.

Categories

Resources